What DesignOps Can Learn From DevOps
Summary
Traditional approaches to maintaining consistency break down when confronted by the complexity of digital business. While DesignOps and related approaches such as DevOps can enhance speed and responsiveness, they risk generating their own kinds of silos, blockages, and breakdowns. This talk will present an agile governance model that scales without becoming brittle, slow, or invasive. It will describe principles and practices teams across-the design-operations spectrum can use to balance agility, coherency, and resilience.
Key Insights
-
•
DesignOps and DevOps respond to the same systemic shift from industrial product focus to post-industrial service focus.
-
•
Modern service systems are complex, interconnected ecosystems, not simple, separable components.
-
•
Emergence means global behavior arises from local interactions without explicit central control.
-
•
Complex systems are inherently unpredictable and sensitive to small changes, complicating testing outside production.
-
•
Governance should shift from central enforcement to enabling continuous alignment and self-correction across teams.
-
•
Breaking work into small, manageable, independently deployable units supports safe, continuous change and scalability.
-
•
Service providers within organizations should treat each other as customers to maintain coherence without brittleness.
-
•
User experience extends far beyond interfaces to the entire service ecosystem including backend operations.
-
•
Continuous learning and iterative service design replace the industrial model of final, fixed solutions.
-
•
Security and governance fail when user-centered design is ignored, impairing technical goals and usability.
Notable Quotes
"I thought design ops was about bringing together design and IT operations, but I was wrong and that’s okay."
"The digital is infusing the physical and breaking down familiar boundaries between parts of our lives and systems."
"You can’t separate the front end from the back end and you can’t separate the inside from the outside."
"Emergence means global structure has no explicit rules, it emerges from local interactions between components."
"At a certain level, the only way to know how your system will work is when people use it for real."
"The very thing that got us into trouble—the complexity of small pieces—is exactly our way out of it."
"Your company is a service provider; your HR, IT, design, and security teams are all service providers."
"Governance needs to become a self-correcting, flexible, and adaptable mechanism rather than centralized enforcement."
"How you make service is part of what you make; functionality and operability become one inseparable experience."
"Far too often security fails because we forget people are involved."
Or choose a question:
More Videos
"Leadership is not management. It never has been."
Edward CuppsThe Principal Path: Journeying from Management to Individual Contributor
June 11, 2021
"You cannot improve security outcomes until you improve the relationship between Alice and Charlie."
Heidi TrostTo Protect People, You Have to Protect Information: A Human-Centered Design Approach to Cybersecurity
January 23, 2025
"The app was a huge flop because we let our excitement about helping people let our design principles slide."
Emily Danielson“I mean, I can lift a shovel”: Design Skills in Disaster Response
June 9, 2022
"Working at a government institution isn’t linear. Some projects might work out. Some simply won’t."
Sofía Delsordo Kassim VeraPublic Policy for Jalisco's Designers to Make Design Matter
December 8, 2021
"Never assume and always ask why."
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"The government UK Design System only works if the community contributes to it."
Kara KaneCommunities of Practice for Civic Design
April 7, 2022
"Even if the model is responsible for the behavior, there’s another piece of the puzzle: the context."
Paz PerezContext Architecture for AI systems
September 11, 2026
"Reviewing decisions out loud held everyone accountable and made it harder for Jeff to forget or change his mind."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"One design at scale advisor supports about 12 scrum teams, which is rewarding but cognitively demanding."
Nora Tejeda Giovanna AlonsoScaling Design Capabilities at BBVA Through a Self-service Design Model
June 10, 2021
