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
"Feedback is a gift; it’s always about the work and never about the person."
Erika Kincaid Brenna Heaps Jessica TsukimuraConnecting the Dots: How to Foster Collaboration and Build a Strong Design Review Culture
June 8, 2022
"The glue that binds strategy, execution, and measurement is missing in rapidly growing design functions."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"We try to provide a lot more patterns because for newbie designers or product owners, patterns help them put together flows quickly."
George Abraham Stefan IvanovDesign Systems To-Go: Introducing a Starter Design System, and Indigo.Design Overview (Part 1)
September 30, 2021
"This is a conference where you can stand up and people will see you do that — which we haven’t had in the past."
Bria Alexander Louis RosenfeldOpening Remarks Day 1
March 25, 2024
"Not everything that is faced can be changed, but nothing can be changed until it is faced."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"I reported to a head of product excellence, not the head of design, so I could say no to requests from design leadership with backing from my manager."
Peter BoersmaHow to Define and Maintain a DesignOps Roadmap
October 3, 2023
"Who is designing these AI systems, why, and for whom? Are those most impacted even involved?"
Sheryl Cababa Ethan Marcotte Milena PribicDay 2 Panel
June 5, 2024
"Executives get experimentation but often it doesn’t stick when people go back to their normal teams."
Alissa BriggsHow to Coach Enterprise Experimentation
May 14, 2015
"Cloud code wasn’t programmed to do this; it’s a very lightweight system where the model does most of the work."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
