Prioritize solution ideas for submission record and tracking

[pacerwow]

Issue Description

As a product team, we want to make space for cross-functional ideation to brainstorm ways to address the Veteran's unmet need so that we can effectively deliver the best solution for the identified problem. Follows from document takeaways from submission experience ideation session #91585

---

Tasks

• [x] Host a structured, cross-functional ideation session to identify possible solutions
• [ ] Build a shared understanding of direction by aligning with T-REX, and OCTO on the proposed solution(s).
  • [ ] Gather info on what Veteran Facing Forms has designed related to being able to download / view a copy of what the Veteran submitted. Shannon mentioned the Decision Review team also has an example to follow (product sync notes) - get info on this. start from Submission Experience: intersection with other teams and projects and update / supplement as needed - bring this into our internal workshop
  • [ ] Agreed for @pacerwow to schedule an internal workshop week of 9/16 to review existing solution from VFF and see if it meets our needs / any technical or user concerns we have based on our working knowledge of impact and feasibility. See if we have improvements to make based on our previous brainstorm. Ideally this would fall while the UX team is waiting on feedback from CAIA on Timely & Truthful Submission design work.
    • [ ] Topic to include: "What do we mean by 'record of submission' "?
    • [ ] Topic to include: "Scope definition: are we including the ability to download files (including evidence) in first phase?"
  • [ ] Document solution directions, details on scope, and rationales
  • [ ] Propose outcomes to OCTO enabling team and seek signoff on solution directions and scope

Acceptance Criteria

• [x] Create a range of ideas for how we could solve this problem
• [ ] design, engineering, and product team members have an understanding of initial solution directions and scope
• [ ] OCTO aligned on initial solution directions and scope
• [ ] takeaways are documented for easy future reference

[pacerwow]

Additional Context:

The Submission Record and Tracking solution should be dictated by the work being done by VFF which includes patterns for providing a copy of the form upon submission that will become a platform standard. The design team is familiar with the VFF copy of submission work and also that of the decision review team, who worked on a solution for an accessible version. This work was uncovered through their initial discovery and from our cross collabs on submission experience. If there is existing work on this from other teams, I would expect the head start knowledge from the VFF/decision reviews would allow us to go into actually working on designing this and discussing technical implementation, not sketching very high-level solution ideas. The goal is not to design a bespoke experience for 526.

Next steps would seem to be looking at the proposed pattern(s) from other teams, and seeing if we have questions/concerns/improvements to make based on the brainstorm. My understanding of strategy on this is that we would either provide an accessible copy OR an accessible copy AND a generated form PDF. I'm not sure we want to provide a form PDF at the moment with the state of the overflow page being what it is, and without looking more closely at the language differences on the questions.

EE team is also working on looking into improvements of the generated 526 pdf, but this may not be a dependency for the provide-a-copy efforts. Their changes may include over flow or the end to end data path entirely, but this is not expected to turn into immediate engineering tasks, hence why it's not considered a dependency.

Maybe there's less work to do on our end, aside from technical feasibility of providing the pdf. DBEX perspective of the initial draft is meant to be lightweight, and would consider these other patterns and solutions as part of feasibility and business viability.

Slack thread, from which is above is summarized.