Content collaboration on 10-10D form

[laurwill]

The IVC forms team is digitizing the CHAMPVA application, form 10-10D.

Recent Figma 3/25 - https://www.figma.com/file/UmAtr3ULQEInMXfNFwP0g0/10-10d-User-Testing-Prep?type=design&node-id=822-33966&mode=design&t=nRyqovG6bAx8Lqtt-0

Product team questions document:
https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/champva/1010D/1010d-program-questions.md

---

Files archive:

Original content source of truth: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/champva/1010D/sourceoftruth_with_stories.md

Updated content source of truth: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/champva/1010D/sourceoftruh_v3.md

Prototype: https://www.figma.com/file/Rnq4uKAlSUnVPD31fViTcj/10-10d-Prototype?type=design&node-id=508-73596&mode=design&t=FFPXL0CR2AQgVf0I-0

Updated prototype: https://www.figma.com/file/LWfLUckNkxEz3fxXsxde93/10-10d---%5BDoc-Uploads%5D-Updates?type=design&node-id=47-259488&mode=design&t=iuyjSZBem7asi9gP-0

User flow: https://www.figma.com/file/aDA1zJmVYRH8eDC776B4KR/Sharable-User-Flow-10-10d?type=whiteboard&node-id=0-1&t=ESV9hYet2Rq0A98q-0

[aliyahblackmore]

Updates here:

• We met with their team yesterday and had a content meeting today.
• We'll prioritize form content edits and then turn to the static page updates
• Their team is still waiting to hear back from SMEs about whether file uploads will be possible for the online form.
• I'll start on this early next week

Last communication with their team was on 1/26.

[aliyahblackmore]

Here's an updated content source of truth doc from their team. They made updates to the list and loop pattern.

https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/champva/1010D/sourceoftruh_v3.md

[aliyahblackmore]

Update here:

• Their team confirmed that applicant's can upload supporting documents for MVP. Their team is still working on designs for this, as of 2/2. I shared two upload screen design examples with their team on 2/1. They'll reach out when the content source of truth document and designs are updated.
• They shared an updated source of truth doc on Wednesday with the standard multiple response pattern.
• There are a few SME questions we need answers to re: differences between the PDF/CHAMPVA fact sheets/the static page. Is the PDF the most up to date and should we consider that the source of truth? I questions with the product team and they're coordinating getting those questions to SMEs. I let them know that they should CC Laura and I on any email communications.
• I let their team know (via Slack) that we'll now aim to have content feedback to them early next week -- since they shared additional updates and they're still in the process of updating other pieces of content/the designs.

My last communication with their team was on 2/1.

[kristinoletmuskat]

Hey ya'll, just jumping in to see if you could give feedback on the IA for this form -- particularly the crosslinks where I'm recommending we add/change stuff.

https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1705521134491/52690602ad9bb3ef8f9cbc82d48bd9698e63e83f?sender=ua641db233dc545173f8d9816

[aliyahblackmore]

Hey @kristinoletmuskat! This ticket is for the 1010D form - your mural link is for the FMP form.

Both forms are coming from the IVC team, but they're two different forms.

I'll have Lily open a content ticket for the FMP work and ping you to add this link there!

[kristinoletmuskat]

whooops sorry about that!

[aliyahblackmore]

No worries at all! @kristinoletmuskat

[aliyahblackmore]

Update here:

• Shared content review of SOT in intake request (2/8)
• We'll talk more with their team about the address content next week.
• Their team is also still working through the upload screens - we can review any new screens after their midpoint review.

Last communication with their team was on 2/9.

[aliyahblackmore]

Update here:

• Their team went to midpoint review today.
• I'll reach out to their team next week (Tuesday) and ask if we can start to look at these Figma files and make content recommendations on the new pieces of content ahead of their testing.

Last communication with their team was on 2/13.

[aliyahblackmore]

Update here:

• Product team shared a more recent in-progress Figma file yesterday 2/23.
• We set up a design and content sync to review some of the design updates they made after midpoint.
• Their testing date is still TBD.
• I'll plan to turn back to this work next week.

Last communications was on 2/22.

[aliyahblackmore]

Updates here:

• Product team share more recent Figma files on 2/29.
• They'll walk through the new pieces of content and questions on Monday.
• Testing date is still TBD. And they're still deciding what user flows they'll test with.
• Content updates are still ongoing - I'll be able to turn to all of the screens next week.
  Last communication was on 2/29.

[aliyahblackmore]

Update here:

• Feedback on the designs is still ongoing
• Teams shared a few other updates to designs based on SME feedback.
• I'm joining Platform design office hours on Tuesday to review the a solution to the form intro page (there are many documents someone may need to submit with the 1010D form)
• Content review will be done by 3/20.

Last communication was on 3/15.

[aliyahblackmore]

Update here:

• I wrapped up my full review of their Figma file.
• There are some outstanding questions that may impact content and flow -- Laura will provide feedback while I'm OOO.
• Laura will also provide feedback on the form intro page based on the Platform design office hours.

