[CAIA intake] 10-10EZR

[hdjustice]

About your team

• Team name: 10-10 Health Apps
• OCTO-DE product owner: Patrick Bateman
• Product manager: Alex Seelig, Heather Justice
• Designer: Hieu Vo
• Accessibility specialist: David Kennedy
• Content writer:
• Slack channel: 1010-health-apps

CAIA Support Request

Describe what you need in a few sentences:

We are building the 10-10EZR Update health benefits form on VA.gov, which cannot be currently submitted online. This form can only be completed while the Veteran is authenticated on VA.gov, so that we can validate the Veteran is enrolled in VA health care. We will need a new URL, as well as Content support to ensure we are adhering to VA.gov standards.

Current 10-10EZR Update Info detail page

• https://staging.va.gov/health-care/update-health-information/

Possible URLs

• va.gov/health-care/update-health-benefits-form-10-10ezr
• va.gov/health-care/update-health-form-10-10-ezr

Which are you doing?

• Launching a new page, tool, form, or app
• Making changes to an existing page, tool, form, or app

Types of Support

What areas does your team need support in? Check all that apply.

Content

• Collaboration on content written by your team’s dedicated content writer
• Collaboration on content if your team does not have a dedicated content writer

Accessibility

• Accessibility review of wireframes and/or prototypes
• Accessibility issue (general request)
• Accessibility PDF review request
• Accessibility user research support (submit a separate, additional request)
• DST component or pattern
• Something else

IA

• User Flows
• Page placement
• URLs
• Breadcrumbs and Left Nav placement
• Redirects

Multilingual content

• Translating content

Timeframe

We guide and work alongside teams across nearly every OCTO digital product. We also work with partners across VA to lead content migration and manage all unauthenticated content on VA.gov. And we're always working to expand the VA.gov content style guide and our IA and accessibility documentation. We need to prioritize all intake requests based on our overall workload and VA and OCTO priorities.

Tell us about your product's timeline. And we'll work with you to meet timeline needs as best we can.

Have you worked with CAIA before?

• Yes
• No

What's your team’s next step and its timing?

• Our next step is Design Intent
• Provide date if available: xx/xx/xxxx

Timing for your next step:

• Next week
• This month
• Next month
• This quarter
• Next quarter
• 6 months
• 1 year

Is this timing related to a specific event or Congressionally mandated deadline?

• Yes
• No

If you're conducting research, when is that starting?

Provide date if available: xx/xx/xxxx

• Next week
• This month
• Next month
• This quarter
• Next quarter
• 6 months
• 1 year

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

• Yes
• No

Note: If you checked yes, we’ll reach out to discuss details about the content in the react widget (we use these widgets to display entry points for new products to a certain percentage of users who visit our static pages).

When do you expect to launch your product to 100% of users?

Please provide an estimated date so our team can create other relevant tickets.

• We expect to launch our product to 100% of users on: Mid to late January 2024

Collaboration Cycle

Will this work be going through the Collaboration Cycle?

• Yes
• No

If no ...

• Skip to the supporting artifacts section, below.

If yes ...

Please provide the link to your Collaboration Cycle ticket:

• Ticket (number): Collaboration Cycle for [10-10 Health Apps team, 10-10EZR Health Benefits Update form] #63773
• Collab. Cycle Ticket Opened (date): 08/16/2023

Please check all of the phases in the Collaboration Cycle you have completed:

• Design Intent (Planned for Late Aug/Early Sept)
• Midpoint Review
• Staging

For planning purposes, please check all of the phases in the Collaboration Cycle you feel you might need CAIA support and guidance:

Design Intent

• Accessibility
• Content
• IA
• Translation
• Already completed, no assistance needed
• Unknown at this time

Midpoint

• Accessibility
• Content
• IA
• Translation
• Already completed, no assistance needed
• Unknown at this time

Staging

• Accessibility
• Content
• IA
• Translation
• Already completed, no assistance needed
• Unknown at this time

Supporting artifacts

Please provide links to supporting artifacts as available.

