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) team.
About your team
Team name: `Veteran Facing Forms'
OCTO product owner: `Matt Dingee'
Product name: `Service Information Pattern'
Product manager: `Tricia Baker'
Slack channel: `veteran-facing-forms
Dedicated content writer on your team (if you have one):Insert name and/or GH handle
Dedicated a11y specialist on your team (if you have one):Insert name and/or GH handle
About your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
[ ] Digitizing a new form
[x] Creating a new digital tool - Creating / updating the Service Design Pattern
[ ] 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: insert description
What's the nature of your initiative and desired outcomes?
`Work with content to ensure guidance on verbiage is consistent and correct for service information patterns.
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
[x] 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 have gone through design intent but would like content to take a look at the figma files and workflow.
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.
[x] 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:
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.
[ ] 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
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) team.
About your team
Insert name and/or GH handle
Insert name and/or GH handle
About your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
insert description
What's the nature of your initiative and desired outcomes?
`Work with content to ensure guidance on verbiage is consistent and correct for service information patterns.
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?
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 have gone through design intent but would like content to take a look at the figma files and workflow.
Will you release this new product incrementally (for example, release to 25% of users to start)?
[ ] 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:
Enter dates
Name
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide a link to your Collaboration Cycle Request:
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.
Next steps
Suggest an addition or update to the design system team