Customer-Centered Design Organizations
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
"It matters what you build, but it matters more if you learn."
Brenna FallonLearning Over Outcomes
October 24, 2019
"We didn’t have the maturity of the practice itself to specify the impacts of losing design ops until it happened."
Benjamin RealShowing the Value of DesignOps by Not Having a DesignOps Team
October 21, 2020
"Design ends up being a means to fix what development has already delivered."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
"The value of what we do is only really valuable if it’s recognized by others."
Johnny MichaelsenMeasure Behaviors, Not Results
April 23, 2026
"If you frame it as poor first experience risks a negative impact on adoption, you get way more eyeballs and attention."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"Assistive technology can feel like another person in the room during a research session, which you have to understand and include."
Kavana RameshMeaningful inclusion: Practicing accessibility research with confidence
September 24, 2024
"Travel is impactful to let your remote teammates experience your context, which helps build empathy."
Jilanna WilsonDistributed DesignOps Management
February 26, 2019
"Conversations create new language, allowing us to see possibilities that old language couldn’t reveal."
Paul Pangaro, PhDSystems Disciplines: Table Stakes for 21st Century Organizations
June 6, 2023
"Please don’t implement the Spotify model. It works for them, it won’t work for you."
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
