Design intent
Did we recommend a Design Intent in the Collaboration Cycle Request ticket? If so, follow the below guidelines to get started.
Owner
Governance Team
Timing
Request this touchpoint when you have an idea of how to solve your problem statement and have drafted a lo-fi prototype and/or wireframe.
Design Intent reviews require a 2 day lead time
Format
Synchronous 30-minute meeting
Agenda
This is the first opportunity for OCTO-DE and Platform to view your product. You’ll introduce your new work initiative and discuss existing solutions in the problem space. You’ll present your wireframe/prototype and walk through the user flow.
Platform and OCTO-DE will then ask questions and provide feedback relevant to the product.
Objective
To get feedback on the user experience and your product’s overall design, as well as guidance on how to meet VA.gov standards.
Both OCTO-DE and Platform use this meeting to gain an early understanding of the product/feature, including the goals/direction of the product, the intended user flow, and the overall scope of the initiative.
Moderator script
Welcome to the Design Intent for _______ team for ______ initiative.
The Design Intent meeting is intended to be a collaboration touchpoint between the VFS team, OCTO-DE and the Platform Collaboration Cycle team. We ask that you first introduce your new work initiative to us and discuss the problem space you are trying to solve for. It’s helpful to learn of any constraints you were facing. Then, present your artifacts and walk us through the user flow. Next, any Platform and OCTO-DE reviewers on the Zoom will ask questions and provide feedback relevant to the product. We will help guide you to existing design components, research findings, and share relevant examples from other VA.gov work. We will also communicate any information to ensure you’re building a product that meets VA.gov standards. Lastly, please note that "must" feedback, if not addressed, could result in launch-blocking issues at Staging Review. By not addressing the "must" feedback, your team accepts the risk of being blocked from launch to the VA.gov platform. Please handle accordingly.
Request
Collaboration Cycle moved to a new process beginning May 26th, 2022.
For those who started the Collaboration Cycle process after May 26th, 2022
VFS Product Manager completes Design Intent section of their Collaboration Cycle Request ticket.
All Collaboration Cycle Requests can be viewed on Collaboration Cycle Reviews ZenHub board
For those who started the Collaboration Cycle process prior to May 26th, 2022
VFS Product Manager submits a Design Intent ticket.
Attendees
VFS participants:
Designer(s)
Product Manager
OCTO-DE (optional)
VFS participants (when applicable):
OCTO-DE Product Lead (optional)
Content, IA, and QA specialists
Other stakeholders you want to invite
Platform participants (when applicable):
Design
Product
Analytics
Content
Research
OCTO-DE (optional)
Artifacts
VFS provides:
Whiteboard sketch or other lo-fi prototypes or wireframes
User flow
Research plan
Any other relevant artifacts you have so far
Outcome
Design, accessibility, research and IA Platform reviewers will document their feedback, if applicable, in a Feedback ticket linked to the Collaboration Cycle Request ticket. Feedback tickets will be available no later than EOD the next business day following the meeting.
Content and QA will not provide feedback at this touchpoint, as it's too early in the development process.
In addition, OCTO-DE or Platform may:
Recommend applicable Design System components and/or patterns
Identify needs for creating/updating Design System components and/or patterns
Identify needs for creating/updating VA.gov standards
Share relevant insights/flows/examples from other VA.gov work
Identify your product as a candidate for experimental design
Recommend early engagement with other teams that this work might impact
Recommend guidance for research
Help and feedback
Create an issue ticket to suggest changes to this page