Your list is never empty. Tasks accumulate faster than they get done, and the feeling of overwhelm is rarely about volume — it’s about the absence of a clear order. Prioritisation is the practice of establishing that order: ranking your activities so that your best energy goes to your most important work, every time.
“What is important is seldom urgent, and what is urgent is seldom important.” — Dwight D. Eisenhower
Why we prioritise badly
Left unmanaged, most people prioritise by recency (whatever arrived last gets done first), by comfort (easier tasks get done before harder ones), or by whoever shouted loudest. None of these produce good outcomes over time. A framework replaces instinct with a repeatable, defensible system.
The five core frameworks
Each framework uses a different lens to rank work. The right one depends on your context — whether you’re managing a personal task list, a team backlog, or a strategic roadmap.
The Eisenhower Matrix is the most intuitive starting point. Its power is the distinction between Q2 (important but not urgent) and Q1 (important and urgent) — most people neglect Q2 entirely, which means they spend their lives firefighting.
Choosing and weighting your criteria
Every framework above relies on you assessing tasks against criteria. The criteria you choose — and how heavily you weight them — determine whether your prioritisation reflects reality or just feels systematic.
The goal is not to use every possible criterion. It’s to identify the 3–5 that genuinely distinguish important work from unimportant work in your specific context, then score consistently against those.
A catalogue of prioritisation criteria
Criterion | What it asks | Weight it highly when… |
|---|---|---|
Impact / value | How much does this move a key metric or goal? | Your objectives are clear and measurable |
Urgency / time constraint | Is there a hard external deadline? | You have contractual or dependency-driven commitments |
Effort / complexity | How much time and resource does this consume? | Capacity is your binding constraint |
Strategic alignment | Does this serve the long-term direction? | You’re building a roadmap or annual plan |
Reach / audience size | How many people does this affect? | You’re prioritising product or service improvements |
Risk / reversibility | What happens if this goes wrong? | Stakes are high or mistakes are hard to undo |
Dependencies | Does something else block or need this first? | You’re working in a team or complex project |
Confidence | How certain are our estimates of impact and effort? | Operating in uncertain or novel domains |
Rule of thumb
Use 3–5 criteria per scoring exercise. More than that and everything regresses toward the mean — the model stops differentiating tasks and just creates administrative overhead.
How weighting works in practice
Once you’ve chosen your criteria, assign each a weight that reflects its relative importance. Below is how the weighting shifts across three common contexts — the same task might score very differently depending on which lens you apply.
Context | Top-weighted criteria | Rationale |
|---|---|---|
Solo operator | Impact, Effort, Urgency | Output-per-hour and cash flow are the binding constraints; anything that doesn’t move a key number or pay the bills gets deprioritised |
Product team | Reach, Strategic alignment, Confidence | Features serve many users; team must agree on direction and be realistic about what estimates to trust |
Risk-sensitive org | Risk level, Reversibility, Compliance | Mistakes are costly or irreversible; impact matters far less if the approach could cause harm or regulatory exposure |
Key insight
Start by asking: “What does a bad outcome look like in my context?” Then weight the criteria that would have predicted and prevented it. Your weights encode your risk model.
Matching framework to context
Context | Use this framework | Because… |
|---|---|---|
Personal task list | Eisenhower Matrix | Fast, visual, no scoring needed |
Team sprint planning | MoSCoW | Aligns team on minimum viable scope |
Product roadmap | RICE | Incorporates user reach and confidence |
Many options, limited time | ICE Score | Quick to score, easy to compare |
Team workshop / stakeholders | Value vs Effort Matrix | Visual, creates shared understanding fast |
Building the prioritisation habit
A framework applied once is a novelty. Applied consistently, it becomes a system. The goal is a lightweight weekly rhythm that keeps your list in order without consuming your whole Monday.
- Weekly capture (10 min)
Empty every open loop — inbox, notes, memory, messages — into one flat list. Capture without judgement. Nothing gets prioritised yet.
- Score or sort against your criteria (15 min)
Apply your chosen framework. A simple high / medium / low pass is enough. The point is to create a ranked order, not a perfect score. Resist marking everything high.
- Identify your “one thing” (5 min)
If the week went sideways, what single item would make it feel like a success? That goes to the top of Monday. Everything else works around it.
- Friday calibration (10 min)
What got done? What didn’t? Were your impact or effort estimates accurate? Review your scores against what actually happened. This is where your model improves over time.
“You can do anything, but not everything.” — David Allen
Prioritisation is not a one-off exercise. It’s a practice — and like any practice, it compounds. The more consistently you apply a framework, the more accurate your scoring becomes, and the less time you spend agonising over what to work on next.
Start with one framework. Apply it for a month. See what it reveals about your habits. Then refine.
For frameworks on choosing between options or making high-stakes calls, see the companion post on decision-making frameworks.