Summary
At a large U.S. federal agency, we've partnered across agency personnel, vendors, and contracts to build a single design culture that delivers an exceptional customer experience while meeting evolving business needs. We’ve built collaboration and critique rituals, tooling approaches, and design governance processes to organize 75+ designers into a unified practice all working together on a single, digital experience. We'll share what worked, what didn't, and provide a set of principles and tactics you can use right away – in any government agency – to begin building your own cohesive design practice, even when your ecosystem is anything but cohesive.
Key Insights
-
•
Centralizing research participant recruitment and documentation streamlines user access for multiple contract teams, improving research quality and inclusivity.
-
•
Collaboration across contractor boundaries is critical and can be facilitated by shared communication tools like Slack and regular cross-team meetings.
-
•
Normalizing design tools and processes across contractors ensures consistency, speeds onboarding, and prevents duplicated effort in maintaining design systems.
-
•
A governance-driven collaboration cycle with strict adherence to accessibility and user experience standards is required to launch VA digital applications.
-
•
Making design work and patterns visible early prevents redundant efforts and clarifies which user problems are already addressed.
-
•
Dedicated centralized expert teams in accessibility, content, IA, and QA free designers to specialize and maintain quality in large-scale enterprise projects.
-
•
Legal constraints, such as the Paperwork Reduction Act, limit research interactions, requiring balancing ethical concerns with agile user research.
-
•
Contracts structured around individual products rather than whole user experiences create challenges in coordination and require extra collaborative effort.
-
•
Fostering psychological safety and informal feedback venues enables design teams from multiple companies to share work openly and improve outcomes.
-
•
The VA’s approach has led to millions of veterans using self-service tools monthly, highlighting the impact of cohesive government design practices.
Notable Quotes
"Throwing a potluck sounds easy until you realize you don’t have a group that magically reads each other’s minds, resulting in a random table of snack foods."
"Our digital experience group acts like hosts and planners making sure veterans sit down to a cohesive, inclusive meal, not just disparate dishes."
"We have over 30 contracting teams spread across roughly 10 vendors all working on parts of the veteran experience landscape."
"A government designer aims to reduce UX variation while a contractor may optimize only their single product, creating potential conflicts."
"Reliable access to veterans and other users is fundamental to running quality, inclusive research across many teams and products."
"Slack channels and weekly meetings encourage cross-contract collaboration, avoiding duplication and sharing learnings across teams."
"The collaboration cycle requires following standards for accessibility, content, design system usage, and IA or you don’t launch your product."
"We treat our shared tooling and design system as a product with a dedicated team maintaining reusable components and governance."
"Designers contribute experimental patterns back to the design system early, making their work visible even before full validation."
"We’ve seen self-service tool usage grow from hundreds to millions of veterans served monthly after launching a unified VA platform."
Or choose a question:
More Videos
"90% of my job is saying the same thing over and over and over again."
Mark BoultonOps without Designers
November 7, 2018
"I message participants regularly during studies to reduce no-shows and troubleshoot any issues immediately."
Lily Aduana Savannah Hobbs Brittany Rutherford5 Reasons to Bring Your Recruiting in-House (and How To Do It)
March 12, 2021
"The bots can produce large amounts of code quickly, but many lines are test or documentation code, not production."
Christian CrumlishThe Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
August 14, 2025
"It’s much easier to classify an answer than to generate an answer, and that’s why LLM as a judge works."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 2: Evals are your moat
July 23, 2025
"We really had to go into it with an adaptable mindset and know when to drink the potion or eat the cake to grow or shrink."
Carla Casariego Sarah SpencerDesignOps in Wonderland
October 24, 2019
"System thinking is the cornerstone competency of design operations."
Jacqui FreyScale is Social Work
March 19, 2020
"People will forget what you said, people will forget what you did, but people will never forget how you made them feel."
Tutti TaygerlyMake Space to Lead
June 12, 2021
"When project scope changes, designers or design advisors raise their hand to reassess and adjust staffing accordingly."
Patrick CommarfordDesign Staffing for Impact
January 8, 2024
"The more complicated a web app becomes, the more necessary the ARIA application attribute is."
Sam ProulxDesigning For Screen Readers: Understanding the Mental Models and Techniques of Real Users
September 30, 2021
