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
"When GPT came out, my kids immediately adopted it at school and couldn’t pry it from their dead hands."
Peter Van DijckBuilding the Rosenbot
June 4, 2024
"The dominant frame became the personal narrative to contain the perspectives I wanted to serve up."
Kevin BethuneReimagining Design: Unlocking Strategic Innovation
June 8, 2022
"There's no such thing as over-communication when you're distributed; silence breeds assumptions."
Jilanna WilsonDistributed DesignOps Management
February 26, 2019
"You wanna do rapid research when the feedback or the findings is gonna be focused and impactful."
Feleesha SterlingBuilding a Rapid Research Program
May 18, 2023
"We are not replacing teachers; we are enhancing their ability to teach effectively."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"You can invite anyone in your family to attend the sponsor sessions for free even if they’re not registered."
Bria AlexanderOpening Remarks
March 28, 2023
"Getting stakeholders involved from the very beginning helps build buy-in and excitement around the research."
Roberta Dombrowski Sam Duong WoloszynskiMaking Research a Team Sport
March 11, 2022
"Most people would prefer to be foraging than work on a farm, but farmers kept taking all the land."
Dave GrayConnection, Community, and the Future of Work
May 28, 2026
"Secondary research can be time-saving, letting you spend more time on deep analysis rather than data collection."
Cara Maritz Rachel NyThe Art of Extrapolation
March 29, 2023
Latest Books All books
Dig deeper with the Rosenbot
What motivated Rachel Garb to write a concise book on AI for beginners post-retirement?
How can naming vulnerabilities in a team setting improve communication and accountability?
How can organizations prevent design system knowledge from being an undocumented API surface reliant on specific individuals?