Must, Should, and Consider Framework for Feedback
After the Design Intent and Midpoint Review, practice area specialists on the Governance Team will gather and formulate their observations from the review, and provide teams a list of written feedback, with each item ranked either, Must, Should, or Consider. The Must, Should, Consider Framework for Feedback does not indicate whether an issue will be launch-blocking at Staging Review. Whether or not the documented issue is launch-blocking will depend on the severity of the VA.gov Experience Standard that the issue violates.
Feedback categories
Must feedback
The practice area specialist has identified an issue that:
Explicitly violates one or more of VA’s design principles
Maps to specific guidance laid out in the VA.gov Design System
If not fixed before Staging Review, would likely be flagged as an issue violating the VA.gov Experience Standards.
Any feedback labeled must is critical, and integral to ensuring that the experience standards for VA.gov are met.
Should feedback
The practice area specialist has identified an issue that:
May violate one or more of VA’s design principles, but does not yet map to specific guidance in the Design System
Does not adhere to current industry best practices
If not fixed before Staging Review, could be flagged as an issue violating the VA.gov Experience Standards
It’s important that VFS teams respond to feedback labeled should, either by sharing a plan for addressing it, or by providing a written explanation of the project constraints that prevent them from implementing the feedback in the Collaboration Cycle ticket.
Consider feedback
The practice area specialist has identified an issue that:
May not explicitly violate VA’s design principles, but its implementation could fall short of current industry best practices
The VFS team should investigate the recommendation to see how it might improve the product’s user experience
If not fixed before Staging Review, likely won’t be flagged as an issue violating the VA.gov Experience Standards, but may adversely affect user experience.
Why feedback matters
Teams who build digital products for VA commit to deliver to Veterans a user experience as good as, or better than what they get on the consumer websites and apps they use every day. The Platform Governance team helps them meet that commitment by providing relevant, appropriate, end-to-end feedback throughout the Collaboration Cycle process. This feedback helps ensure that the team’s product and process:
Advance the top-level, user-focused objectives outlined in VA.gov's design principles
Follow the case-specific standards laid out in the VA.gov Design System
Meet the experience standards for the VA.gov Platform
Over the course of three Collaboration Cycle meetings, known as Touchpoints, Governance team members review the VFS (Veteran Facing Services) team’s design plans and artifacts to make sure they align with those principles and guidelines.
Help and feedback
Get help from the Platform Support Team in Slack.
Submit a feature idea to the Platform.