Synthesize insights & refine ideas : Submission Record and Tracking

[pacerwow]

As a Product Manager, I want to help guide the direction of the Design and Engineering work for this epic so that all team members and stakeholders are clear on the problem we're trying to solve, why it's important, and have ideas for a proposed solution. When we're ready to start designing a solution, we are confident that we have all of the inputs we need to create an effective solution.

The outcome we're seeking is alignment on the problem & proposed solution that we’ll design to in the future. Wireframes, mockups, high-fidelity design, and prototypes are out of scope for this Story. We'll build on top of previous research and thinking to complete these tasks. In some cases what we already have is sufficient and we won't need to do additional work.

Tasks

• [x] Analyze feedback and identify key insights from Research Study
• [x] Synthesize research findings, both previous and current and document this in GH
• [x] Identify key stakeholders who are affected by or influencing the problem
• [x] Write/revise a clear, concise articulation of the problem to be solved
• [x] Revise our user-centered problem definition combining user, need, and any new insights
• [ ] Host a structured, cross-functional ideation session to identify possible solutions (not possible - deferred)
• [ ] Build a shared understanding of direction by aligning with T-REX, and OCTO on the proposed solution(s) (not possible - deferred)

*Can build on or refine previous ideas we have

Acceptance Criteria

• [ ] The team, cross-functionally, has internal alignment on proposed solution
• [ ] The team has external alignment with OCTO on proposed solution
• [ ] Outcomes from tasks are documented in Github or GoogleDocs

• [ ] User story map is updated with needed Stories that reflect the proposed solution

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[pacerwow]

Updated the Submission Experience Initiative Brief with details on this future Feature. Let's review as a team and cross-reference the research.

[pacerwow]

The AC from this ticket were specific to the ideation session. We've chosen to combine Timely & Truthful and Submission Record and Tracking into one session, currently scheduled for Aug 26th. Closing this ticket as AC is no longer relevant.

[mengA6]

(just a note to help me keep track of where this is) per @mayacarrolluxa6 , working ideation workshop Mural, per Slack

[pacerwow]

I'll keep this open until @evelynhilbrichdavis and @mengA6 have had a chance to review edits Shannon suggested and I made to the Submission Experience Initiative Brief.