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
-
•
Most organizations have a design operating model but often it is accidental, not intentional.
-
•
Positioning design at equal eye level with business and technology is crucial for creating valuable customer experiences.
-
•
A design operating model should focus on customer value outcomes, not just technical or financial outputs.
-
•
Three core levers to affect design operating model change are people (mindsets, skills), processes (rituals, tools), and organizational structures.
-
•
Leading by strategy with shared goals enables better collaboration than leading by rigid organizational structures.
-
•
A successful design system acts as a single source of truth, reducing redundancy and inconsistencies while enabling faster delivery.
-
•
The evolution of design teams—from individual embedded roles to shared design pods and guilds—solves workload imbalances and leverages individual strengths.
-
•
A 'false start' design operating model often shows itself in design being reactive, fixing what developers have done, lacking ownership and transparency.
-
•
Quick, visible wins like hackathons can catalyze design adoption and demonstrate value to executives.
-
•
Continuous communication, alignment, and protecting headspace for creativity are vital to sustain and evolve the design operating model.
Notable Quotes
"Design often ends up being a means to fix what development has already delivered."
"Bringing design on an equal eye level with technology and business is the starting point."
"The purpose of a design operating model is to place the customer at the centre of everything the whole organisation does."
"A design system is our hero here—it acts as a single source of truth facilitating collaboration among design and technology."
"Design needs to be aligned first; if design cannot agree amongst itself, how can the bigger organisation understand it."
"In a false start, design is perpetually fixing what development has done and is reactive, not proactive."
"A hackathon with designers, developers, business and architects can accelerate UI coded component delivery."
"Selling the design system’s value continuously, especially as new teams and components are added, is essential."
"You cannot sleep on your job; the design operating model must continuously evolve and be communicated."
"We are not a circus juggling nine balls; we focus on two to avoid cognitive overload and achieve meaningful output."
Or choose a question:
More Videos
"Democratization is not research anarchy where anybody can talk to any customer for any reason with no oversight."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"Designers are rebels; to get their buy-in, involve them and treat them as precious collaborators."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"Almost all the non-adopters were in engineering — they were more interested in their power within the organization than efficiency for users."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"When tactical metrics end up on the left side and KPIs on the right side of the compass, that signals we need a longer conversation about what we measure."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"There isn’t one single formula that works every time for a re-platforming journey."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Some people prefer their beliefs to data even in academia, which may surprise you."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"You can change the time zone to whatever works for you on the conference site to avoid ambiguity."
Bria AlexanderOpening Remarks
June 9, 2021
"Growth boards demonstrate you can have agile software development at enterprise scale without rigid processes or chaos."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"When they become important is when they recede into the background and become mundane."
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024
Dig deeper with the Rosenbot
What practical steps can UX and product teams take to integrate climate-conscious design in everyday tools?
What strategies help design digital environments that reduce bullying and promote supportive interactions?
How do common data standards serve as a 'common language' in modular healthcare IT platforms?