Draft research plan for quick submit

[bestes-usds]

• [x] Review existing workflows for user research.
• Recruitment methods
• Incentive distribution

Create a research plan for testing quick submit:

• [x] Background
• [x] Goals
• [x] Method
• [x] Participants
• [x] Recruitment
• [ ] Timeline
• [x] Incentive process
• [x] Discussion guide
• [ ] Resources/Links

[bestes-usds]

Questions about existing workflow:

• There is reference to an email screener, but the link is broken. Cannot find the screener itself on Github.
• Need additional details on egiftcards.com, what the gift card is for, how they can redeem it, etc. We should clearly communicate the incentive since it's so important to the folks we speak with.
• ScheduleOnce is being used for scheduling and is a widget(?) in the consent form. Can I get access to this?
• Who is receiving the signed electronic consent form and demographic survey?
• How did recruiting via email work in the past? I know it wasn't very successful, but am curious about the process.
• Who have we reached out to and spoken with from these contacts?
• Where are existing recordings saved? How do we get access to NJ SharePoint to upload recordings for Guiseppe?

[allyceh]

What we test Do we test quick submit or do we test the end to end prototype (where quick submit is part of that experience)? Since quick submit it just a small part of the questionnaire, we might be able to collect more feedback and make better use of the applicants we test with (especially if they are hard to find) if we put our initial version of the app in front of folks.

Possible goals of testing Quick submit:

• Understand if the quick submit option is intriguing to applicants and if they're likely to use it
  • What circumstances would warrant them using quick submit?
  • Based on the messaging we provided (encouraging them to complete the app), do they understand that it is in their best interest to complete the full application?
• Is there any information they wish they had before they started our app?
  • Do they feel like our instructions page answers all of their questions prior to diving in?
• Is there any terminology that is tricky to understand that required further explanation?
• Is there any part of the process the applicants don't understand?
  • Examples: why we're asking for specific information? Why they need to provide gender or rent info?
• Do they understand what their next steps are after they complete the application?

Other thoughts Do we have documented goals of the new application? Reduce time by x minutes? Decrease manual entry errors for x field? Those goals could be things we test for and ensure our application achieves.

[allyceh]

@bestes-usds Found these design review notes. Jenn shares some usability testing goals with NJ:

https://github.com/usds/covid-19/blob/master/new-jersey/safety-net-benefits/design/design-meetings/2020-07-09/070920-design-review-notes.md