Summary
How do we shape design organizations to always be in service of the user? Peter Merholz talks about how everything changed when he focused on getting the organization operations correct instead of just getting the design right. Peter Merholz is the VP of Design at Snagajob and the co-author of "Org Design for Design Orgs."
Key Insights
-
•
Great user experiences require aligning design strategy, execution, and organizational structure, not just individual designer skills.
-
•
Centralized design teams offer community and consistency but often struggle with strategic influence and slow delivery.
-
•
Decentralized embedded designers gain ownership and speed but suffer loneliness, skill narrowing, and fractured experiences.
-
•
A hybrid centralized partnership model balances dedicated design skill teams with close collaboration across product teams.
-
•
Organizing product, design, and engineering teams around customer types and journeys creates more coherent, customer-focused solutions.
-
•
Strong team leadership is crucial: leaders must manage down (team empowerment), across (stakeholder relationships), and up (executive communication).
-
•
Design organizations benefit from diverse skill sets beyond interaction and visual design, including content strategy and research.
-
•
Clear, shared definitions of design quality and brand experience principles enable designers to be bold and focused.
-
•
Leaders must be willing to say no to overextension, preserving capacity to deliver high-quality design work.
-
•
Relying solely on process without attention to the content and quality of the work leads to mediocrity and frustration.
Notable Quotes
"Execution is in service of the user."
"It’s not enough to have great people; you need to create the space that brings out the best in them."
"Centralized design teams tend to be brought in after decisions are made, turning design into an us versus them relationship."
"Designers embedded in teams often feel lonely and their work leads to fractured user experiences."
"Organize your product managers, designers, and engineers around customers, not features or code repositories."
"Design is always going to be subjective, so you have to figure out what quality looks like in your organization."
"If you want your teams to be bold, you need explicit quality standards and the courage to say no."
"Team leadership means managing down to empower your team, managing across to build stakeholder relationships, and managing up with executives."
"Relying on process is not a proxy for quality, and divorcing process from content is a fatal enterprise mistake."
"When the design team is organized into coherent teams working across multiple squads, designers feel more supported and less isolated."
Or choose a question:
More Videos
"Democratizing code with an internal open source model accelerates innovation."
Bill ScottLean Engineering: Engineering for Learning and Experimentation in the Enterprise
May 14, 2015
"Difficult people change things by looking at the world not as it is, but as they hope it could and should be."
Jemma AhmedTheme 2 Intro
March 26, 2024
"The catalyst that got your head count approved is the problem you should tackle first."
Amy Gawronski ZuccaroAdvice for DesignOps Employee #1
September 29, 2021
"Different organizations need different approaches; it’s hard to generalize research tooling needs."
Andrea GallagherThe Problem Space
May 16, 2019
"Synthetic data is useful because it’s easier to generate more examples of something you already have than to create entirely new data."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 2: Evals are your moat
July 23, 2025
"Curiosity and asking lots of questions helps push boundaries and improve solutions."
Product and Design at Bloomberg: A 15-year Evolution
December 6, 2022
"Design is problem-solving, and part of the problem is the environment in which you’re trying to work."
Bob BaxleyLeading with Design Operations Past and Present
December 19, 2019
"It’s less about interaction and more about integrity: How can we build trust in experiences?"
Ron BronsonDesign, Consequences & Everyday Life
November 18, 2022
"A design system team often has to wear multiple hats—diplomat, facilitator, architect, community manager—to keep momentum."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
