DUW usability research readout and report

[thejordanwood]

Description

User story

AS A researcher I WANT to wrap up my research study SO THAT I can share insights with others and protect participants' private information

Tasks

Collaborate

• [x] Share draft research report with team and ask for feedback

• [ ] Incorporate feedback into report

• [ ] Discuss draft recommendations with team

  • Recommendations are key outputs of the research process. They connect your findings back to the product roadmap(s) and shape the experience of future users. Depending on the type of research conducted, recommendations might be narrowly focused on improving a specific interface component of your team's product, or they might have broad implications for multiple parts of the VA.gov ecosystem. Work with the Sitewide UX Lead, UX team, Product Manager, and Product Owner to generate, refine, and categorize recommendations. PMs and POs also play a key role in socializing recommendations to other teams.

• [ ] Work with Sitewide UX Lead, PM, and/or PO to discuss whether research readout(s) are needed. If so, determine audience and meeting length (e.g., 30-min meeting with 20-min presentation and 10-min discussion).

• [ ] Work with PM to schedule research readout(s)

Research Readout(s)

• [x] Draft readout presentation slides
• [ ] Share readout slides with Sitewide UX Lead for feedback
• [ ] Incorporate feedback from Sitewide UX Lead
• [ ] (optional) Consider doing a practice runthrough to gauge flow and length
• [ ] Present readout(s) to team and/or stakeholders
• [ ] Revise report and/or readout slides per feedback from readout(s)
• [ ] (optional) Consider presenting at Sprint Demo; make a very short version of your readout slides
• [ ] (optional) Consider presenting at Veteran Digital User Experience Weekly Design Sync meeting; slack Naomi Marcussen to schedule a date; presentation template here

Add Findings to Research Repository

• Once your report is final, link to the relevant research repository:
  • Veteran-facing research: How to add research to Research Repo > What to do when you complete your research
  • Editor-facing research: CMS Research Repository

Delete and Archive Research Materials

• Review your notes and synthesis materials to make sure they don't contain any PII (Personally Identifiable Information). Then add them to your github research folder, and link to them in your research report.
• Once your readouts are complete, you should delete session recordings and transcripts from your computer and empty the trash folder.

Acceptance Criteria

• [ ] Feedback incorporated into research report
• [ ] Readout(s) conducted
• [ ] Findings added to Research Repo
• [ ] Notes and synthesis materials scrubbed of PII, posted to github, and linked to report
• [ ] Session recordings and transcripts deleted from your computer

[jilladams]

Per Slack, we'll plan to pull this into Sprint 16, but it's likely to start at the tail end of sprint and roll into SPrint 17.

[thejordanwood]

End of sprint update:

I have some readout slides drafted, but want to give everyone more time to give feedback on the research report. This ticket will roll over to leave time for feedback, any updates that need to be made to the report, and finalizing the readout.

[thejordanwood]

@FranECross @davidmpickett Please let me know if you have any feedback on the DUW research report. You can post that feedback in this ticket or in this Slack thread.

[FranECross]

@FranECross @davidmpickett Please let me know if you have any feedback on the DUW research report. You can post that feedback in this ticket or in this Slack thread.

@thejordanwood The research report is amazing. Great job, and I don't have any suggested changes.