Review and Update User Testing Items in Epics

[dan-padgett]

The purpose of this issue is to review and update the User Testing items for each epic. The process will ensure that our user testing items reflect our updated priorities and help us determine what data we need to collect to meet our research objectives. The goal is to have updated research objectives so that we can plan our testing accordingly. This will, in part, take the form of distinguishing research questions for MVP from the those for post-MVP.

Epics

Authentication and Authorization

• [Epic] Getting started shared landing page (unauthenticated)  #7
• [Epic] Filing home shared landing page (authenticated) #8
• [Epic] Login.gov account creation and sign in #9
• [Epic] View or update your user profile #10
• [Epic] View or update your financial institution profile #11
• [Epic] Complete your user profile (first time user) #12

Filing Process

• [Epic] Small business lending filing home #14
• [Epic] Provide type of financial institution #143
• [Epic] Upload file #35
• [Epic] Resolve Errors #166
• [Epic] Review warnings #169
• [Epic] Provide filing details #150
• [Epic] Sign and submit #180

Other

• [Epic] Confirm financial institution details #15
• [Epic] Navigate the platform #157

[dan-padgett]

Note: these are working notes for how to tackle this ticket.

Problem Statements

From a research perspective, there are two main problems (for MVP) we want to consider:

• Authentication and Authorization - How do we ensure that only those authorized to file lending data on behalf of an institution are able to do so?
• Filing Lending Data - How do we ensure that filers are submitting relevant, complete, and accurate data about and for their financial institution(s)?
  To address these problems, we need to achieve several objectives.

Authentication and Authorization

To address the problem around authentication and authorization we need to:

1. Understand how much compliance officers trust our authentication process with ensuring that only authorized individuals can file for an institution.
2. Determine whether our current "Complete your user profile" page encourages trust in our authorization process.
3. Assess the accuracy of the scenarios used to design the "Complete your user profile page".
   (Taken from Focus Group research plan.)

Research Questions:

• What do participants think of the ways in which SBL Help assists with verifying credentials? (Objective 1)
• Are users confident that someone creating a profile can associate themself with an institution if and only if they are authorized to file on behalf of that institution? (Objective 2)
• What do participants expect the system to do to verify a user should be associated with an institution? (Which of these need to be "behind the scenes"? Which need to be visible to person completing their profile?) (Objective 1)
• What gaps or inaccuracies do we have with our scenarios? Can participants give us an idea of how likely each scenario is at their institution? (Objective 3)
  (Taken from Focus Group research plan.)

Filing Lending Data

To address the problem around filing lending data we need to:

1. Submit correct and relevant information about the financial institution
2. Submit the correct lending data for that financial institution
3. Submit correct information for a point of contact.
   These need to be rephrased as research objectives since they are currently statements about the goals a user is attempting to accomplish for filing

[dan-padgett]

Some of the epics only list "Define tasks", some have "Define tasks" and "testing conducted". The checkboxes above are ambiguous on what they mean. Need to determine whether we need this ticket to focus on the task ideation and another to track user testing (or multiple tickets for tracking user testing).

"Define tasks" only - 8, 12
Both - 7, 9, 10, 11

[dan-padgett]

#15 isn't relevant for MVP design anymore, so that is being skipped in this review.

[dan-padgett]

The checklist above indicates that epics have been reviewed and user testing goals and tasks have been added (if needed). We'll want to track whether testing has been conducted separately, since we're still working on designs for some of these epics.