[CAIA Intake] BMT 2: Benefits Management Tools, VA Letters and Documents

[rallencf]

Content, accessibility, information architecture (CAIA) new initiative collaboration request

Use this ticket to request collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) shared services team. Feel free to delete instructions and unselected options from the ticket to make it easier to scan.

Your team

• Product name: Claim status tool
• Team name: Benefits Management Tool 2
• OCTO product owner: @amylai-va
• Product manager: @salihaghaffar
• Designer(s): @sh0wn
• Slack channel: #benefits-management-tools
• Dedicated content writer on your team (if you have one): @rallencf
• Dedicated a11y specialist on your team (if you have one): Trevor Pierce @1Copenut

CAIA specialists involved

Filled out by CAIA

• IA: @kristinoletmuskat
• Content:
• Accessibility:

Your Initiative

Which of these descriptions best fits the work we’ll partner on?

Select all that apply.

• Digitizing a new form
• Creating a new digital tool
• Updating an existing form or tool
• Translating a form or tool into Spanish
• Adding new unauthenticated content to VA.gov
• Updating existing unauthenticated content on VA.gov
• Something else:

What's the nature of your initiative and desired outcomes?

Improve the usability and readability of the VA benefit letters and documents download user flow, including simplifying the process of downloading letters and verifying your mailing address—as well as updating the pre-login static pages to improve readability and align with new site-wide content and design standards.

Supporting artifacts

Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content. FOR FIGMA/MURAL: please tell us which screens/board/section to look at so we don't leave comments on old stuff.

• Benefit letters and docs user flow (Figma)
  • Draft user flow (in progress)
• Benefit letters and docs (Figma)
  • Refer to WIP page to review draft content and design

Collaboration timeframe

Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.

Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?

• Yes
• No
• I’m not sure

Where are you at in your timeline?

Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.

We're in early stages of wireframing and drafting content. We're starting the Collaboration Cycle on Friday, December 20 to discuss design intent.

Will you release this new product incrementally (for example, release to 25% of users to start)?

• Yes
• No

Note: For an incremental launch, we use React widgets to display dynamic content. We'll need at least 2 weeks of extra time to coordinate the content for this and work with your engineer. Learn more about our process for dynamic content. If your launch plans change, notify CAIA of the change as soon as possible so we can talk about how that will impact the timeline.

If you are releasing incrementally:

• What dates do you anticipate starting and ending your incremental launch? Enter dates
• What is the name of your engineer who will build the React widget? Name

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

• Design intent
• Midpoint review
• Staging
• None. This initiative isn’t going through the collaboration cycle.

Collaboration cycle ticket

If you’re going through the collaboration cycle, provide a link to your Collaboration Cycle Request:

• 98499

Next steps

• Review the remaining next steps in the VFS team tasks section here.
• If you also need engineering support from the public websites team, fill out their intake request form as well: Open a public websites intake request
• If you're requesting a page/URL redirect, a URL change, or a vanity URL, submit an additional request for this work: Open a redirect, URL change, or vanity URL request
• If you're creating an experimental design, also contact the design system team: Read more about experimental designs
  Suggest an addition or update to the design system team
• If you're requesting a11y support for usability research, submit a research support request next: Open an a11y research support request
• If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).
• Please don't close this intake when work is complete - CAIA will close and track