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
"Many federal benefit programs face challenges verifying income, causing stress and leaving billions in unclaimed benefits."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"Unfortunately, that was very good."
Dan WillisEnterprise Storytelling Sessions
June 8, 2017
"Remote research is not a silver bullet."
Sarah RinkRemote User Research: Dos and Don'ts from the Virtual Field
June 11, 2020
"Leadership public recognition of time spent engaging with research is a powerful way to give people permission to participate."
Crystal YanBuilding a Customer-Centric Culture
March 30, 2020
"The tools are more important than ever even if the title UX becomes less central."
Greg PetroffExit Interview #1: Greg Petroff: From Silicon Valley Executive to Sonoma County Possibilitarian
September 24, 2025
"Taxonomy and controlled vocabulary help the system map user language to internal concepts and improve tool selection."
Paz PerezContext Architecture for AI systems
September 11, 2026
"We could not have this conference without you all — the curation team relies heavily on audience participation."
Bria AlexanderOpening Remarks
September 9, 2022
"Don't just throw a URL at someone without context, explain why it’s interesting."
Nick CochranGrowing in Enterprise Design through Making Connections
June 20, 2019
"Synthetic participants shouldn't be used as a methodology but are great for cold starting research."
Erin Weigel Petra RajkovTesting and Experimentation Tools
March 12, 2026
