[EPIC] Discharge Upgrade Wizard: modernize & convert to Subtask pattern

[wesrowe]

Top-line Description / Goal(s)

The existing discharge upgrade wizard was built in Vets.gov days. It does not use current design or content patterns. It requires a lot of scrolling due to the legacy pattern. We are also unsure if the information within the wizard remains correct.

Based on learnings from the PACT Act wizard, this effort will improve the ability for Veterans to determine their eligibility for a discharge upgrade by re-modernizing the product to align with current VA.gov design and content standards, and convert to a subtask pattern.

Initiative document

Status

[2024-07-08] All finished except for the Review screen tickets (see tickets below) and some stakeholder feedback to incorporate. [2024-04-01] Chris has completed the first two tickets and is working on the 1st question (ticket 3 of 15). These tickets include the Phase 1 content updates. Fran to create a ticket to implement the text corrections offered via email from Tanekwa, and these will be done after he’s finished with the 15 initial “MVP Phase 1” tickets.

[2024-03-01] No new updates

[2024-02-22 Fran] The V1/V3 Component work has bumped this project; hopefully will be started on 3/13 in Sprint 106.

IA request filed for temporary route

[2024-1/22 Fran] Tickets have been created by Chris K. and will be prioritized for upcoming sprint(s).

[2024-01-16] Sprint 102 will pull in work breakdown ticket.

[2024-01-08] Tickets for work breakdown for conversion to subtask and Phase 1 content changes are in Next Refinement.

Fran: get csat score for discharge upgrade wizard STATUS as of 01/04/2024

• Ticket created to scope the work it will take to update the DUW to the substack pattern; Chris K and Randi M will then create additional stories. #16656
• Ticket repurposed for Phase 2, which will be comprised of Stakeholder feedback (stakeholders not identified yet). #12801

STATUS as of 12/8/2023

• This project will consist of two phases for content updates. We were provided updates for Phase 1 this week, and the design ticket will be fleshed out with Katherine's updated provided.
• Fran has questions out to Dave re; who are stakeholders, and also a content question from Katherine

STATUS as of 8/8/23

• Discussed with DaveC. Steps to get this off the ground:
  • Dave: locate stakeholder(s) to validate that existing app is still correct
  • Dave: Verify that Public Websites should own this app, at least during iteration
  • Content team: Validate that content and results meet current standards
  • PW Devs: analyze existing app code and ensure that all possible branches are accounted for in a flow chart or other artifact. (Existing artifact needs to be replicated at this point.)

---

Headlines

VA stakeholders - TBD. Stakeholders for product has changed from past.

OCTO lead - Dave Conlon

Is this project tracked to an upcoming event or congressional deadline? - No

Details

Which OCTO team should do this and what is currently on their roadmap? - Sitewide (Public Websites)

Which OCTO priority does this work support? -

What is the user impact and scale of impact? - 19,000 views/month as of August 2023

Who would manage this product long term? - Public Websites

How much leverage will this create to solve more problems in the future? -

How great is the cost of inaction? (e.g., Can it wait? Must it be done by us?) -

---

Background

The wizard pattern has been deprecated by DST in favor of the Subtask pattern. The Discharge Upgrade Wizard needs to be converted to a subtask pattern. Designs for this can be found in this Sketch file.

User Story or Problem Statement

As a Veteran, or caregiver of a Veteran, I need the Discharge Upgrade Wizard to be easily understood a navigable SO I can complete it accurately and improve my chances of my discharge upgrade request being approved.

Affected users and stakeholders

• Veterans and their caregivers
• VA employees who receive and process the Discharge Upgrade Wizard requests/answers.

Hypothesis

We believe this effort will improve the ability for Veterans to determine their eligibility for a discharge upgrade by re-modernizing the product to align with current VA.gov design and content standards, and convert to a subtask pattern.

Assumptions

Acceptance Criteria

• [ ] Discharge upgrade wizard follows the substack pattern, e.g. one question per page. See this Sketch design.
• [ ] The existing logic flow for questions/answers is not degraded/lost.
• [ ] Requires KB article update

Change management triage

The change represented by this user story will:

• [ ] Be a site-wide change to appearance or key functionality (such as log-in process)
• [ ] Be a specific change that requires more than 30 minutes of work by a user to meet a publishing requirement
• [ ] Remove a piece of functionality (such as restricting editing functions, or “hardening”)
• [ ] Require action by some or all users by a specific deadline
• [X] Change the front end and be highly visible to the public
• [ ] Noticeable performance improvements (publishing speed, predictability)

If you selected an item above, use the Change Management Runbook to create a CM epic and associated tickets.

If you did not select an item above, update issues/PRs in GitHub but don’t plan for change management.

Design principles

Veteran-centered

• [ ] Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
• [X] Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
• [ ] Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
• [ ] Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

• [ ] Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
• [ ] Efficient: Remove distractions and create clear, straightforward paths to get the job done.
• [ ] Approachable: Offer friendly guidance over authoritative instruction.
• [ ] Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
• [ ] Empowering: Provide clear information to help editors make decisions about their work.

Runbook

### CMS Team Please check the team(s) that will do this work. - [ ] `Program` - [ ] `Platform CMS Team` - [ ] `Sitewide Crew` - [ ] `⭐️ Sitewide CMS` - [x] `⭐️ Public Websites` - [ ] `⭐️ Facilities` - [ ] `⭐️ User support`

[wesrowe]

Moving this to icebox for now – modernized subtask design is available in design ticket in this epic. We will consider this work in the context of evaluating the whole Public Websites product portfolio for design and tech debt.

[DanielleThierryUSDSVA]

Update 6.3.24: Expected to ship by end of second quarter.

[mmiddaugh]

Update 7.08.24

• Work complete except for updates to Review screen and the incorporation of some stakeholder feedback
• Planning Veteran research to validate the flow following an edit on the review screen