Framework · DesignOps & capacity · 3 min read
Weighted scoring
Criteria and weights agreed with stakeholders before any request is scored, which makes UX prioritisation transparent and less political.
Users × frequency × pain.
1 few/rare · 5 many/dailyBusiness or operational value, such as cost or compliance.
1 low · 5 criticalAlignment with the UX vision and pillars.
1 none · 5 coreRisk of not doing it: errors, compliance, rework.
1 low · 5 highScored inverse: smaller work scores higher.
1 large · 5 smallScore = sum of (criterion score × weight), weights agreed before scoring
Use it when
- Several domains need UX at the same time and you have to explain why one goes first.
- Prioritisation feels political: the loudest stakeholder wins.
- You prepare a capacity and priorities session with product leads.
How to use it
- Agree the criteria and weights with stakeholders. Start from a standard set: user impact (users × frequency × pain), business or operational value, strategic alignment with the UX vision, risk of not doing it, and effort (inverse). Adjust the weights together, before any scoring. Output: an agreed criteria table with weights that add up to 100%.
- Define what 1, 3 and 5 mean. For each criterion, write short anchors (for example user impact: few/rare, moderate, many/daily). Anchors make scores comparable between people. Output: a scoring scale everyone reads the same way.
- Score in cross-domain pairs. Two people from different domains score each request together. This reduces bias towards your own domain. Output: a score per criterion for each request.
- Calculate and rank. Multiply each score by its weight and add them up. Sort the list. Output: a ranked list of requests.
- Discuss surprises, not every item. Look at the requests whose rank surprises people. Ask whether a score is wrong or a weight is wrong. Fix the model if needed. Output: an agreed ranking for the allocation review, plus any weight changes.
Worked example
An internal operations platform with 6 product teams. Domain leads agreed these weights last quarter: user impact 30%, business value 25%, strategic alignment 15%, risk of not doing 15%, effort (inverse) 15%. Three requests compete for one designer.
| Request | User impact | Business value | Strategic | Risk | Effort (inv.) | Weighted score |
|---|---|---|---|---|---|---|
| Shareable delay view (orders) | 5 | 3 | 3 | 3 | 3 (M) | 3.6 |
| Audit fields for a compliance check (billing) | 3 | 5 | 1 | 5 | 5 (S) | 3.8 |
| Dashboard redesign (reporting) | 3 | 3 | 5 | 1 | 1 (L) | 2.7 |
Weighted score = sum of (score × weight). For the delay view: 5×0.30 + 3×0.25 + 3×0.15 + 3×0.15 + 3×0.15 = 3.6.
The surprise is that the small compliance request beats the delay view. The group checks the scores, agrees they are right, and plans the compliance work first because it is small and the risk is high. The dashboard redesign goes to "not now", with the reason visible to its domain lead.
Watch out for
- Weights set after scoring. It turns the model into a justification for a decision you already made.
- Scoring alone. One person's scores reflect one person's view. Score in pairs from different domains.
- False precision. 3.6 against 3.8 is close. Use the scores to start the conversation, not to end it.
- Never revisiting the weights. If the ranking keeps feeling wrong, a weight is probably wrong. Review the weights with stakeholders each quarter.
Template
Copy this into a shared sheet. Agree the weights first, then score.
Criterion Weight 1 3 5
User impact (users x frequency x pain) 30% few/rare moderate many/daily
Business / operational value 25% low medium critical
Strategic alignment (UX vision/pillars) 15% none partial core
Risk of NOT doing (errors, compliance) 15% low medium high
Effort (inverse) 15% L M S
Request | Impact | Value | Strategic | Risk | Effort | Weighted score
| | | | | |
Weights agreed with: on:
Scored by (pairs):
Surprises to discuss: