How to prioritize tasks: five methods and when each one fails
The methods are not the hard part. Urgency bias and optimistic estimates are. This guide compares five methods on the same criteria and tells you which one fits your situation.
Every guide to prioritising tasks lists the same methods. Few say which one to use, and none that we found explain why prioritising is hard in the first place. The difficulty is not a shortage of frameworks. It is that urgency captures attention independently of value, that people underestimate how long everything takes, and that most methods were designed for a context (a software team, a product backlog, a single busy executive) that may not be yours. This guide compares five methods on the same criteria, summarises the research that bears on them, and gives a decision guide for choosing one. It sits between our guides to the Eisenhower matrix, which covers one method in depth, Getting Things Done, which supplies the lists a method sorts, and time blocking, which gives the chosen tasks a place in the calendar.
Why prioritising is hard
Four findings explain most failed to-do lists.
| Finding | Evidence | Consequence for prioritising | Grade |
|---|---|---|---|
| Urgency beats importance even when both fit | In five experiments, people chose urgent tasks with smaller payoffs over important tasks with larger payoffs although they had time for either; the effect was strongest in those who felt busiest and weakened when payoffs were made visible at the moment of choice [1] | Any method that does not force you to look at value before deadline reproduces the bias; writing the payoff next to the task counteracts it | B |
| Estimates are optimistic, knowingly | Students predicted when they would finish their theses; most finished later than predicted, and even their "worst case" estimates were often exceeded [2] | A ranked list of twelve tasks that "fit this week" usually contains six that fit. Prioritising is also deciding what not to do | B |
| Specific goals outperform vague ones | Across roughly four decades of studies, specific, difficult goals produced higher performance than "do your best", given commitment and feedback [3] | "Work on the proposal" cannot be prioritised; "send the proposal draft to Ana by Thursday" can | A |
| Time management helps wellbeing more than output | A 2021 meta-analysis found time management moderately related to performance and more strongly to wellbeing [4]; the field's methods review found the literature short of theory and inconsistent in how it measures planning and prioritising [5] | No method has been tested against a control. Expect lower strain and a clearer week; do not expect a method to make you faster | A |
The environment adds pressure: in Microsoft's 2025 telemetry across 31 markets, employees were interrupted every two minutes on average, around 275 times a day [6]. Interrupted work in a lab simulation was finished faster but with more stress and effort [7]. A prioritisation method is partly a defence against re-deciding your day each time something arrives.
Five methods compared
The criteria are the same for each: how it scores, what it was designed for, where it fails, and what evidence bears on it.
| Method | How it ranks tasks | Designed for | Where it fails | Evidence |
|---|---|---|---|---|
| Eisenhower matrix | Two yes/no questions, urgent and important, giving four quadrants: do, schedule, delegate, drop | One person's week; triage | Binary boxes flatten tenfold differences; no effort or dependency dimension; Q2 loses unless it is scheduled | The bias it fights is documented [1]; the grid itself is untested B |
| MoSCoW | Four buckets: must have, should have, could have, won't have (this time) | Scope negotiation on a fixed-deadline delivery, from 1990s software practice | Everything migrates to "must"; no ranking inside a bucket; nothing about sequence or value | None specific; a communication device rather than a scoring method C |
| ICE and RICE | Score each item on impact, confidence and ease (ICE), adding reach for RICE; rank by the product or ratio | Product backlogs with many comparable ideas | False precision from guessed numbers; confidence is rarely calibrated; favours small safe items | None specific; the value of making payoffs explicit is supported [1] C |
| WSJF (weighted shortest job first) | Cost of delay divided by job duration; do the highest ratio first | Teams with a queue of work where delay has a measurable cost | Needs honest duration estimates, which are optimistic [2]; cost of delay is hard to put on personal tasks | Queueing logic is sound; no trials in knowledge work C |
| Weekly big three (with a daily highlight) | Choose three outcomes for the week and one task per day; everything else is secondary | Individuals and small teams; combining with GTD or a calendar | Three is arbitrary; without estimates the three can still exceed the week; needs a review to work | Specific goals and if-then plans are well supported [3][8]; the count of three is not B |
A pattern shows up across the table. The scoring methods (ICE, RICE, WSJF) are strongest where items are many, comparable and owned by a team. The sorting methods (Eisenhower, big three) are strongest where items are few, varied and owned by one person. MoSCoW is a negotiation tool wearing a prioritisation costume: its job is to make "won't have" sayable to a stakeholder.
Decision guide
Answer in order; stop at the first match.
- Are you prioritising for a team with a shared queue, and does delay have a cost you can estimate? Use WSJF. Publish the cost-of-delay assumptions so the ranking can be argued with rather than ignored.
- Is the list long (roughly fifteen items or more), are the items comparable, and do you need a defensible order? Use RICE, or ICE if reach is the same for everything. Re-score monthly; the first scores are guesses.
- Is the real problem that a stakeholder wants everything by the date? Use MoSCoW for the conversation, then one of the other methods for your own order within "must" and "should".
- Do you feel busy all the time and suspect the urgent is eating the important? Use the Eisenhower matrix weekly, and write the payoff of each quadrant-2 task next to it [1]. Schedule quadrant 2 into the calendar, or it loses.
- Otherwise, and for most individuals: use a weekly big three with a daily highlight. Give each outcome a definition of done [3] and a slot in the calendar [8].
Two rules apply to every branch. First, estimate duration for anything that makes the shortlist, then add a margin, because the shortfall is predictable [2]. Second, keep the chosen items visible at the moment you decide what to do next, since the urgency bias weakens when value is in view [1].
Worked example
A freelance designer starts Monday with twelve items. Six matter for the week; the rest are small.
| Task | Deadline | Value if done this week | Estimate | Method verdict |
|---|---|---|---|---|
| Finish client A's brand guidelines | Friday, contractual | High (final invoice, 40 percent of the project) | 10 h | Big three, item 1. Blocked Tuesday and Thursday mornings |
| Proposal for prospect B | None stated | High (new project, if won) | 4 h | Big three, item 2. Quadrant 2: important, not urgent, so it gets Wednesday morning before anything can displace it |
| Portfolio update | None | Medium, cumulative | 6 h | Deferred to next week; written on the list with a reason, so it does not nag |
| Reply to client C's revision requests | "ASAP" | Medium | 2 h | Urgent and important, but 2 hours, not the week: Monday afternoon admin batch |
| Quarterly tax filing | 15th | High (penalty), low effort | 1.5 h | Big three, item 3, because the cost of delay is real |
| Newsletter draft | Self-imposed | Low this week | 3 h | Won't have this week; moved to the someday list |
Twelve tasks became three outcomes, one admin batch and two explicit deferrals. The estimated 15.5 hours for the big three fit a week with meetings only because the portfolio and newsletter were deferred, and because the estimates were written down to be checked on Friday.
Prioritising with a team
Individual methods break in a team for a simple reason: everyone's quadrant 1 is someone else's quadrant 3. Three practices help.
- Make the criteria public. Whichever method you use, write the scoring rules where the team can see them. The purpose is not precision; it is to move the argument from "my task is more urgent" to "which assumption is wrong".
- Separate the queue from the week. A team queue (RICE or WSJF) answers what comes next. Each person's week still needs a personal layer (big three or Eisenhower), because the queue does not know about their meetings, energy or the three small urgent things that arrived on Monday.
- Review the ranking on a cadence, not on demand. Re-prioritising every time a request arrives recreates the interruption cost [7]. A weekly re-rank with a short mid-week check is enough for most small teams.
Demand note: who searches for this
In the United States "how to prioritize tasks" draws about 1,300 searches a month with a keyword difficulty of 15 and a cost per click of $7.97, down 58 percent year on year and declining about 19 percent a year over three years (DataForSEO, retrieved 2026-11-09) [9]. The term is not among the forty we tracked in UK, German, French, Spanish and Czech data, so this page has no localised version yet.
What to do next
Pick the branch of the decision guide that fits, then build the week around it. The OS Builder asks about your role, team size, inputs and obstacles (unclear priorities and interruptions among them) and recommends one of four priority systems, a weekly big three with a daily highlight, an Eisenhower triage, a GTD-style capture and review loop, or a Kanban board with work-in-progress limits for teams, together with a weekly rhythm that gives the chosen tasks their calendar slots and a four-week checklist for putting it in place.
Frequently asked questions
What is the best way to prioritize tasks?
For most individuals, a weekly big three with a daily highlight, each with a definition of done and a calendar slot, because specific goals and if-then plans are the best-supported components in the research [3][8]. Teams with a shared queue do better with a scoring method such as WSJF or RICE. No method has been tested against a control group, so choose by fit, not by claimed results.
Why do I always do urgent tasks instead of important ones?
Because urgency captures attention independently of value. In five experiments people chose urgent, lower-paying tasks over important, higher-paying ones even when they had time for both, and the effect was strongest in people who felt busiest [1]. Writing the payoff of the important task where you can see it at the moment of choosing reduced the effect.
What is the difference between MoSCoW and the Eisenhower matrix?
MoSCoW sorts work into must, should, could and won't have for a fixed delivery and is mainly a tool for negotiating scope with stakeholders. The Eisenhower matrix sorts by urgency and importance for one person's week. MoSCoW says what is in the release; Eisenhower says what you do on Tuesday.
When should I use RICE or WSJF?
When the list is long, the items are comparable and the ranking has to be defended to other people. RICE scores reach, impact, confidence and effort; WSJF divides cost of delay by duration. Both depend on estimates, which are optimistic by default [2], so re-score on a cadence and publish the assumptions.
How many priorities should I have per week?
Three outcomes is a common and workable number, though nothing in the research fixes it. What matters is that each has a definition of done [3], an estimated duration with a margin [2] and a place in the calendar [8], and that you record what was deferred and why so it stops competing for attention.
Sources and evidence
- The Mere Urgency Effect — Zhu, M.; Yang, Y.; Hsee, C. K. (2018), RCT B doi.org/10.1093/jcr/ucy008 (retrieved 2026-11-09)
- Exploring the "planning fallacy": Why people underestimate their task completion times — Buehler, R.; Griffin, D.; Ross, M. (1994), RCT B doi.org/10.1037/0022-3514.67.3.366 (retrieved 2026-11-09)
- Building a practically useful theory of goal setting and task motivation: A 35-year odyssey — Locke, E. A.; Latham, G. P. (2002), review A doi.org/10.1037/0003-066X.57.9.705 (retrieved 2026-11-09)
- Does time management work? A meta-analysis — Aeon, B.; Faber, A.; Panaccio, A. (2021), meta-analysis A doi.org/10.1371/journal.pone.0245066 (retrieved 2026-11-09)
- A review of the time management literature — Claessens, B. J. C.; van Eerde, W.; Rutte, C. G.; Roe, R. A. (2007), systematic review B doi.org/10.1108/00483480710726136 (retrieved 2026-11-09)
- 2025 Work Trend Index Annual Report: The year the Frontier Firm is born — Microsoft WorkLab (2025), report B www.microsoft.com/en-us/worklab/work-trend-index/2025-the-year-the-fro (retrieved 2026-11-09)
- The cost of interrupted work: more speed and stress — Mark, G.; Gudith, D.; Klocke, U. (2008), RCT B doi.org/10.1145/1357054.1357072 (retrieved 2026-11-09)
- Implementation Intentions and Goal Achievement: A Meta-analysis of Effects and Processes — Gollwitzer, P. M.; Sheeran, P. (2006), meta-analysis A doi.org/10.1016/S0065-2601(06)38002-1 (retrieved 2026-11-09)
- Keyword database: DataForSEO Labs keyword overview and historical search volume, US/UK/DE/FR/ES/CZ (data/research/keywords) — Productivity Signal research (2026), dataset A dataforseo.com/apis/dataforseo-labs-api (retrieved 2026-11-09)