Framework · DesignOps & capacity · 2 min read
Decision rights matrix
A table of who decides, who is consulted and who owns what between the central UX lead, the domains and the designers, so a hybrid team model doesn't turn into constant negotiation.
Decides UX staffing, shared standards, and designer hiring and growth.
Reviews quality of domain designsDecides which problems the domain solves: the product priorities.
Accepts the design solutionDecides and owns the design solution within the domain.
Contributes to shared standardsOne decider per row. Everyone else is consulted, contributes, reviews or is informed.
Use it when
- You run a hybrid model: designers report to UX but are embedded in domains, and they feel they have two bosses.
- The same question keeps coming back: "Who gets to say no to this design?"
- You start in a new lead role and want to agree with your manager which decisions you own.
How to use it
- List the recurring decisions. Collect the decisions that come up again and again: product priorities, UX staffing, shared standards, design solutions, hiring and growth. Add any that caused friction recently. Output: 5–10 decisions, one per row.
- Set the columns. Use the three parties in a hybrid model: UX lead (central), domain (product manager or product lead) and designer. Output: an empty matrix.
- Name one decider per row. Mark who decides, then mark the others as consulted, contributes, reviews or informed. If two parties want to decide, split the decision into two rows. Output: a draft matrix with exactly one decider in each row.
- Validate it with domain leads and your manager. Walk through each row and ask where they see it differently. Ask your manager which decisions they want to keep and which they expect you to own. Output: an agreed matrix.
- Publish it and use it in the moment. Put it in the UX wiki and point to it when a decision gets stuck: "Per our matrix, the designer owns this, and you review quality." Output: a shared reference that ends repeat debates.
Worked example
An internal operations platform with 6 product teams in a hybrid model. The UX lead drafts this matrix and validates it with domain leads.
| Decision | UX lead (central) | Domain (product manager / 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) | — |
In validation, one product lead wants to approve every design solution. The lead keeps the designer as owner and adds "Accepts" for the domain, so the product lead has a clear moment to say yes without redesigning.
Watch out for
- Two deciders in one row. "Decided together" means nobody decides. Split the row or pick one owner.
- Drafting it alone. A matrix the domain leads never agreed is just your opinion. Validate every row with them.
- Too many rows. A matrix with 30 decisions is never read. Keep the recurring and contested ones.
- Writing it and forgetting it. It only works if you point to it when a decision gets stuck. Review it when the team model or people change.
Template
Copy this into your UX wiki and fill one row per recurring decision.
Decision | UX lead | Domain | Designer
-------------------------------|---------|--------|---------
| | |
| | |
| | |
Key: D = Decides (one per row), C = Consulted, Ct = Contributes,
R = Reviews, A = Accepts, I = Informed
Validated with: on:
Next review: