The Power of Difficult Conversations: A Case Study on How We Introduced Design Ops in the Federal Government Space
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
"People connect with other people, even through screens, so employee recommendations matter digitally too."
Erin WeigelReal-world lessons to improve your conversion rates
June 26, 2024
"Context is everything — providing AI with a folder of your company’s knowledge makes responses more detailed and useful."
Daniel KorczynskiWhy AI Is Bad at Research (and how to make it actually useful)
March 10, 2026
"I don’t want people to do a 6 AM call — I can do a 10 PM call to brainstorm but not a design critique."
Kim LenoxLeading Distributed Global Teams
May 20, 2019
"We don’t have to restrict ourselves to playing the canary in the coal mine. We can design the harm out of our products before they’ve even taken flight."
Brendan JarvisFraming Tomorrow by Questioning Today
June 8, 2022
"We dropped the word prototyping for simulation because it resonated better with clinicians and learning departments."
Carol MassaDesigning Health: Integrating Service Design, Technology, and Strategy to Transform Patient and Clinician Experiences
December 3, 2024
"Upskilling customer success managers and others to help with testing meant we could do far more research than I alone could manage."
Dr Chloe SharpUsing Evidence and Collaboration for Setting and Defending Priorities
November 29, 2023
"Pay transparency within organizations is critical for enabling good work and healthier working conditions."
Sarah Auslander Betsy Ramaccia Gordon RossInsights Panel
November 18, 2022
"His sigh was just a sigh. It was not a signal of any defect or usability issue to solve."
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"By automating deliverables analysis, we saved 12 hours per week within one design team alone."
Farid SabitovAutomatization for Large Enterprise Teams
January 8, 2024
