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
"Follow-up questions missed opportunities to probe deeper or were confusing, and participants had to repeat themselves."
Tara TresselInvestigating qualitative depth of AI-moderated interviews
March 10, 2026
"Customer obsession instead of competitor obsession or technology obsession must be really clear across teams."
Tatyana MamutOpening Keynote: Breaking Conway's Law--or How to Work Differently and Not Ship Your Org Chart
June 3, 2019
"Teams started shipping multiple new features every few weeks, not because they cut corners, but because of fewer false starts."
Bianca JeffersonFrom Sprints to Systems: Operationalizing Continuous Discovery Through DesignOps
September 10, 2025
"Designing for AI means designing for behavior because you will not always get the same result for the same question."
Lukas Moro“Feels Like Paper!”: Interfacing AI through Paper
June 11, 2025
"Providing context to designers leads to much better design outcomes."
Product and Design at Bloomberg: A 15-year Evolution
December 6, 2022
"We wanted them to see the government not as an old machine, but as people who see themselves as users."
Sofía Delsordo Kassim VeraPublic Policy for Jalisco's Designers to Make Design Matter
December 8, 2021
"Collective consciousness cannot be asked to happen overnight; it’s a game of patience."
Jacqui Frey Dan WillisPanel Discussion: Integrating DesignOps
November 7, 2018
"Data standards are like selecting English as the common language, even if systems natively speak Portuguese or Spanish."
Lais de Almeida Maria IzquierdoDesigning Data Services
December 4, 2024
"There was never an official kickoff meeting to align all stakeholders and set clear expectations."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
