Document takeaways from submission experience ideation session

evelynhilbrichdavis commented 2 weeks ago

Issue Description

This ticket captures the work of summarizing the workshop thinking into a light-weight list of takeaways, which will inform design work once the epics are picked up.

As a result of this ticket, we will have the value of the brainstorm clearly documented so we can make informed strategic decisions around how to solution for the next epics in submission experience.

Context

On August 26, 2024. DBEX hosted an ideation session with OCTO and Team 2 to brainstorm ways to 1) give Veterans a submission record and 2) make it easier/faster for them to resubmit failed material.

Artifacts

Mural for the ideation session

Tasks
[x] Document themes from workshop and ideas that rose to the top for each group
- [x] @mayacarrolluxa6 to document themes and ideas from group 1 (Reduce resubmission burden)
- [x] @evelynhilbrichdavis to document themes and ideas from group 2 (Submission record and tracking)
[x] @mengA6 to share documentation with team, OCTO, and other attendees / invitees from the workshop (slack)

Acceptance Criteria

[x] Takeaways from the workshop are shared out w/ OCTO
[x] Information is added to existing submission documentation so it is easy to find for when design begins

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.)

mayacarrolluxa6 commented 2 weeks ago

@mengA6 @evelynhilbrichdavis @pacerwow Here are the key themes generated by Group 1 during the resubmission workshop: (https://docs.google.com/document/d/1VVUeJicqqyynUvTxdnTAZVvqBxn3FDOrhvepJTjc8Z4/edit?usp=sharing)

evelynhilbrichdavis commented 2 weeks ago

Thanks @mayacarrolluxa6! I just added mine for Group 2-- all you @mengA6 @pacerwow

pacerwow commented 2 weeks ago

Thanks for putting this together @mayacarrolluxa6 @evelynhilbrichdavis. I gave it a scan and it looked good. I'll give it more time when I'm back in office.

I think it's really important that we show the value of this ideation session asap by getting together w engineering to consider some possible solution directions for Submission Record & Tracking. While I think it would be okay to wait a week from the date of the session, I don't think this could wait a month. @mengA6 it would be great to have you there, but since Maya and Evelyn facilitated the session and did this writeup I think it's most important to have one or both there. If you don't have bandwidth to attend, that's okay just let us know so we can determine how to proceed within this timeframe. Thanks!

mayacarrolluxa6 commented 2 weeks ago

@pacerwow Thanks for reviewing the write ups! Those next steps work for me.

evelynhilbrichdavis commented 2 weeks ago

Likewise!

On Fri, Aug 30, 2024 at 11:26 AM Maya Carroll @.***> wrote:

@pacerwow https://github.com/pacerwow Thanks for reviewing the write ups! Those next steps work for me.

— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/91585#issuecomment-2321863578, or unsubscribe https://github.com/notifications/unsubscribe-auth/BB5JWKNCJAMP35XT5RB2ABTZUCMLRAVCNFSM6AAAAABNGKUYDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRRHA3DGNJXHA . You are receiving this because you were mentioned.Message ID: @.*** .com>

-- Evelyn Hilbrich Davis. Sr. UX Researcher friendsfromthecity.com

mengA6 commented 2 weeks ago

Thanks, all. I'll communicate these themes out to OCTO early next week.

@pacerwow say more about why this couldn't wait a month. The workshop and these topics covered future epics in submission experience just because the research had findings to inform them. However, we are most focused on wrapping up Timely and Truthful Submission so that we can get it ready for engineers and release that first improvement soon.

I think postponing additional workshops and decision making on these future epics within Submission Experience until we wrap up design on Timely and Truthful Submission will give us the best chance of success and avoid overall project delays. I don't think there will be much loss in doing that since we are documenting the themes and takeaways so far here.

Shifting focus or context switching to do more decision making on Submission Record and Tracking, for example, will distract us and delay design work on Timely and Truthful, and I am anticipating it being more than just a single workshop - we will likely need to consider technical feasibility, including other systems that are not our own, to generate a PDF, and we'll need to consider consistency with other products in the ecosystem, etc. There might be additional discovery tickets needed.

We are re-teaming under the new contract, Maya is onboarding, and I'm shifting into a new role, and there is work / capacity involved in that.

Generally also I thought we were wanting to focus on fewer simultaneous initiatives, and I see focusing on a single epic within an initiative at a time as being in line with that idea.

mengA6 commented 1 week ago

I converted the key themes doc to markdown and put it in github and shared it out in this slack post .

Also linked to the doc from the epics it will inform:

mengA6 commented 5 days ago

We discussed internally and captured next steps (ideation session) in the updated Ideate solutions#90455

department-of-veterans-affairs / va.gov-team