Finalize Research Plan

[msbtterswrth]

User Story

As a member of the AEDP team I want to finalize our research plan so that we can submit it for review and scheduling.

Background

ACs

• Research plan is ready for final review
• Conversation guide is ready for final review
• Screener questions are ready for final review
• Research plan in it's entirety has been presented to the team

Artifacts - (Google docs links for now until the test plan has been reviewed by Matt & Becky on Friday)

Research Plan
Conversation Guide

Testing Plan:

Task Orange
The unauthenticated signin alert
Header not included in prefill alerts
(Something about the language we use for non-editable data - awaiting CAIA response)
Prefilled information in the new “review style” for both editable and locked data
Users only save changes to the form
Service history presented in new “review style”
Review page and editing from there
Edit page contains multiple items

Task Gray
Header not included in prefill alerts
(Something about the language we use for non-editable data - awaiting CAIA response)
Prefilled information (address, specifically) presented in new white review card for both editable and non-editable data
Only allow users to save to their profile
Service history presented in white review card style

Task Blue
Header included in prefill alerts
(Something about the language we use for non-editable data - awaiting CAIA response)
Prefilled information (address, specifically) presented in gray card for locked data and white review card for editable data
Allow users to choose if they save to their profile or only the form (default to their profile)
Edit page contains one item

[beckyphung]

Adding my comments from #60 into this ticket:

See my thoughts on each of these research goals below. I went through each one and tried to understand the purpose for each goal. Please lmk if this aligns with what you were thinking too @msbtterswrth and @ChristineRoseSteiffer

Goal 1: Understand how users expect the prefilled data to display.

• Related components in our pattern: Uneditable and editable prefilled information
• Purpose: So we can decide which component users prefer (gray card or white card with outline) and to recommend in our pattern
• Why I think we don't need this goal: There wasn't a overwhelming preference for address block or gray card in the previous study.
  • address block We know address block is out because: (1) it isn't in USWDS which may make it more difficult to contribute, something I've heard Matt mention and (2) using address block in this way would be outside of its original purpose.
  • gray card We know VADS recommends moving away from gray card (similar to other direction we've gotten and won't test, like inline editing).
  • Therefore, I'd recommend we make the decision update our pattern guidance to using white card with outline AND remove this research goal

Goal 2: Understand users' expectations around why certain data can be edited within their profile and other data cannot.

• Related components in our pattern: Directions for updating uneditable information
• Purpose: Test new content that has clearer directions and links to and information page on VA.gov (Danielle's comments in this Slack thread)
• Suggested revision: Understand if users understand the directions for updating uneditable information

Goal 3: Understand if users want or need a confirmation step before submitting forms with prefilled data.

• Related components in our pattern: The form review page, I think?
• Purpose: I'm actually not sure about the purpose for this. All forms should have a review page. We shouldn't test a form without a review page. What we CAN test is whether reviewing prefilled information once is fine, and omit prefilled info on the review page (which some forms do). OR whether it's a better experience to review prefilled information in the middle of the form AND on the review page (some forms also do this).

Goal 4: Understand how users expect the edit process to work and where they expect their edits to get saved.

• Related components in our pattern: Confirmation message after saving, Edit as a subtask page with profile banner(?)
• Purpose: Test asking people whether they'd like to update their profile or not. If they do want to update their profile, test whether the confirmation message is clear. I'm assuming that their profile would be updated in the middle of the form, before hitting submit at the end.

[msbtterswrth]

This is looking really great! left a few comments in the doc, let's clean that up and move up updates into the github page!

[ChristineRoseSteiffer]

The research plan is ready for PO review. We met today and decided to remove Service History from the study, as we believe it's specific use case relates more to the 'Help users to understand when their data is mismatched' pattern that we will work on in the future. There are a few items to finalize, but they can be covered in our ticket next sprint for the review/revisions of the documentation and designs.

[beckyphung]

@ChristineRoseSteiffer and @kristen101606 I added some comments, suggestions, and q's to the research plan.

[beckyphung]

@ChristineRoseSteiffer and @kristen101606 I reviewed the conversation guide. The biggest feedback I have is to add in the "Things to notice" section after asking questions. This clarifies the purpose of the questions. Thanks!