[CAIA Intake] Unified Appointment Experience: Community Care Veteran Digital Self-scheduling (CC VDSS)

[benbrasso-agile6]

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: Appointments
• Team name: Unified Appointment Experience
• OCTO product owner: Kristen McConnell, Kay Lawyer
• Product manager: Jeff Roof, Lori Pusey
• Designer(s): Ben Brasso, Christina Gednalske, Ciera Maddox
• Slack channel: unified-appointment-experience
• Dedicated content writer on your team (if you have one):
• Dedicated a11y specialist on your team (if you have one): Riley Orr

Your CAIA team:

Filled out by CAIA

• IA:
• 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
• [x] 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?

Tell us briefly about your work and the outcomes you’re aiming to achieve.

CC VDSS initiative brief

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.

• Figma designs (Laura W. is familiar with these)
• Veteran notifications via VA Notify in Figma needs review from Laura W.
• Veteran notifications via Notify in Word SharePoint

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?

• [x] Yes, Cleland Dole Act; pilot released before calendar EOY
• [ ] 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.

Software implementation; have not scheduled Staging Review yet. Heavy IVC coordination around change management, marketing, and communication.

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

• [x] Yes, specific pilot facilities

• [ ] 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? Assume the pilot might last 1-2 months; depends on IVC needs and success.
• What is the name of your engineer who will build the React widget? n/a

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

• [x] Design intent
• [x] 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:

• Hyperlinked Ticket Number: 80703

Next steps

• [x] 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
• [x] If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).

[laurwill]

Hey @benbrasso-agile6 , I made suggestions in the Figma — happy to attend that meeting you mentioned as well, and let me know if you need anything else here!

[benbrasso-agile6]

Looks perfect. tysm!!!

[benbrasso-agile6]

I'll update that Sharepoint doc next week, thanks

[benbrasso-agile6]

Made all suggested changes. TYSM, @laurwill!

This ticket can be closed.