• Product outline: 10-10EZR Product Brief
• User flows: 10-10EZR User Flow
• Prototype or mockups: 10-10EZR Wireframes
  • Focus on Flow A, the wireframes just under the User Flow
• Content source of truth: In Progress
• Research plan: Financial Disclosure Research Plan
• Any epics/issues that may be helpful:
• Link to testing accounts (please do not paste them in this ticket):

Additional Support: Collaborative Sessions

Have you already worked with someone from OCTO leadership?

• Danielle
• Beth
• Mikki
• Martha

How do you plan to work with us on this request?

• I’ll take this to Beth or Danielle’s office hours.
• I’d like to schedule time to talk about this.
• Let’s work async and meet as needed.
• Schedule a kick-off call with your team and CAIA for your project (Recommended)

Accessibility Help in Slack

The #accessibility-help channel in the DSVA Slack, is also available to you as a resource. Everyone is welcome to ask questions or get help from our a11y (accessibility) specialists. Tag @Terry Nichols to get a11y help asap.

Next steps

Once you’ve submitted this ticket, please post a link to this issue in the #sitewide-content-ia Slack channel and tag @Terry Nichols.

• If you also need engineering support from the Public Websites team, fill out their intake request form.

• If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a Redirect, URL change, or vanity URL request

• If you are creating an experimental design, please also contact the DST.

• If you are requesting a11y support for user research, please complete this form, next.

Content tasks

Preview Give feedback

1. Content updates to "Update your VA health benefits info" and other static pages for new 1010 EZR form #65056
   sitewide CAIA sitewide content +2
   

   
2. Content review of 1010EZR form screens #65655
   sitewide CAIA sitewide content +2
   

   

[sara-amanda]

Updated Comments as of 9/14/2023

CAIA Update

Completed

• Intake Ticket converted to an EPIC
• CAIA Epic already linked in the Collab Cycle Ticket
• CAIA GHP Fields Updated

Next Steps

• CAIA Kickoff Meeting @coforma-terry - Status completed as of 9/6/2023
  • 10-10-Health Apps Team @hdjustice , CAIA is starting the practice of a kickoff meeting with teams, who submit intake tickets. Your intake ticket mentioned working async and did not check the box for a kickoff meeting.
  • If you would like to schedule a short one, to go over your request, please let @coforma-terry know, many thanks!
• Create CAIA tickets for requested areas tied to Epic: Pending Meeting 9/14/2023 per @aliyahblackmore
  • Content Ticket @laurwill (Requesting CAIA assistance for portion of cycle: Midpoint and Staging)
  • Accessibility Ticket @ohgreatkate (Requesting CAIA assistance for portion of cycle: Midpoint and Staging)
  • IA @jennymayoco (Requesting CAIA assistance for entire cycle: Design Intent, Midpoint and Staging)

Collab Cycle Notes

• Design Intent Skipping DI - OK per Platform
• Check back on Collab Cycle Calendar, per intake ticket
  • Midpoint Date TBD as of 9/14/2023
  • Staging Date TBD as of 9/14/2023

Research

• Research
  • Sept TBD initial round of research - @hdjustice (will you be testing with users of Assistive Tech?)
    • If no, CAIA can assist with Assistive Tech. sessions, if sessions can be scheduled.
    • Here is a link to the CAIA Research Ticket.
    • DK will research out if they have any questions ahead of research.
      • 1010 team still figuring out the best route for research.

[hdjustice]

Thank you @sara-amanda!

• I wasn't sure about the CAIA kickoff meeting, but I will reach out to Terry for that. Since this is a new form, I definitely want as many eyes and ears on it as possible.
• We expect to have the Design Intent scheduled in the next couple weeks, and will be sure to inform this audience.
• We have David "DK" Kennedy as our resident Accessibility resource, and always welcome input from the CAIA team in that regard.
• We will be testing with users of Assistive Tech, and DK has been a great help there. We will submit a ticket if additional assistance is needed.

[hdjustice]

