This prioritisation framework is used to score and prioritise requests in our design system.
Each change is scored based on the 4 criteria below. For each criteria the request is scored as either low, medium or high priority. A total score is determined by the points accumulated from all 4 criteria. The total score determines the priority of the request.
The criteria are weighted so that the relative importance of each question is reflected in the total score. If any of the criteria score as Won't fix the request will be rejected.
These are the criteria at a glance - make sure to read the Criteria in detail below, to score each appropriately.
| Criteria | 🟢 High | 🟡 Medium | 🟠 Low | ❌ Won’t fix |
|---|---|---|---|---|
| 1️⃣ Product area | 15 points | |||
| [Team A], [Product A], [Project A] | 10 points | |||
| [Team B], [Product B], [Project B] | 0 points | |||
| [Team C], [Product C], [Project C] | ❌ | |||
| [Team D], [Product D], [Project D] | ||||
| 2️⃣ Reusability | 15 points | |||
| Impacts most end-users and many product teams will benefit from it. | 10 points | |||
| Impacts a majority of the end-users and a few product teams will benefit from it | 0 points | |||
| Impacts a minority of end-users and only one feature team or use-case has been identified. | ❌ | |||
| 3️⃣ Existing options | 10 points | |||
| There are no existing solutions | 5 points | |||
| Existing solutions exist but something is missing | 0 points | |||
| Existing solutions are sufficient (even if not preferred) | ❌ | |||
| 4️⃣ Estimated effort | 10 points | |||
| <3 man days | 5 points | |||
| 4-9 man days | 0 points | |||
| 10+ man days | ||||
| ❌ |
Tally up the scores from the criteria to determine the final priority
Note: points are only awarded in multiples of 5 points, hence the priority ranges reflect this.
| Priority | Score (range) | Description |
|---|---|---|
| 🟢 High | 40-50 | High priority requests are most likely to be picked up by our team as soon as our bandwidth allows. |
| 🟡 Medium | 30-35 | Our team will pick these up if we are running out of high-priority requests. Contribution is encouraged if teams are pending the changes in the short to mid term. |
| 🟠 Low | 15-25 | Low priority requests are unlikely to be picked up by our team. Contribution is encouraged for these. |
| ❌ Won’t fix | 0-10 or if any consideration in any criteria is rated as Won't fix. | The request will not be picked up by our team and contributions won't be accepted. The requesting team is encouraged to consider a more scalable solution or design and build the change outside of the design system, using the design language. |