Priority Matrix Generator

Every prioritisation argument is really an argument about weights that nobody has written down. One person is optimising for impact, another for how quickly it can be finished, and the discussion goes in circles because those are different objectives rather than different opinions. Scoring the backlog against explicit weights does not remove the disagreement, but it moves it somewhere it can actually be settled — and effort counts against a task here, which is what stops one big worthy project outranking three you could ship this week.

Tasks or items to prioritise

One per line. Works well for a backlog, a to-do list or a set of proposals.

What makes something a priority

Weights are relative — 3 against 1 means three times as important. They are normalised to add up to 100%, and the share each one ends up with is shown below.

Score each one out of 10

Scores for each option against each criterion
Option	Impacthigher is better	Urgencyhigher is better	Effortlower is better	Confidencehigher is better
Task A
Task B
Task C
Task D

Score the options, then press the button.

What this generator does

Turns a backlog into an ordered list with the reasoning attached. The backlog picker on this site chooses something at random when you cannot decide; this ranks the whole list. Effort is set to lower-is-better by default, so a high effort score reduces a task's priority rather than raising it — which is the behaviour people expect and the one a naive weighted sum gets backwards.

How to use this tool

List the tasks, one per line.
Adjust the weights on impact, urgency, effort and confidence.
Score each task out of 10 against each.
Press score to get the ranked order.

Understanding the controls

Tasks: One per line. Works for a sprint backlog, a list of proposals, or a personal to-do list that has got out of hand.
Impact and urgency: Both higher-is-better. Impact is how much it matters if it is done; urgency is how much it matters if it is done *now*. They are genuinely different and worth weighting separately.
Effort: Lower-is-better by default, so a big task scores worse on it. Change the weight to control how much you want speed to influence the order.
Confidence: How sure you are of the other three scores. A high-impact task you are guessing about is a different proposition from one you have evidence for.

Worked examples

A quick high-impact task: Scores well on impact and, because effort is inverted, well on effort too.
A large speculative project: High impact, low confidence, high effort — usually ends mid-table, which is the honest answer.
Two tasks tied: Shown at the same rank rather than separated arbitrarily.
Changing the effort weight to zero: Ranks purely on value, which is a useful thing to look at once.

Common use cases

Ordering a backlog before a planning session
Deciding what to drop when a quarter is over-committed
Comparing proposals from different teams on the same basis
Making the case for a small quick win against a large slow one
Recording why the order was what it was, for the next planning session

How this generator works

The same weighted-sum engine as the decision matrix: weights normalised to sum to 1, lower-is-better criteria inverted, totals computed as the sum of score times normalised weight. Tasks that score identically share a rank. The sensitivity check tells you how far the weight on the first criterion would have to move before the top task changes, which is the quickest way to see whether the order is a real conclusion or an artefact of the weights.

Randomness and fairness

Nothing here is random. The same tasks, weights and scores always give the same order.

For how randomness is produced across the whole site, see how Generate Random works.

Assumptions this tool makes

Every task could in principle be done next — the order is about value, not about what is blocked.

Limitations and good to know

It ranks; it does not schedule. Two tasks that both must happen in a fixed order need the critical path calculator, not a priority score.
It has no knowledge of dependencies, deadlines or who is available.
Scores are yours. A team that scores optimistically gets an optimistic order.
The backlog and its scores vanish when the tab closes; copy the matrix if the ordering has to survive the planning session.

Common mistakes

Setting effort to higher-is-better: That makes hard tasks rank higher, which is almost never what anybody means. Leave it inverted unless you genuinely want to prioritise difficulty.
Scoring everything 8 to 10: If everything is high impact, nothing is. Use the full range or the order is noise.
Treating the output as the plan: It is an input to the conversation. Dependencies, deadlines and who is free will all reorder it, and should.

Practical tips

Agree the weights as a team before anybody scores a task.
Score confidence honestly — it is the field that stops a confident guess outranking a known quantity.
Rerun it with the effort weight at zero once, to see the pure-value order alongside the practical one.

Privacy and your data

Your task list and scores stay in your browser. Nothing is uploaded, nothing is stored between visits, and none of it is written into the page address — which matters for an unreleased roadmap. Analytics records that the tool ran and how many tasks were ranked, never any text.

Frequently asked questions

How is this different from the decision matrix?: Same arithmetic, different job. The decision matrix compares a few options you are choosing between; this ranks a whole list you are sequencing, and it comes set up with the four criteria most backlogs actually use.
Why does effort count against a task?: Because for the same value, less effort is better. Adding effort raw would rank the biggest task top, which is the opposite of prioritising.
Should the top item always be done first?: No. This scores value; it knows nothing about dependencies or deadlines. Use it to decide what is worth doing, then the critical path to decide what has to happen when.