Prioritizing Your Tasks: Methods That Actually Work

A task manager organizes; a method decides. Here's an honest overview of the major prioritization methods — what they're really worth, their limitations, and which one to adopt based on your situation.

Why do you need a method, not just a tool?

A tool solves storage and visibility; it doesn't decide for you what comes first. The method provides the decision rule. The two are complementary, and one without the other leaves the job half done.

A task manager without a method is like a neatly organized drawer where you still toss things in randomly. Having everything noted in one place solves half the problem — the part where you no longer forget anything. The other half remains entirely open: faced with a list of thirty things to do, which one do you tackle right now? No app can answer that question on its own. That's exactly what the methods below are for. There's nothing academic about them: most can be summed up in one sentence and applied in a few minutes.

The goal of this page isn't to get you to adopt one method wholesale, but to give you enough of a reference point to pick and choose what's useful from each.

How do you make sense of all these methods?

The simplest approach is to group them by function. Some help you decide what to do before what, others help you get to work, and still others help you see where each task stands — with one final category offering a complete system.

• Prioritize: Eisenhower matrix, MoSCoW, ABCDE, Pareto principle.
• Execute with discipline: Ivy Lee method, OHIO rule and the 2-minute rule, Pomodoro technique.
• Visualize the flow: Kanban.
• Full system: GTD (Getting Things Done).

This distinction helps avoid the most common confusion: thinking you have a prioritization problem when you actually have an execution problem, or vice versa. You can know perfectly well what to do and never start doing it — and that's not the same method that fixes both.

How does the Eisenhower matrix work?

The Eisenhower matrix classifies each task along two axes — its importance and its urgency — placing it in one of four quadrants, each calling for a different decision.

The principle attributed to Dwight D. Eisenhower, later popularized by Stephen Covey, comes down to one idea: importance trumps urgency. What's urgent grabs your attention; what's important moves the needle. Confusing the two means letting the ambient noise drive you — handling whatever shouts loudest rather than what actually matters.

Its strength lies in legitimizing two decisions we rarely make on our own: delegating and eliminating. Its limitations are real. The classification remains subjective, especially without a clear deadline, and you need to reclassify regularly as unexpected things come up. Reducing every task to just these two axes is inherently simplistic — but that's precisely what makes it quick to use.

What is the MoSCoW method?

MoSCoW classifies tasks or features into four categories based on their degree of necessity: Must (non-negotiable), Should (high value but not a blocker), Could (if time allows), and Won't (not this time).

Born in software development in the 1990s, it excels when trade-offs need to be visible and shareable. Its real contribution is often overlooked: it gives a framework for communicating what will not get done. The "Won't" owns a decision rather than leaving it vague, which saves you from having to justify yourself task by task. That's why it works particularly well in teams, for aligning expectations at the start of a project or sprint.

Eisenhower or MoSCoW: which one should you choose?

The two aren't in opposition — they don't answer the same question. Eisenhower classifies by intrinsic urgency and importance; MoSCoW classifies by value and feasibility within a given period.

In practice, Eisenhower works better for individual, day-to-day trade-offs — "where do I start today?" MoSCoW works better for a collective scope with a defined time frame — "what are we delivering this sprint, and what are we consciously setting aside?" There's nothing stopping you from using one in the morning and the other in a planning meeting.

What is the ABCDE method?

The ABCDE method, formalized by Brian Tracy, assigns a letter to each task based on its real consequences: A (serious if not done), B (minor), C (none), D (to delegate), E (to eliminate). Within a category, you can refine further: A1, A2, A3.

Its advantage over Eisenhower is that it reasons in terms of consequences rather than a felt sense of urgency — which leaves less room for subjectivity on the "important" axis. It's fast, works on a simple list, and is a solid alternative for those who find the matrix too theoretical.

What is the 80/20 rule (Pareto principle)?

The Pareto rule observes that, in many situations, roughly 20% of actions produce roughly 80% of results. Applied to tasks: identify the few high-impact actions and prioritize them above everything else.

This isn't really a classification method — more of a reflex to cultivate. Three questions are enough to trigger it:

• What are the two or three tasks that, if done today, would make everything else secondary?
• That report, those meeting notes, that meeting — is anyone actually using them?
• Could a five-minute call replace a two-hour meeting?

Its strength is in challenging "default" tasks — things you do out of habit that give the illusion of being busy without producing much. A note of honesty: the 80/20 ratio is a metaphor, not a mathematical law. There's no point trying to measure it precisely — the idea stands on its own. Pareto helps you judge the importance of a task; Eisenhower then helps you decide what to do with it.

What is the Ivy Lee method?

The Ivy Lee method comes down to one routine: each evening, write down the six most important tasks for the next day, rank them by priority, and when the day comes, work through them in order without moving on to the next one until the previous is finished.

No more than six. That constraint is the whole point: it forces you to prioritize before the day even begins. Unfinished tasks simply carry over to the next day. The method is anti-multitasking by design and gives you a clear heading from the moment you start — particularly useful if you begin your days unsure where to start. Its downside is its rigidity: it handles unexpected events poorly and only covers daily execution, not complex projects. The story of its origin at Bethlehem Steel — said to have earned a $25,000 fee — is widely repeated but rests on shaky sources; it belongs to management folklore more than established fact. The method itself, however, is solid.

What do the OHIO rule and the 2-minute rule mean?

Both say the same thing in two different forms: only touch an item once. OHIO stands for Only Handle It Once; the 2-minute rule (from GTD) sets the threshold: if an action takes less than two minutes, do it immediately rather than adding it to your list for later.

