Summary
All organizations have a design operating model. But not all organizations are intentional about creating it. It gets established by accident. Design gets fitted around other priorities of business or technology. As a result, organizations struggle to create valuable experiences for customers. This is why organizations need to design their design operating model.
Key Insights
-
•
Many organizations have design operating models established accidentally without deliberate intention, leading to reactive design work and inefficiencies.
-
•
Design must be positioned on equal footing with business and technology to create valuable, seamless customer experiences.
-
•
A successful design operating model has four dimensions: customers/users/market, organizational context, product teams, and communities of practice.
-
•
Three key levers drive change in the design operating model: people (mindsets and incentives), processes (rituals and tools like design systems), and structures (team and physical environments).
-
•
Leading by strategy with shared goals and governance is more effective than leading by structure focused on power and departmental silos.
-
•
The 'true start' scenario shows the benefit of early, lightweight integration of design within agile teams, supported by rituals like prioritization meetings and design critiques.
-
•
Design systems serve as a crucial single source of truth that fosters collaboration between designers and developers, reduces redundancy, and maintains consistency.
-
•
Scaling design teams requires flexible structures like design pods and guilds to balance workload and support strengths while maintaining alignment.
-
•
The 'false start' scenario reveals challenges of fragmented, output-driven domains with weak collaboration, lacking end-to-end ownership, transparency, and timely design involvement.
-
•
Intentional, continuous evolution of the design operating model and clear communication of its value across the organization are essential for lasting impact.
Notable Quotes
"Design ends up being a means to fix what development has already delivered."
"Bringing design on an equal eye level with technology and with business is the starting point."
"Design is not about one brilliant idea but about collaboration between different roles and expertise."
"Customer value outcomes should drive empowered product teams rather than technical outputs or budgets."
"Leading by strategy with common goals and governance enables better alignment than leading by structure."
"Design systems act as a single source of truth facilitating collaboration among design and technology."
"A false start means design is not considered first, leading to rework, cost loss, and product failure."
"The hackathon gave design the ability to produce coded components quickly, showing executives the value of design investment."
"A strong, consistent design voice is critical so the organization understands what design really is."
"Creating space and mechanisms for creativity protects design time and cognitive load, enabling quality work."
Or choose a question:
More Videos
"Qualitative data is data. It’s okay to be informal and human when designing complex systems."
Alison Rand Sarah BrooksScaling Impact with Service Design
March 25, 2021
"Our technical leads started attending other teams’ meetings, helping break down integration barriers."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Drawing a boundary was the hardest part for me, like stopping drawing the systems."
Sarah FlamionComplex Problem? Add Clarity by Combining Research and Systems Thinking
March 31, 2020
"Design is enabling, enabling function and therefore it was invested in as IP and USP, but now it is seen more as a resource and expense that is questioned."
Silke Bochat5 Antifragile Strategies for a DesignOps 2.0
September 23, 2024
"The grownups’ table is where we talk about business problems and organizational complexity, not just sketching."
Uday Gajendar Lada Gorlenko Dave Malouf Louis Rosenfeld Dan Willis10 Years of Enterprise UX: Reflecting on the community and the practice
June 18, 2025
"We’re going to say fortunately, and she’s going to say a sentence. Then we say unfortunately, and he’s going to say a sentence connected to that sentence."
Dan WillisEnterprise Storytelling Sessions
June 8, 2017
"We ran community gatherings with themes, presentations, and breaks, because people needed space to just chat and connect."
Kara KaneCommunities of Practice for Civic Design
April 7, 2022
"We made this move in January 2020 — our research and insights team moved out of UX but stayed within product organizations."
Nalini KotamrajuResearch After UX
March 25, 2024
"The most highly rated part of the conference every year are the facilitators making the cohorts sing."
Bria AlexanderOpening Remarks
October 1, 2021