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
"We used virtual sketching where users could move components into spaces representing their actual workflows on the platform."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"Researchers are often nervous about their research being used in the wrong way, so trust and communication matter."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community
August 27, 2020
"Scaling change starts at the margins and ripples from the periphery into the center of a system."
Hana NagelTurning Research Ripples into Waves
November 8, 2018
"Organizational DNA includes formal behaviors like policies and informal ones like communication styles that software must match."
Robert ReimannTaming Design Complexity with UX Models
June 8, 2017
"Product owners want everybody to be able to use their software, but if it isn't accessible, you're effectively discriminating against disabled users."
Sheri Byrne-HaberThe Importance of Accessible Design Systems
January 8, 2024
"Businesses hire designers for ROI; if you don’t measure design metrics aligned to business goals, design has no reason to exist."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 8, 2022
"Sometimes the power lies in choosing not to give energy to certain system dynamics."
Luke Roberts Christian Bason, Ph.D. Amanda Woolley Ben ReasonPanel Discussion
December 4, 2024
"What is in a name in a title is not much. It’s more of a mad libs plug and play where every title and role word can be swapped out."
Abbey SmalleyToday’s Design Ops and Programs Landscape & Career Paths
October 4, 2023
"Before, we never really looked holistically at decades of UX data—now we use it to be proactive and avoid duplicative studies."
Kristin WisnewskiMeasuring What Matters
October 23, 2019
