Create a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
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
"Unmoderated tools can achieve 100% completion rates and rapid insights if designed thoughtfully."
Anna Poznyakov Richa PrajapatiGet The Most Out Of Stakeholder Collaboration—and Maximize Your Research Impact
March 12, 2021
"Designing for change means focusing on learnability and product consumability, not just ease of use."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Whenever possible, you should be breaking down your work into specific research projects or topics."
Daniel KorczynskiWhy AI Is Bad at Research (and how to make it actually useful)
March 10, 2026
"It’s how you think about the relationships between people and these artifacts that makes a design system."
Dan DonaldDesign Systems as a Vehicle for Systemic Change
June 1, 2023
"I had to clean the taxonomy up because GPT wouldn’t know what to do with acronyms like TAOI."
Jorge Arango[Demo] How to re-categorize content at scale using LLMs
June 5, 2024
"Minimizing a user’s stress is the best possible design principle for disaster recovery."
Emily Danielson“I mean, I can lift a shovel”: Design Skills in Disaster Response
June 9, 2022
"We want to make sure researchers spend one hour in office hours, not eight to twelve hours a week helping others."
Mike OrenImproving Democratized Research with CustomGPTs and Gems
February 25, 2026
"Early inclusion is less costly and more effective than retrofitting accessibility later."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"Horst Rittel introduced wicked problems to describe problems where consensus on definition is difficult, and calling them problems can be misleading—maybe they’re better called messes or tangles."
Hugh DubberlyProblems with Problems: Reconsidering the Frame of Designing as Problem-Solving
June 19, 2019
