[Epic] Design: IA mapping for OneApp

[Samara-Strauss]

Background

Melissa has undertaken the huge task of mapping the existing IA of OneApp, the new structure we are proposing, and how these two versions map to each other. This epic is to track to-dos related to the IA mapping that is happening.

Tasks

PM

• [ ] Resolve some of the existing InVision comments with NJ team #153
• [ ] Determine how to help Melissa move forward IA spreadsheet during RI sprint #154

Mapping

• [ ] Complete IA mapping for Section 1: Basic Info #144
• [ ] Complete IA mapping for Section 2: Income #145
• [ ] Complete IA mapping for Section 3: Resources #146
• [ ] Complete IA mapping for Section 4: Expenses #147
• [ ] [FE] Generate a list of old questions to fields in the database #148

Client reviews/approval

• [ ] Review & finalize IA mapping for Section 1: Basic Info #149
• [ ] Review & finalize IA mapping for Section 2: Income #150
• [ ] Review & finalize IA mapping for Section 3: Resources #151
• [ ] Review & finalize IA mapping for Section 4: Expenses #152

Acceptance criteria

• [ ] Documentation is complete
• [ ] NJ has reviewed and approved structure for new sections

[allyceh]

@leahbannon2 @bestes-usds @melissajschaff and I met so that Melissa could walk us through the spreadsheet. Here are some ideas that came up during the conversation:

Design reviews with NJ:

• Provide NJ with a spreadsheet (or word doc, or something) that shows them the following so that they can provide feedback on the requirements before it translates to design:
  • The questions that are asked in the new prototype and the current questions they map to
  • Possible responses for drop downs or radio buttons
  • Whether or not a field is required
• After (or simultaneously?) they review the spreadsheet, share the designs so that they can see how the requirements translate to design.
  • This will allow us to have two separate design review convos, one for required questions and business requirements, and one for how that translates to design.
• InVision can be difficult to use for design reviews. Consider exporting PDFs of screens rather than using the InVision prototype.

Understanding what makes it to the new app:

• Once we have all of OneApp mapped, assess the application questions for the following:
  • Is this question necessary?
  • Does it help caseworkers? Is it required for processing? Is it required by law?
  • Is this question duplicative?
    • Can we get the answer to this question from somewhere else?

Ways of demonstrating why we made certain design decisions (i.e., one question per screen, wording of questions, etc)

• Prior to diving into design, show examples from Cal Fresh or other states as inspiration
  • Note that CFA has tested these (I am making that assumption, need to verify) and explain why they tested well
• Say what design principles we are following from plainlanguage.gov, CFA, others. Help anchor our designs in best practices.

[allyceh]

Next steps:

• Once @melissajschaff gets back from PTO, sync on finishing the spreadsheet and understand when @allyceh and @bestes-usds can help. This will likely be after quick submit work is finished.
• Determine if everything from OneApp made it in to the prototype.
• Consider piloting a spreadsheet and design PDF review with NJ for quick submit. Understand if reviewing questions in a spreadsheet is helpful for them prior to looking at screens.
• Internally, conduct an audit of the questions in the current OneApp. Determine if we can propose the removal of questions to make the application more concise and document application questions that we need to understand more about from NJ. Compare paper application and OneApp questions to identify possible questions for removal from OneApp.
• Consider showing other States' quick submit flows to NJ in Mural if we think it will bring value or mitigate pushback on design decisions.