Conduct VBA Regional Office editor facing research sessions

[xiongjaneg]

Description

User story

AS A researcher
I WANT to conduct research sessions with participants
SO THAT we can get feedback on the VBA Regional Office editor experience

Guidelines

• Moderator guidelines
  • Research Safety guidelines
• Notetaker guidelines
  • For Editor-facing research, recruit a member of the product team to take notes
• Observer guidelines

Recruitment Trackers

• Editor-Facing research should track participants in the [VA.gov CMS UX research base](link TBD from CMS Platform team)

No-shows and rescheduling

• If a participant doesn't show up at the scheduled start time, they should be contacted
  • In Editor-facing research, the Moderator should contact the participant through email or Microsoft Teams
• If the participant hasn't shown up within 15 minutes of the start, consider it a no-show
  • See if the participant can reschedule for a different available slot

Acceptance Criteria

Before each session

• Moderator(s), Notetaker(s), & Observer(s) reviewed guidelines for their role(s)
• Moderator completes session-specific prep tasks

After every session

• Observers and Notetakers share their notes with Research Lead
• Researcher debriefs (i.e., into note-taking spreadsheet/Mural)
• Session recording and transcript downloaded from Zoom
• Researcher reviews notes taken by observers

After ALL sessions have been completed

• All notes stored in the research folder on github
  • Notes documents for cancelled/no-show sessions have been deleted

Resources

Research plan
Conversation guide
Notetaking Mural

[ALogsdon3]

Started a "Weekly Insights" section in the Mural. I'll share top insights here each week there are research sessions and we can look at them in UX sync.
cc: @mmiddaugh @thejordanwood @xiongjaneg @davidmpickett @jilladams

[ALogsdon3]

@xiongjaneg this ticket is structured a little differently from #17155, so I can't just check off all the ACs here, but for this sprint, all Before each session and After every session ACs have been completed.

[jilladams]

@ALogsdon3 @xiongjaneg @aklausmeier curious how we want to handle this ticket, given the low number of signups for research and that it may be a long-running situation to handle that. I hate to keep carrying it forever, but don't want to lose track of the details. What do you all think about spinning up a version of this ticket when we get new editor volunteers and run new sessions? Tedious bookkeeping?

[ALogsdon3]

@jilladams that seems reasonable!

[jilladams]

Per sprint planning discussion: we will spin up a small ticket per editor sign up to track both prep and conducting sessions.