<aside> π‘
Use this table to decide what to fix first.
Score each issue for impact (how much it helps users) and effort (how hard it is to do). The tool adds the scores together and shows you which tasks should happen now, next, or later. Update the list as new issues come up and sort by the highest score to see your top priorities.
</aside>
Impact
How much this change helps users use your website or service.
| Score | Meaning |
|---|---|
| 3 | High impact β solves a common problem or removes a major barrier |
| 2 | Medium impact β improves something noticeable but not critical |
| 1 | Low impact β helpful, but not urgent |
Effort How much work, time, or coordination is needed to fix it.
| Score | Meaning |
|---|---|
| 1 | Low effort β quick win or simple fix |
| 2 | Medium effort β needs some time or cross-team help |
| 3 | High effort β requires planning, budget, or technical support |
<aside> π‘
Impact score + (4 β Effort score)
This rewards high impact and low effort in a simple way.
(The number 4 is used to turn the effort score around, as itβs one more than the highest effort rating.)
Example:
Impact: 3
Effort: 1
Score: 3 + (4 β 1) = 6
</aside>
High Priority (Score 5β6): Fix these first β they help the most users with the least effort.
Medium Priority (Score 3β4): Important, but not urgent. Plan these in your next cycle.
Low Priority (Score 1β2): Nice to have. Do these only when time and resources allow.
<aside> π‘
The table below includes sample data only β replace these with your own tasks.
</aside>
Created by Mugs Studio β www.mugs.studio
Need help improving your website?