Collaboration Cycle Kickoff [Claims and Appeals, Higher Level Review Form Refresh]

[vhenry07]

Steps to complete Collaboration Cycle Kickoff

• [x] VFS Product Manager: Create this issue and fill in your team and feature name in the title.
• [x] VFS: Answer the questions below.
• [x] VFS: Using the Slack Workflow (User guide), notify Collaboration Cycle team of this Github ticket in #vfs-platform-support.
• [x] VFS: Attach any available artifacts.
• [x] Platform: Review the responses and comment in ticket with recommended touchpoints and practice area involvement.
• [x] Platform: Add project/feature to the Platform Collaboration Point Tracker.
• [x] VFS: Close this ticket when all steps above are completed.

Artifacts (if available)

• Link to draft of product outline
• Link to wireframes, mockups, or prototypes. Sketch mockups
• Any other artifacts you have so far - GitHub ticket outlining all changes implemented for the form refresh.

Questions

Please refer to the guidance in Getting Started with the Collaboration Cycle for detailed information and examples for the below questions.

1. Will your work result in visible changes to the user experience?

• [x] Yes
• [ ] No

Examples of visible changes include:

• Any changes that the user will see
• Adding a new form, tool, or page
• Modifying buttons, design elements, interactions, or page layouts
• Reordering content, adding new calls to action, alert boxes, expandable sections, or error messages

Examples of no visible changes include:

• Changes to code that the user won’t see
• Changes to accessible labels. These might include aria-label, aria-labelledby, aria-describedby

2. Is your work a new product/feature or an iteration to an existing product/feature?

• [ ] New
• [x] Iteration

Examples of a new product/feature include:

• Migrating over a paper form that has new design components
• Creating a new design component to a page layout
• Adding new functionality to an existing tool that is completely new to VA.gov

Examples of an iteration to an existing product/feature include:

• Modifying or adding functionality, an interaction, or content to an existing page
• Adding additional form fields or interactions to an existing online form
• Re-organizing content (adding headings, subheadings, new paragraph order)

3. Are you making changes to the visual design?

• [x] Yes
• [ ] No

Examples of changes to the visual design include:

• Any changes to design components, buttons, layout, or patterns
• Any changes to colors, icons, or typography

Examples of no changes to the visual design include:

• Code-only changes

4. Are you doing research with VA.gov users?

• [ ] Yes
• [x] No

Examples of research with VA.gov users include:

• Usability testing
• User surveys
• Card sorting

5. Will your work involve changes to: (select all that apply)

• [x] Tools and applications*
• [ ] Static pages
• [ ] Both

For tools and applications, take into account if any static page entry points will need updates.

6. Will your work include:

• [x] New content
• [x] Changes to existing content

7. Are you making a change to the user flow?

• [x] Yes
• [ ] No

Examples of changes to the user flow include:

• Adding a new section to a form
• Moving from a wizard to one thing per page form model

8. Are you making a change to urls, navigation, or entry points?

• [ ] Yes
• [x] No

Examples of changes to url, navigation, or entry points include:

• Moving an online tool or content page within the site or needing to retire/redirect a page
• Modifying options within core navigation elements (for example, top nav, left nav, home page)

9. Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo?

• [x] Yes
• [ ] No

10. If yes, then do you need to capture any other analytics or metrics in addition to what you're currently tracking?

• [ ] Yes
• [x] No

11. Who is the VA business owner for this body of work?

• [ ] VHA (Veterans Health Administration)
• [x] VBA (Veterans Benefits Administration)
• [ ] NCA (National Cemetery Administration)
• [ ] VACO (Veterans Affairs Central Office)
• [ ] Other. Please specify: ____

Additional information

Please refer to the Platform Collaboration Cycle guidance on Platform website for more information about the Collaboration Cycle.

[vhenry07]

Tagging @sshein for awareness. Also requesting we postpone kickoff temporarily.

[vhenry07]

@shiragoodman ready to move forward with kickoff.

[allison0034]

Hi @vhenry07. Thanks for completing this Collaboration Cycle Kickoff ticket! Based on your responses, your project is an iteration to a tool and/or application.

So we are recommending the following Collaboration Cycle touchpoints:

• Design Intent
• Midpoint Review
• Contact Center Review
• Staging Review
• Privacy and Security Review
• Full Accessibility and 508 Office Audit
• Post-launch Check-in

The following practice areas will be included throughout the Collaboration Cycle process:

• Design
• Content
• Information Architecture (IA)
• Quality Assurance (QA)
• Accessibility
• Product

We understand that scope of work and/or solutions can change as you work through your design process. If you find that your scope and/or solution changes, please reach out so that we can update and/or modify your touchpoints appropriately.

Your project has been added to the Platform Collaboration Point Tracker. Please review the guidance on our Collaboration Cycle Touchpoints page for next steps.

[vhenry07]

Thanks @allison0034. Requesting we skip Design Intent as this form update was small technical front end modifications on an existing product that didn't require new design. Form updates are to bring this product in line with our other (sister) appeals product that recently went through Collab Cycle (Notice of Disagreement). If other touchpoints can be skipped based on the NOD work precedents as well, please advise.

[shiragoodman]

@rtwell are you okay if this team skips Design Intent per @vhenry07's message above?

[rtwell]

ok by me!

[shiragoodman]

@vhenry07 I'll update the tracker to reflect skipping design intent. If possible, it would be great to have your Midpoint synchronous, opposed to asynch, otherwise the first time we'll see your product will be at Staging. Historically, this hasn't worked out well for teams, so please keep that in mind!

[shiragoodman]

@vhenry07 i hate to do this, but after discussion with OCTO and others, we decided that we cannot allow you to skip Design Intent for this work. OCTO, Platform Product Support, and Sitewide Content all use the Design Intent meeting to get a better understanding of what's coming down the pipeline. While the design may be good to go, and you could receive no feedback from us, the implementation of your product may impact other teams/products, and we need to be aware of that.

Please let me know if you have any questions. I'll reach out via Slack too to confirm you understand our decision.