Formulate a plan: Forms digitization research

[steel36]

Purpose

The SDT has been tasked with helping Forms teams and Leadership understand why digitizing VA forms, currently offered to Veterans as PDFs, takes so long (three to nine months).

The outcomes should offer flexibility in case assumptions do not pan out, and provide a way to present to stakeholders for support and approval.

Assumptions

The SDT will have access to Forms teams The SDT can ask for access to VA staff such as adjudicators Forms teams have institutional memory of their past digitization work

Tasks

• [x] Prep approaches
• [x] Discuss possible approaches
• [x] Settle on a direction

Acceptance Criteria

• [x] Direction documented in Research Plan

[twoangstroms]

Holding here for now:

"Doing in/as a retro: journey-map-like format frame the whole project main phases/stages key actions or milestones Can any of this research be done async before a live workshop? Anonymous (if possible) round of green stickies for “what went well”, then discuss Anonymous (if possible) round of red stickies for “not so much”, then discuss Maybe set up the frame of the journey map in advance and let participants get familiar with it and have thoughts before sync workshop/meeting"

[twoangstroms]

From Naomi: Why do Form Teams go the custom route? What are all the variances?

Previous research on what components were least reliable out of the box could kickstart this: https://vfs.atlassian.net/wiki/spaces/FLT/pages/2161836319/Preliminary+Component+Research+-+FLT

[twoangstroms]

Previous research from a Forms spike team: https://vfs.atlassian.net/wiki/spaces/FLT/overview

[twoangstroms]

The initial examples of prioritization dovetail with what we've already seen from Forms teams, but interesting process insights into roadmaps here