shiragoodman
commented
2 years ago Hi @rileyorr. 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: (select all that apply)
- Design Intent
- Sitewide Content and IA intake request
- Research Review
- Analytics request
- Midpoint Review
- Contact Center Review
- Staging Review]
- Privacy, Security, Infrastructure Readiness Review
We recommend that you bring the tool/application and static pages through the Collaboration Cycle together so we can review the full flow/user experience.
Please reach out to Dave Conlon to let him know your work will impact static pages, the nature of the work, and your projected timeline.
The following practice areas will be included throughout the Collaboration Cycle process:
- Design
- Content
- Information Architecture (IA)
- Quality Assurance (QA)
- Accessibility
- Product
- Research
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 When you’re ready to schedule your recommended Collaboration Cycle touchpoints, please review the guidance outlined on the Collaboration Cycle Touchpoints page.
rileyorr
Steps to complete the Collaboration Cycle Kickoff
VFS Product Manager
Platform
Artifacts (if available)
Provide links or documents for the following:
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?
2. Is your work a new product or an iteration to an existing product?
3. If this is an iteration, please tell us what product or feature you're iterating.
Product or feature: Financial Status Report (VA Form 5655)
The online Financial Status Report (FSR) currently allows Veterans to request financial help for benefit debts incurred with the Debt Management Center. This initiative will expand the FSR's capabilities to allow Veterans to request financial help for VA medical copay bills. Additionally, we're incorporating feedback from the MVP usability study to redesign the list loop components. The goal is to simplify the experience and make it more accessible, as the existing list loop components were unintuitive to participants and the component is not navigable for folks who use assistive technology.
One thing I'm eager to receive guidance on is the suggested path forward for the wizard pattern. When we launched the FSR's MVP, the wizard still used progressive disclosure. Since then, I've heard that we're moving away from progressive disclosure to a more accessible one-question-per-page format.
4. Are you making changes to the visual design?
5. Are you doing research with VA.gov users?
6. Will your work involve changes to: (select all that apply)
*For tools and applications, take into account if any static page entry points will need updates.
**For information and examples of Static vs Dynamic pages, review the Static vs Dynamic guidance.
7. Will your work include:
8. Are you making a change to the user flow?
9. Are you making a change to urls, navigation, or entry points?
We will potentially make changes depending on IA's feedback. We'll be working closely with Mikki on this initiative!
10. Does your product or feature have Google Analytics tracking and a KPI dashboard in Domo?
11. If yes, do you need to capture any other analytics or metrics in addition to what you're currently tracking?
12. Is there a GitHub label in the va.gov-team repo for this product?
13. Who is the VA business owner for this body of work?
Additional information
Please refer to the Platform Collaboration Cycle guidance on Platform website for more information about the Collaboration Cycle. FYI: @shiragoodman , @chaseakirby