Reading the same email three times without replying takes longer than handling it once and for all. Every "I'll deal with it later" is a deferred cost and one more piece of mental clutter. These rules clear out your inbox and cut procrastination on small actions short. Their limit is clear: they apply to quick processing, not to long or complex tasks, which actually deserve to be scheduled rather than rushed.

Should you time yourself, or simply clear your head?

The Pomodoro technique — work for 25 minutes without interruption, then take a 5-minute break — formalizes an idea that is simpler and, at its core, more important than the timer itself: we prioritize poorly when we're saturated. The interval structure is just a means to an end; what really matters is stopping regularly.

The timer doesn't work for everyone. For tasks that require deep focus — coding, long-form writing, analysis — being cut off every 25 minutes is counterproductive. Rigidity can then hurt rather than help. Better to keep the principle than the mechanics.

Yet this principle is rarely presented as a prioritization tool, even though it is one. Looking up from your screen, taking a ten-minute walk, stepping outside, changing rooms: these breaks aren't wasted time. They restore the perspective you need to distinguish urgent from important — a distinction that collapses when you push through without breathing. The best prioritization decisions are rarely made with your nose to the grindstone. A problem that feels insurmountable at 5 p.m. sometimes resolves itself in two minutes the next morning, simply because your mind had a chance to decompress. Giving yourself those breathing moments isn't a luxury: it's a prerequisite for seeing your priorities clearly.

How does a Kanban board help with prioritization?

Kanban doesn't tell you what to do first — it shows you where each task stands. On a board divided into columns — at minimum To Do → In Progress → Done — each task is a card that moves from one column to the next.

Born at Toyota in the 1940s–1950s and since adapted for office work, its most useful concept is the work-in-progress limit (WIP limit): setting a maximum number of tasks allowed in the "In Progress" column. This constraint forces you to finish before you start, reveals bottlenecks, and cuts through scattered efforts. Its immediate visibility makes it an excellent team tool: it replaces verbal status updates with a state that's always current. But it doesn't stand alone — it tells you where each task is, not which one matters most. It's therefore paired with a prioritization method. A task manager like Octopussian integrates this type of board, onto which urgency or deadline filters can naturally be layered.

What is the GTD method (Getting Things Done)?

GTD is not a prioritization method but a complete attention management system. Its goal: empty your mind of everything that's running in the background by entrusting it to a reliable external system, so you can focus fully on what you're doing right now. Formalized by David Allen in 2001, it rests on five steps: capture everything that holds your attention, clarify what is actionable, organize into the right lists, review weekly, then engage based on context and available energy.

Three ideas are worth keeping even if you don't adopt the full system. The next action: always define the concrete next step ("call client Johnson to confirm the quote") rather than a vague project ("Johnson file"). The project vs. action distinction: anything that requires more than one step is a project, and a project without an identified next action is a stalled project. And the weekly review, often overlooked yet central: without it, the system degrades quickly.

GTD covers everything — capture, prioritization, execution, review — and genuinely relieves the mental load for people juggling many projects. In return, getting it set up requires an upfront investment and ongoing maintenance discipline. For most people, a minimal version (three lists and a weekly review) is more than enough.

What about more advanced methods: RICE, OKR?

These are team and strategy tools, not personal task management — useful to know, rarely necessary day to day.

RICE assigns each initiative a score = (Reach × Impact × Confidence) / Effort. Born on the software product side, it's used to rationally prioritize a backlog of competing initiatives. Relevant when you need to justify choices to others, but far too structured for a daily to-do list.

OKR (Objectives and Key Results), popularized by Intel and then Google, pairs a qualitative, inspiring objective with two to five measurable, time-bound key results. Watch out for a common misunderstanding: OKRs are not task lists — they are outcomes to observe. The actions needed to achieve them still live in the task manager. It's a team alignment instrument, not to be confused with an individual prioritization method.

Should you adopt one method or combine them?

Most of these methods can be combined, because they don't cover the same step. A common and effective setup: one method for prioritizing (Eisenhower or Pareto), one for executing (Ivy Lee), one for visualizing (Kanban) — all built on the habit of clearing your head to maintain perspective.

The opposite trap exists too: stacking methods until you spend more time maintaining the system than actually working. A simple setup that you actually stick to will always beat a sophisticated one abandoned after three weeks. The right approach is to start with a single method — the one that addresses your most pressing problem — and only add another when you feel the gap. A task manager then serves as the common foundation: it's where the priorities you've decided on become tracked, shared, and completed actions.

Which method should you choose for your situation?

There is no single best method in the abstract — only the one that fits your current problem. This table summarizes what each one solves, who it's for, and over what time horizon.

Key takeaways

• A tool organizes and makes things visible; the method decides what to do before what. Both are essential.
• Distinguish between methods that prioritize (Eisenhower, MoSCoW, ABCDE, Pareto) and those that help you execute (Ivy Lee, OHIO, breaks) — you can't fix an execution problem with a prioritization method.
• Eisenhower and MoSCoW aren't competing: urgency/importance on one side, value/feasibility over a period on the other.
• Beyond the Pomodoro timer, the real point is to take breaks and clear your head: that's where the perspective you need to prioritize well is restored.
• Combine carefully: one method per step, never more than you can sustain. A simple system maintained beats an elaborate one abandoned.
• GTD, RICE, and OKR are powerful but sized for complex or collective needs — there's no reason to adopt them just to manage a single day.