Framework · DesignOps & capacity · 3 min read
UX team models
Three ways to organise designers (centralised pool, decentralised/embedded, or hybrid where designers report to UX and sit long-term in domains), so you can name your model and fix its weak spot.
Designers in one team, assigned to projects. Consistent, flexible, strong community.
Risk: shallow domain depth, "service" imageDesigners report into product or domain teams. Deep domain knowledge, close to developers.
Risk: isolation, drift, no career pathDesigners report to UX and are embedded long-term in domains.
Risk: two bosses without decision rightsHybrid = domain depth + shared practice + UX career path, if decision rights are explicit
Use it when
- You join an organisation and need to describe how the UX team is set up today.
- Leadership asks for "a stronger central UX practice without losing the ties to products".
- Designers embedded in product teams feel isolated, or quality drifts between domains.
How to use it
- Name your current model. Ask who designers report to and where they spend their days. Centralised: one team, assigned to projects. Decentralised: designers report into product or domain teams. Hybrid: designers report to UX and are embedded long-term in domains. Output: one sentence describing today's model.
- List the symptoms you see. Match what you observe to the known cons: shallow domain knowledge and a "service" image (centralised); isolation, drift, no career path, "team of one" (embedded); two bosses (hybrid). Output: the problems your model is causing, with examples.
- Choose the target model. Many organisations move from decentralised to hybrid as UX grows. Merholz & Skinner argue the centralised partnership (hybrid) is the healthiest model for most organisations. Check that it fits your size and goals. Output: a target model and the reason for it.
- Make decision rights explicit. For a hybrid model, agree who decides product priorities, UX staffing, shared standards, design solutions, and hiring and growth. Use a decision rights matrix. Output: an agreed decision-rights table.
- Add the rituals that hold it together. A weekly UX sync, a cross-domain critique and a show and tell keep embedded designers connected to the practice. Output: a ritual calendar for the team.
Worked example
An internal operations platform with 6 product teams. Five designers report to different product managers. Each domain has its own patterns, and two designers say they have no one to learn from.
| Model | What it would mean here | Fit |
|---|---|---|
| Centralised | All five in one UX team, assigned project by project | Fixes consistency, but loses the domain depth the complex domains need |
| Decentralised (today) | Stay as they are | Keeps depth, but the drift and isolation continue |
| Hybrid | Designers report to the UX lead, each stays long-term in their domain | Keeps depth and adds a shared practice and career path |
The UX lead proposes hybrid, with a decision rights matrix agreed with the product managers before anyone changes reporting lines.
Watch out for
- Hybrid without decision rights. Designers get conflicting direction from the UX lead and the product manager. Agree the table first.
- Centralising too far. A pure pool can make designers feel like a ticket service with shallow domain knowledge.
- The "team of one". An embedded designer with no peers loses quality and motivation. Connect them through critique and community.
- Changing the model without explaining why. People hear "reorg". Explain the problems you are solving and what stays the same.
Template
Copy this into a proposal doc.
Current model: Centralised / Decentralised (embedded) / Hybrid
Who designers report to today:
Symptoms we see (with examples):
-
-
Target model:
Why this model fits us:
Decision rights agreed with: (link to matrix)
Rituals that connect the team:
What stays the same:
- Org Design for Design OrgsPeter Merholz & Kristin SkinnerBook · 2016 (Amazon)
- Team TopologiesMatthew Skelton & Manuel PaisBook · 2019 (Amazon)
- Where Should UX Report? 3 Common ModelsNN/g (external site)
- Managed-UX IntegrationNN/g (external site)
- Designing your Design OrgSkinner & MerholzVideo (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.