Last communication with the product team was on 3/19.

[aliyahblackmore]

Updates here:

• Laura and I chatted more with their team about the upload screens and they are okay to leave the designs as they are for testing (action links on upload screens at end of the form). Content concerns about designs/UX are documented in this Figma file.
• We'll leave the third-party rep language as it is for testing since their team confirmed they're not testing that flow. I documented that we will need to adjust this before they launch the form. This is tracked in Figma.
• We'll also leave the language about "helpless children" as is for testing. We'll plan to adjust this after testing.

[aliyahblackmore]

Updates here:

• Designers have all updates. And we'll revisit a few areas after testing.
• Yesterday they shared their compiled questions and replies from SMEs.

Last communication with team was on 3/28.

[aliyahblackmore]

Update here:

• Team is still getting ready for testing.
• They are still getting updates on some outstanding questions from the SMEs.

[aliyahblackmore]

Tracking updates here:

• Laura worked with the designers on updates to the screens inside of the form while I was OOO. I'll just go through and review and flag anything else that I'm noticing (i.e. there are some outstanding content items on the screen about applicant's between the ages of 18 and 23). If there are still outstanding questions that impact the content, we'll need to address this before the form is live.
• Laura is going to track some updates to the static page draft she worked on with Derek.
• And I'm tracking updates to the confirmation screen on this form. I added in question today and I am waiting on replies from the designers.

fysa @laurwill @strelichl

[aliyahblackmore]

Update here:

• Still waiting on question replies from the product team on the 1010D confirmation screen. There are questions in this comment and there's also a question on the confirmation email. We'll need answers to those questions in order to adjust the content accordingly. And as mentioned to the product team, once I have those answers I'll be able to track similar adjustments on the OHI and CHAMPVA Claim confirmation screens and emails.
• And as mentioned, I'll turn to the full OHI review after the confirmation screens. I started to take a look today and added a few comments on the earlier screens. I'll continue tomorrow.

[aliyahblackmore]

Update here :

Content adjustments/recommendations for the 1010D confirmation screen and emails are in Figma.

🔗1010D link

I flagged a few small inconsistencies in the designs across the forms (i.e. the use of "Your application details" as a header on the 1010D vs. as a field title on the other form emails) And I flagged a question about the name on the confirmation screen vs. the email (i.e. who signed vs. the applicant - I think the product team can include both)

[aliyahblackmore]

Update here:

Mary and Jamie joined office hours to talk about FMP reg and the other emails.

• We confirmed that we'll move forward with making the CAIA content adjustments to the confirmation emails now. The adjustments across 1010D/OHi/CHAMPVA claim, where applicable, will align. And when CAIA has standard VA notify content, we'll circle back if there are any future adjustments that need to happen.

• We confirmed on the call that we'll move the contact information up under "What to expect next" and remove the header "How to contact us about your application."

• And we confirmed that we'll use the header "What to do if you need to submit supporting documents" for the supporting documents information.

🔗1010D link

[aliyahblackmore]

Update here:

• The product team is prepping to launch MVP.
• They requested a content review of updates they made to the signer screens.
• I tracked adjustments directly on their screen and there are a few outstanding comments. I'll circle back on any content changes once I hear back from the team.

[aliyahblackmore]

Update here/cross posting from Slack:

• For post-MVP iterations in the future, we'll plan to chat more about a potential radio button option to reflect the use case you all observed in testing - applicants applying for themselves and other family members. A potential way to do this can be a radio button that says "I'm applying for myself and a family member" - this could help avoid showing the signer screen to applicant who are only applying for themselves.

• And the only outstanding question in Figma is about edits in the "Applicant" section and how they'll carry over to the "Signer section". Rachel mentioned that she'll flag this as a question for the engineers. Just tracking here that my only concern (from an applicant perspective) is that if edits to the applicant prefill don't carry over to the signer section - that could lead to potential confusion and extra steps for the person applying. For example, if someone misspells something and they decide to edit it in the applicant section, but when they review their information at the end and the change doesn't show in the signer section, then they'd need to go back and make the change. Or if they don't adjust the information at all at the end and the two sections have different information - that could be an issue for folks processing the form.

[aliyahblackmore]

Cross posting an update:

Chatted with the designers and engineer and the "prefill from signer section" flow will remain as it is and they'll implement an alert on the Review screen for applicants applying for themselves who have mismatched information in the Signer and Applicant section. I added the alert content using a comment.
🔗Figma link

Some other things throughout:

• On the Applicant section prefill auxiliary screens - If it's feasible for MVP, the team can still consider adding content in the info alert that let's the applicant know that they can go back to their signer screen and update their information there as well (doesn't require a link, just an instruction to go back). If they overlook that content in the information alert, they'll still see the alert on the review screen. 🔗Figma link
• On the auxiliary review screens at the end, there were some previous content updates/recommendations missing. I re-tracked those things using comments and added a question 🔗 Figma link
• Other comments on figma screens for their attention (i.e. consistency, buttons, etc.)