Integrate VA Stakeholders Feedback into Q3 Survey Results

[gracekretschmer-metrostar]

User Story or Problem Statement

As an OCTO stakeholder, I need to know how my feedback will be integrated back into the Q3 Survey Results doc.

Relevant Work

• Create Report for Review of Q3 Editor Survey Results #19315
• https://vfs.atlassian.net/wiki/spaces/PCMS/pages/3504308249?atlOrigin=eyJpIjoiM2Q3NDBmOTY5MTI0NDk0NTg3OGVhYmJmMGIzYWRkZDgiLCJwIjoiYyJ9

Steps for Implementation

• Send report to VA stakeholders to review. Give VA stakeholders with expectations on how and when to give feedback.
• Integrate VA stakeholders feedback into the report.
• Synthesize and finalize report.

Acceptance Criteria

• A finalized report that is ready to be sent to VA-at-large for Q3 editor survey results that includes VA stakeholders' feedback.

[aklausmeier]

Add recommended next steps to include areas we should research more of or consider design iterations on. Include in the internal report, NOT the stakeholder report.

[mmiddaugh]

Thanks for the opportunity to review your draft, @MDomngz

Appreciate the detailed and clear presentation of the responses, expressed in both percentage and number and the notable quotes

Suggest the following

• a Key findings section with clear bullet points preceding the data (i.e., The majority of respondents are relatively new to the system) - this will help readers scan/extract summary
• Recommendations for future iterations of the survey itself - what went well + what, if anything you'd do differently, such as new questions to consider next time, changes to the way existing questions are asked, or the inclusion of definitions for "accessible content" or "plain language"
• Recommendations to address actionable findings + any areas for further segmentation/analysis or addition research

[RLHecht]

@MDomngz this is really great to read. Thanks for sharing this with me. One thought I have (and maybe it's more for a future survey), is if it's worth looking at survey results based on the product worked on. For example, which types of editors find Drupal easy to learn or find what they need in the knowledge base. Seeing that might be helpful when figuring out next steps to improve certain areas.

[MDomngz]

After an internal team discussion -

• synthesize survey results into top insights/findings with recommendations/next steps section
• For "unpack" flags - synthesize and consolidate findings

[EWashb]

I think this work is great @MDomngz @gracekretschmer-metrostar. I have no notes. I understand there were other insights about digging deeper into individual products but I do not think it is in scope of this first survey. We can add them as things to consider on the next round.