@coforma-terry - In regards to the above comments from Sara, we would be happy to have a CAIA Kickoff meeting. Since this is a new form, I think that could be a good idea. We plan to have our Design Intent within the next couple weeks, so we can meet before or after that. Is there a Calendly calendar, or do we try to coordinate?

[coforma-terry]

Hey @hdjustice - @aliyahblackmore is going to be coordinating on the content side and so will reach out to you to set up a kick off meeting for us! Thank you

[aliyahblackmore]

Hi @hdjustice thanks for reaching out.

Since you all would like IA assistance/feedback ahead of design intent, let's meet before you all have that on the calendar!

Jenny, Sara, Terry, and I are all available on September 6th and September 7th. These are some of our available times.

September 6:

• 2:30pm ET
• 3:30pm ET

September 7:

• 3:00pm ET
• 3:30pm ET

Do any of these dates and times work for you all?

If so, can you let me know the folks on your team that'll need in this meeting and I'll send over a calendar invite.

Thanks so much and looking forwarded to continued collaboration with this team!

cc @coforma-terry @jennymayoco @sara-amanda

[hdjustice]

@aliyahblackmore - you rock star!

The best time for our team would be September 6 at 3:30pm ET/12:30pm PT.
Teammates:

• Alex Seelig | [email protected] - Product manager
• Emily Brown | [email protected] - Delivery Lead
• Jessica Stump | [email protected] - Sr UX Design/Research
• David "DK" Kennedy | [email protected] - UX Design/Research
• Katelyn Caillouet | [email protected] - UX Design/Research
• Hieu Vo | [email protected] - UX Design/Research
• Matt Long | [email protected] - Sr Frontend Engineer
• Matt Kerns | [email protected] - Frontend Engineer
• Chapley Watson | [email protected] - Full Stack Engineer
• Lihan Li | [email protected] - Backend Engineer
• Joshua Drumm | [email protected] - Full Stack/Backend focus Engineer
• Fletcher Bonds | [email protected] - Sr Engineer/QA
• Luis Simauchi | [email protected] - Sr Data Analyst

Thanks so much!

[jennymayoco]

Hi everyone! Looping in @kristinoletmuskat for visibility in case of any IA questions while I am OOO (8/30-9/5). Looking forward to connecting with the team on 9/6 and happy holiday weekend

[aliyahblackmore]

Thanks @hdjustice ! I just sent over an invite for September 6 at 3:30pm ET/12:30pm PT. I've included the names listed in your above comment..

[hdjustice]

Can you add me? ([email protected]) I forgot myself!

[aliyahblackmore]

@hdjustice yes absolutely! I just added you.

[aliyahblackmore]

Hi @hdjustice - as you mentioned via Slack, these are a few alternative times for the kickoff (due to Alex being OOO most of the week of 9/5).

September 11:

• 2:00pm ET

September 12:

• 1:00pm ET
• 4:00pm ET

September 15:

• 12:00pm ET
• 1:00pm ET

Let me know if any of these times works for your team and I'll adjust the calendar invitation.

[aliyahblackmore]

Hi folks - posting some timeline updates here for awareness @jennymayoco and @ohgreatkate

The 1010 team will need to have designs (including content, IA, and accessibility feedback) to their engineers by September 29.

They encourage us to focus in on two key areas for this MVP of the 1010EZR:

• Any content, IA, or accessibility changes or feedback needed to keep a Veteran from getting blocked during the experience
• Focusing in on the intro and confirmation pages since those are new and unique to this form

Additional notes from their team:

• This 9/29 deadline is for the MVP focus; other suggestions and edits received after that will be incorporated into v2 early next year unless they are launch blocking edits.

• There will still be a midpoint and staging review phases in the collab cycle too.

@jennymayoco and @ohgreatkate - if you all have any questions while I'm mostly offline tomorrow (9/20) and Thursday (9/21) you all can use the design channel I mentioned via Slack!

cc: @davidakennedy @jessicastump @IMHieuVo @katelyncai

[kristinoletmuskat]

Hey ya’ll, here is the IA Spec Doc for the 1010ezr form (basically summarizing all of our decisions from the mural). We create these for every new launch so that when we later wonder what the IA decisions were and why, they’re all in one place. Pls read through and lmk if anything looks wrong!

And here's the link to the mural as well.

[aliyahblackmore]

Hi folks - just updating here that my content feedback is in the sketch screens

Some notes:

• As we chatted, I did a review and provided feedback on the new content outlined in red.
• There are some global changes to better align the content pulled from the EZ with current style standards (i.e. format for contact us info, telephone numbers, bolding, etc.).
• I’ve noted a few pieces of content that I’d like to revisit post MVP (including the error confirmation screen, since you all are considering prefilling the PDF that a user can download)
• I’ll coordinate confirming how to get necessary approvals from HEC stakeholders for the static page content. I have a question out to Danielle about this.
• Once I update the static page in Drupal, I’ll message Matt Long about the code for the sign in widget.

[aliyahblackmore]

Tracking some updates here:

• I shared the content for the sign in widget for the static page with Matt Long last week.
• Megan will copy edit the static page and I'll share that with HEC stakeholders this week.
• In the midpoint review artifacts, I saw that the 1010 team created a content source of truth doc. The doc includes placeholder text from the EZ. I chatted with the team and they'll update their content doc so that it's aligned with the sketch designs. If there's any content feedback that's still in the sketch comments and not in the designs, the content doc will at least be consistent with the current EZR sketch designs for midpoint. They'll plan to align both.

[hdjustice]

You all may already be aware, so I am leaving this comment for reference - We have scheduled our Midpoint review for Friday, October 27th at 2pm ET/1pm CT/11am PT.

[aliyahblackmore]

Hi folks -

Just tracking here that I opened a ticket with public websites re: testing the static page changes when they're not yet published.

Ticket for PW CMS/React content dark launch request

It's possible that public websites can dark launch a page for testing purposes only. This would basically include creating a duplicate page in Drupal that'll be behind a feature flag and when the content needs to be live, we'd archive the duplicate page and publish the "original" page.

I've pinged Alex (and cc'd Jessica and Hieu) about some of the questions that I don't have answers to (like the technical Point of Contact, date this would need to be in production, etc.).

And I let Jill know that she can reach out if she has any additional questions.

[aliyahblackmore]

Hi folks - tracking an update here for awareness:

• I made some adjustments to the static page content based on the last set of HEC feedback. Changes are now in the original and duplicate static pages. And I added the react widget code to both pages.

• The work on the dark launch is being tracked in this ticket.

• I also replied to the midpoint feedback in the the necessary tickets. Link to ticket with related tickets from Heather

[aliyahblackmore]

Just cross posting updates here following the my health/product team meeting today (cc @alexseelig)

Notes:

• Product team will determine if it'll be possible (from the technical side) to make the form intro page auth-only accessible (since it lives in my-health) before April 10. Based on what Sara mentioned, that means taking the sign in widget off of the form intro page. And based on what Matt shared, it sounds like there are some other technical things that need to happen (i.e. My Health has "route guards").
• If product team CAN'T make the form intro page auth-only, they'll leave the sign-in widget that's currently on the form intro page. As you all mentioned, the impact to user experience is that you all show Veterans something that they may not be able to do. And on the static page, we'll include an action link to the form intro page (where Veterans can sign in).
• If they can CAN make the form intro page auth-only, we'll need a react widget for the static page so that users can sign in. We'll place that widget under the Online option for the form - similar to this page.

Product team will work with Sara if there are any other questions about my health and how the forms live in my health (i.e. the my health alerts if someone isn't enrolled in VA health care, etc.).

Once they determine what'll happen ahead of April 10:

• I'll either need to add the react widget in Drupal (I can share the content with Matt and add the code to Drupal), OR
• I'll place a primary action link on the Drupal page (that's something I can do, nothing for you all to do)

[coforma-jamie]

I reached out to Heather Justice, the team's PM, who let me know that this has already launched and that we can close this ticket. She says that any further CAIA work will have new tickets.

[aliyahblackmore]

Thanks @coforma-jamie!

I'm going to move this to validate (cc: @strelichl @NaomiPMC).