Design system request scorecard
Score every component request with the same four questions: where it's needed, who can reuse it, whether you have it already and how hard it is. Get a ranked backlog with clear verdicts you can share with teams.
- Free, no sign-up
- Runs in your browser
- Saves as you go
Any “✕” answer rules a request out. 55+ is high, 40–54 medium, below 40 deferred.
How to use it
- Name the request
What's being asked for, and by which team.
- Answer four questions
Each answer adds points; any answer that rules it out ends the scoring.
- Share the ranking
The backlog sorts itself. Export it for your planning or docs.
The four questions
| Question | Points | Rules it out when… |
|---|---|---|
| Where is it needed? | Main products 20 · smaller products 15 · one team 5 | It's needed nowhere yet |
| How many teams can reuse it? | Many 20 · a few 15 · one 5 | Only one product will ever use it |
| Do we already have it? | No 15 · partly 10 · mostly 5 | It's already fully solved |
| How hard is it to build? | Under a week 15 · 1–3 weeks 10 · 3+ weeks 5 | It isn't worth the effort |
55 or more is high: the system team builds it first. 40 to 54 is medium: accept it after high-priority work, ideally as a contribution. Below 40, defer: the team builds it as a local component, which can be promoted later if a second team needs it.
The model comes from the CARS24 governance work, where one front door and a shared scorecard let any team see why a request was ranked where it was.
Questions
How do you prioritise design system requests?
Score each one with the same questions: how widely it's needed, how many teams can reuse it, whether it exists already and how hard it is. Rank by score, and publish the reasons.
What happens to low-scoring requests?
They're deferred, and the requesting team builds a local component. If a second team needs it later, it can join the system.
Can I change the scoring?
Not in the tool yet, but the export gives you every answer, so you can re-weight in a spreadsheet.
Our two-week audit turns your real screens into a token plan, a first-components list and a rollout plan.