Module 7 of 12 · 7 min read
DesignOps, Team Models & Capacity
How to choose a UX team model, set decision rights, build minimum viable DesignOps, and make capacity and prioritisation visible.
Why it matters
As a lead, you are now responsible for how the team works, not just what it designs. Two requests come up again and again: "make UX capacity and allocation more transparent" and "build a stronger central UX practice without losing the ties to products." That is DesignOps and org design (the Transparent capacity pillar in the course's example practice model).
For many new leads, capacity is the newest skill. As a designer, you managed your own workload; now you decide how scarce design time is spread across teams. Expect the question from stakeholders sooner or later: "Several teams need UX at once. What do you do?" Common pitfalls: saying yes to everyone, allocating by who shouts loudest, and making trade-offs privately so stakeholders never see them.
1. UX team models
| Model | How it works | Pros | Cons |
|---|---|---|---|
| Centralised (agency/pool) | Designers in one team, assigned to projects | Consistency, shared standards, flexible allocation, strong community | Designers lack domain depth; seen as a "service"; context switching |
| Decentralised / embedded | Designers report into product/domain teams | Deep domain knowledge, close to devs/product managers | Isolation, drift, inconsistent quality, no career path, "team of one" |
| Hybrid / centralised partnership (matrix) | Designers report to UX, are embedded long-term in domains | Domain depth + shared practice + UX career path | Two "bosses"; needs clear decision rights |
Many organisations move from decentralised → hybrid as their UX practice grows: they want a stronger central practice while keeping designers close to products. Merholz & Skinner argue the centralised partnership is the healthiest model for most organisations: designers report to design leadership but are assigned long-term to product teams.
Decision rights in a hybrid model
Make explicit who decides what. Without this, a hybrid model turns into constant negotiation.
| Decision | UX Lead (central) | Domain (product manager / product lead) | Designer |
|---|---|---|---|
| What problems the domain solves (product priorities) | Consulted | Decides | Consulted |
| How UX is staffed across domains | Decides (with stakeholders) | Consulted | Informed |
| Shared standards / design system | Decides (with designer community) | Consulted | Contributes |
| Design solution within a domain | Reviews quality | Accepts | Decides / owns |
| Designer hiring, growth, performance | Decides | Consulted (input) | — |
2. DesignOps: the three layers
NN/g's DesignOps framework groups the work into:
- How we work together. Team structure, roles, collaboration with product managers and developers, rituals.
- How we get our work done. Process standards, tools, workflow, quality, research ops.
- How our work creates impact. Measurement, communication, influence, maturity.
A minimum viable DesignOps for a set of internal apps:
| Area | Minimum standard |
|---|---|
| Intake | One shared request form/board for UX work |
| Capacity | A monthly capacity map: who works on what, % allocation |
| Process | "Definition of Ready for design" and "Definition of Done for design" |
| Quality | Cross-domain critique (bi-weekly); design QA checklist pre-handoff |
| Knowledge | One UX wiki: principles, patterns, research repository, decisions log |
| Tools | Figma org structure, library governance, plugin catalogue |
| Community | Monthly UX guild/show-and-tell; onboarding kit |
3. Capacity & resource allocation
Step 1 — Make demand visible
Intake fields: requesting domain, problem (not solution), users affected, business impact, deadline & why, dependencies, size estimate (S/M/L).
Step 2 — Make supply visible
Capacity map (month) Domain A Domain B Domain C DS/Practice Available
Designer 1 (Senior) 60% 20% 20%
Designer 2 (Mid) 80% 20%
Designer 3 (Junior) 70% 10% 20%
Keep ~15–20% unallocated for urgencies, practice work and learning. Explain to stakeholders why that buffer exists.
Step 3 — Prioritise with explicit criteria
RICE (Intercom): Reach × Impact × Confidence ÷ Effort.
Weighted scoring for internal UX requests (agree weights with stakeholders):
| Criterion | Weight | 1 | 3 | 5 |
|---|---|---|---|---|
| User impact (users × frequency × pain) | 30% | few/rare | moderate | many/daily |
| Business/operational value | 25% | low | medium | critical (cost, compliance) |
| Strategic alignment (UX vision/pillars) | 15% | none | partial | core |
| Risk of not doing (errors, compliance, rework) | 15% | low | medium | high |
| Effort (inverse) | 15% | L | M | S |
Alternatives: MoSCoW, Value vs. Effort 2×2, Cost of Delay / WSJF (if your organisation uses SAFe, speak that language).
Step 4 — Make trade-offs explicit, then decide with the right people
- Monthly/quarterly UX allocation review with domain leads: present demand vs capacity, recommend, let them see the trade-off.
- When saying "not now," say what would have to stop to do it: "We can start this in two weeks, or now if we pause the X redesign. Which matters more to you?"
Step 5 — Allocation patterns
| Pattern | When |
|---|---|
| Dedicated (designer stays in domain long-term) | Core, complex, high-change domains |
| Shared (one designer across 2 small domains) | Low-volume domains, but cap at 2 |
| Pool / flex | Short projects, peaks, audits |
| Enablement (design system + guidelines + office hours) | Domains without designers; devs build with DS |
| Tiger team | Cross-domain initiatives (e.g., a navigation shell) |
4. Rituals for a distributed UX team
| Ritual | Cadence | Purpose |
|---|---|---|
| UX team sync | Weekly, 30 min | Priorities, blockers, capacity changes |
| Design critique (cross-domain) | Bi-weekly, 60 min | Quality & shared learning |
| 1:1s | Weekly/bi-weekly | People (see module 04) |
| Show & tell / demo | Monthly | Visibility, celebration, cross-pollination |
| Design-system council | Bi-weekly/monthly | Contribution decisions (module 08) |
| Retro | Monthly/quarterly | Improve how the team works |
| Team health check | Quarterly | Measure what matters to people |
| Planning / allocation review | Quarterly | Capacity vs demand with stakeholders |
Distributed tips: async first (Loom/written updates), meeting-free focus blocks, rotate facilitators, document decisions in one place, meet in person 1–2×/year if budget allows.
5. RACI / DACI for clarity
DACI (Atlassian Team Playbook): Driver, Approver (one person!), Contributors, Informed. Use it for any cross-domain decision, e.g., "new table component standard":
- Driver: design-system designer
- Approver: UX Lead
- Contributors: designers from 3 domains, frontend lead
- Informed: all product managers
Why only one approver? Two approvers means nobody can decide alone, so decisions stall or get reopened.
Practice
Evidence to collect
Keep proof in your leadership log:
- Capacity map + prioritisation model (anonymised).
- A story of saying "not now" well, with the trade-off framing.
Read / watch
Library → DesignOps & org design: Org Design for Design Orgs, NN/g DesignOps 101 & framework, The DesignOps Handbook (InVision), Team Topologies (for working with platform/stream-aligned dev teams), Atlassian Team Playbook.
Talking about it
- "Several teams need UX at once. What do you do?" Walk through the five steps: make demand visible, make supply visible, score with criteria agreed in advance, show the trade-off, decide with the right people, and pick an allocation pattern. The key message: "I don't hide the trade-off; I make it visible so the right people decide."
- With your manager: bring the capacity map and the decision-rights table. Ask which decisions they want to keep, and which they expect you to own.
- With product managers: explain the 15–20% buffer before an urgency arrives, not during one.
- In a promotion or hiring conversation: tell one story of a "not now" that kept the relationship intact, and what the stakeholder decided when they saw the trade-off.
Check yourself
Answer out loud, then open the section to compare.
- What does a hybrid model need to work? → answer
- What are the five capacity steps? → answer
- What are the four DACI roles, and why only one approver? → answer
Connections
← Module 6: UX Strategy & Vision · UX Lead Course · Module 8: Design Systems & Standards Governance →
Related
- 11 — Workshop techniques: run a UX capacity & priorities session with domain leads
- Module 10: Stakeholders, Influence & Change: saying 'not yet' with trade-offs
- Module 8: Design Systems & Standards Governance: the design-system council as a ritual
- Module 4: People Leadership: 1:1s in a distributed team