Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conduct VA Regional Office editor-facing research session #17713

Closed
9 tasks
jilladams opened this issue Apr 3, 2024 · 6 comments
Closed
9 tasks

Conduct VA Regional Office editor-facing research session #17713

jilladams opened this issue Apr 3, 2024 · 6 comments
Labels
Blocked Issues that are blocked on factors other than blocking issues. Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team Research CMS team practice area sitewide UX

Comments

@jilladams
Copy link
Contributor

jilladams commented Apr 3, 2024

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

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
    • Prep hand-off for subsequent researcher(s)

Resources

Research plan
Conversation guide
Notetaking Mural
Sharepoint UX Folder, specific to this study

@jilladams jilladams added Needs refining Issue status Research CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team UX labels Apr 3, 2024
@davidmpickett
Copy link
Contributor

@thejordanwood Agree on a 2?

@thejordanwood
Copy link

@davidmpickett Sounds good!

@davidmpickett
Copy link
Contributor

Update: @aklausmeier told us that the participant has had other priorities come up and may not be able to complete this session during this sprint

@jilladams jilladams removed the Needs refining Issue status label Apr 10, 2024
@davidmpickett
Copy link
Contributor

@jilladams I am removing Sprint 1 from this ticket and moving it back into Ready. The participant was unable to schedule the session. This was an injection rather than part of the Sprint plan. We can keep this ticket in our pocket for any other opportunity that pops up.

@davidmpickett davidmpickett added the Blocked Issues that are blocked on factors other than blocking issues. label Apr 30, 2024
@davidmpickett
Copy link
Contributor

Moving to Blocked since we don't have any participants lined up

@aklausmeier
Copy link

closing, no longer a prioritized effort

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked Issues that are blocked on factors other than blocking issues. Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team Research CMS team practice area sitewide UX
Projects
None yet
Development

No branches or pull requests

4 participants