Customer-Centered Design Organizations
Summary
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
"Onboarding isn’t a single event or process, it’s an ecosystem with many touchpoints impacting the new employee experience."
Russ UngerOnboarding: The Ecosystem, not the Afterthought
November 7, 2017
"A design ops career ladder can look like a step stool unless you create multiple tracks for growth and specialization."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
"You don’t know what you don’t know. Let’s write surveys that cover those blind spots."
Chris EngledowlA Mixed Method Approach to Validity to Help Build Trust
April 28, 2023
"Don’t cold reach out to people with ‘let’s connect’; instead, ask very specific questions about topics they care about."
Sara ConklinA UXer’s 12-Month Journey from Climate Concern to Climate Credibility
June 26, 2025
"Let's keep up those discussions in Slack—there's some really good stuff going on today."
Uday GajendarTheme Four Intro
June 6, 2023
"Development is often best supported through pragmatic peer activities—not just training or conferences."
Jason MesutShaping design, designers and teams
November 8, 2018
"We want to feel valued and find satisfaction in our daily work."
Kit UngerTheme 1 Intro
June 8, 2022
"Week one onboarding was like technology hazing week — dealing with too many systems and passwords."
Jose CoronadoFrom Zero to Hero
September 8, 2022
"Our job as design teams is to teach others what we do, not to feel insecure about sharing."
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017