Summary
A large federal agency was interested in improving the experience that individuals have with their digital services, as well as the velocity at which they were able to improve those services. But through our research, we found that they didn't have the design roles, tools, or processes in place to support this goal and make it successful. As a digital services firm that specializes in human-centered design and design ops, we came up with a plan to get them where they needed to be. We started by having a difficult conversation with them about design maturity, what it would take to be successful, and how design ops could help. We then introduced a series of training sessions on human-centered design, which prepared us to have conversations about design roles and processes, as well as tools. And finally, we were able to collaborate with them through a series of engagements to see how these things should work in practice. Through our experience, we learned this is not an uncommon challenge. There are likely many entities (both public and private) that know they need to evolve their design practices, but don’t know how. By sharing how we introduced design ops to a federal client, we hope to inspire others to help promulgate design ops in a wider variety of sectors and client types.
Key Insights
-
•
Federal government contracting imposes long timelines, strict policies, and limited tool adoption, challenging UX implementation.
-
•
Initial contracts may have fixed scopes that do not align with the actual user or organizational needs discovered later.
-
•
The agency’s design maturity was at a limited stage, lacking strategic UX culture, process integration, and measurable outcomes.
-
•
Delivering a design system without addressing foundational cultural and process barriers is insufficient for sustainable UX improvements.
-
•
Human-centered design training for non-designers builds empathy and broadens organizational understanding of UX benefits.
-
•
Government teams often rely on outdated or inappropriate tools like MS Paint, hindering effective design communication.
-
•
Internal champions, especially design managers on related teams, are crucial for advocacy and change management.
-
•
Combining top-down support and bottom-up engagement helps overcome entrenched silos and fosters adoption of design ops.
-
•
Frequent design reviews and biweekly syncs, though initially resisted, can become valued forums that enhance product quality.
-
•
Change in government design culture is incremental, often non-linear, requiring patience, persistence, and difficult conversations.
Notable Quotes
"It pains me to say, one of the tools they were using was MS Paint."
"Dropping a design system in this environment was not going to magically get them the improved experience they hoped for."
"It was finally the pathway to get them what they really wanted: a more intuitive and consistent user experience."
"People who work in government tech are some of the most passionate because they believe in the mission."
"Government culture is not like tech culture; IT constraints mean tools like Sketch are still a win."
"We basically wrote an HCD book with 25,000 words of notes for the training workshop."
"Early on, getting stakeholders to attend syncs felt like pulling teeth, but later it became their favorite meeting."
"Design ops is the bridge between silos and agencies that otherwise tend to be somewhat stagnant."
"Don’t ever be afraid to have those difficult conversations because they’re the most important ones to have."
"It’s about getting our stakeholders what they need, not just what they ask for."
Or choose a question:
More Videos
"Product managers can feel like they have no say about priorities just like UX practitioners do."
Louis Rosenfeld Christian CrumlishOpening Remarks
November 29, 2023
"Asking stupid questions can lead experts to reframe their thinking and improve the work."
Dem Gerolemou Alexis Oh Neef RehmanClimate technology fundamentals
May 15, 2024
"We hadn’t really thought about governance up front at all, which is not the ideal way to do something like that."
Dave Malouf Amy ThibodeauPanel: Design Systems and Documentation
November 7, 2017
"A lot of times those data streams are acting somewhat independently."
Brad Peters Anne MamaghaniShort Take #1: UX/Product Lessons from Your Industry Peers
December 6, 2022
"Doing this tagging manually would have taken me around 10 hours of mind-numbing work."
Jorge Arango[Demo] How to re-categorize content at scale using LLMs
June 5, 2024
"AI helped me produce nearly 80 posts in a year; without AI, that pace would be impossible."
Changying (Z) ZhengPractical DesignOps: From Ideas to Tools That Teams Actually Use
September 25, 2025
"Research office hours sound good, but many people feel nervous or don’t know if they’re ready to participate."
Crystal YanBuilding a Customer-Centric Culture
March 30, 2020
"Everyone putting their video on in hybrid design crits creates better engagement and makes remote folks feel included."
Courtney Maya GeorgeScale Your Organization and Grow Your Designers
September 8, 2022
"The internal dialects developed by project teams require intentional translation into a formal, limited lattice framework for portfolio analysis."
Sean Baker Sara RomanoskiWeaving Knowledge Management into the Fabric of Our Design Practice
September 11, 2025
