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
"Imagine if everyone you worked with, regardless of the role, had deep empathy for your customers and made decisions based on those customer needs."
Jemma AhmedTheme 2 Intro
January 8, 2024
"Fourth order design is about understanding system structure and intervening to create new pathways of experience."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"A key metric for a successful design system is how early the design system team is invited into project conversations."
Dan Mall“Ask Me Anything” with Dan Mall, Author of Upcoming Rosenfeld Title, Design that Scales
October 2, 2023
"Marital status mattered because some people buy cars for their spouses or kids, not just themselves."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Large language models sometimes hallucinate, so agentic backends assign sub-tasks to specialized expert agents."
Christopher NoesselAI of the now: Designing for Agents
July 31, 2024
"Exploratory user research can help teams think outside of commonplace organizational silos and facilitate collaboration across teams."
Sharon BautistaTime to Make the Donuts: How User Research Helped Bridge Disparate Teams
January 8, 2024
"Multitasking is a myth. You can’t listen and do emails at the same time effectively."
Tutti TaygerlyVideconference: How to Work with Difficult People with Tutti Taygerly
June 25, 2020
"We found a three percent decrease in time to market using our design system, which translates into measurable business savings."
Gonzalo GoyanesDesign ROI: Cover a Little, Get a Lot
September 8, 2022
"You have to be serious people making this business work, not just doing conferences and performative acts."
Max Gadney Andrea Petrucci Joshua Stehr Hannah WickesAssessing UX jobs for impact in climate
August 14, 2024
Latest Books All books
Dig deeper with the Rosenbot
How should service designers adapt their approach when working in different cultural and market contexts, like the US versus Europe?
What are examples of AI failures that highlight the need for bias testing and regulation?
What are the main requirements of the EU AI Act for product teams designing AI systems?