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
"By centering racialized experiences in research, we're not just addressing diversity, but fundamental realities shaping modernity."
Florence OkoyeAfroFuturism and UX Research
March 27, 2023
"The golden nuggets—the unique insights—still require direct user engagement, but many teams have no time or access for this."
Joerg Beringer Thomas GeisScaling User Research with AI: Continuous Discovery of User Needs in Minutes
June 10, 2025
"Systemic bias means a tendency for procedures and practices within an institution that favors certain social groups over others."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"Are we excited to go to work in the technology industry to remove jobs and eliminate the human from the equation?"
Sam YenDriving Organizational Change Through Design? Do more of this and less of that
June 9, 2017
"Design requires teams because you can't be expert in everything—from pixels to hardware to databases."
Paul Pangaro, PhDSystems Disciplines: Table Stakes for 21st Century Organizations
June 6, 2023
"Retrofitting accessibility at a later date is difficult, costly, and demoralizing."
Sam ProulxAccessibility: An Opportunity to Innovate
September 8, 2022
"Most of institutional knowledge is tacit, meaning it’s understood or implied without being stated."
Maria TaylorKnowledge is Power: Managing the Lifeblood of the Design Org
October 3, 2023
"We entirely stopped using Figma at Survicate and are all working on these AI-powered prototypes."
Daniel Korczynski Justyna ParmeeFrom generic to contextual research insights with AI | Live Q&A
March 11, 2026
"If you are questioning your path, that’s data. It’s a sign something needs to evolve and that’s okay."
Ashley SewallExit Interview #5: Designing My Life After Tech
February 19, 2026
