How to Prioritize Tasks at Work

What does prioritizing at work actually mean?

Prioritizing at work means deciding which tasks get your attention today and which ones wait. That is a smaller definition than most people expect. It is not about working faster, and it is not about clearing a list; it is about ranking the list so the work you finish is the work that mattered most. Every method on this page is a different way of producing that ranking, and every one of them assumes you will leave some tasks undone on purpose.

The split most of them lean on is urgency against importance. An urgent task has a deadline attached, or a person waiting, and it announces itself. An important task moves a goal you actually own, and it usually sits in the background with no deadline at all. The Eisenhower Matrix rests on the urgent-versus-important split that Stephen Covey built Habit 3 of The 7 Habits of Highly Effective People around, and the reason that split survived is that both questions are small enough to ask about any task, in any week.

In practice the ranking gets tested by other people rather than by you. Two colleagues send requests within an hour of each other and both describe theirs as blocking. A manager stops by with a quick ask that turns out to be an afternoon. Two deadlines that sat comfortably apart in the plan collide because one project slipped a week. None of those are failures of effort. They are ordering problems, and effort applied in the wrong order just produces more finished work that nobody was waiting for.

The quick ask deserves its own warning. Requests that arrive with the word quick attached are rarely quick, and they almost never carry the context that would let you judge their real weight. Before one displaces something already ranked, it is worth asking what it is for and when it is genuinely needed, because the honest answer is often later than the request implies. A ranking that any passing request can reset is not a ranking; it is a queue in arrival order.

That is also why prioritizing is a routine rather than a single decision. You will do it again tomorrow, and the tomorrow version has to work on a day when three things went wrong before lunch. The five methods below are all built to be repeatable at that low cost: a few minutes with a grid, a list capped at six tasks, or one task named the evening before. If none of them fits the problem you actually have, the other families of methods on the hub approach the same day from a different angle, through focus, planning or habits.

How do you choose a prioritization method?

Start from the friction, not from the method. All five produce a ranking, but they produce it in different ways and at different costs, and the one that fits is usually the one that answers the question you keep getting stuck on. What follows is the mapping this site uses: friction first, working style second.

If the problem is too many inputs arriving from too many directions, start with the Eisenhower Matrix. Sorting each task into one of four quadrants forces the urgency question and the importance question to be asked separately, which is exactly what a crowded inbox blurs together. It rewards people who like structure, which on this site means the Architect, and the Visionary who wants to see how today's work maps onto a longer goal. It costs a few minutes of sorting before it saves any, so it suits people who are willing to plan on paper.

If the problem is that everything on the list looks equally worthwhile, try the Pareto Principle. It asks a single question - which small share of this work produces most of the result you care about - and then asks you to protect time for that share first. The 80/20 shorthand is a heuristic rather than a measurement, and this site names it as one. It suits people who think in outcomes rather than in tasks, which is why it lands well with Visionaries and with Improvisers who do not want a daily ritual to keep up.

If the problem is that each morning starts with re-deciding what to do, the Ivy Lee Method is the cheapest fix on this page. You write six tasks the evening before, rank them, and work them in that order. There is no grid and no analysis; the whole decision happens once, at a moment when the day is already over and nothing new can arrive to change it. It suits Architects who want a plan waiting for them in the morning, and Sprinters who would rather start working than start choosing.

If the problem is that the biggest task keeps sliding to tomorrow, Eat That Frog puts it first by rule. You name the task you are most likely to put off, and you do it before anything else in the workday; Brian Tracy's book of the same name is where the phrase comes from. It suits people whose mornings are genuinely theirs to control, and people who work in bursts. A Sprinter can spend one strong block on the frog and treat the rest of the day as lighter work.

If the problem is a calendar broken into fragments by other people's meetings, the Pickle Jar Theory is the one built for that shape of week. It has you place the big items into the schedule first and let the small ones fill in around them, on the argument that the reverse order leaves no room for anything large. It suits anyone whose real constraint is available blocks rather than available tasks, and it pairs naturally with a weekly planning slot rather than a daily one.

Working style is the second filter, not the first. A method that fits your friction but fights the way you already work gets abandoned within a fortnight, which is why the working-style self-check on the home page is worth the few minutes it takes: it names which of the four styles you recognize yourself in, and the comparison table further down that page lists the methods to try first for each one. When two methods look equally plausible, pick the one that asks less of you on a bad day, run it for two honest weeks, and judge it then. Nothing here has to be permanent, and running two methods for two different problems is normal rather than a sign that neither worked.

What if everything is urgent?

Some weeks every task on the list carries a deadline, and the ranking question stops being theoretical. The first thing worth knowing is that a list of genuine urgencies is still a list with an order. Two deadlines on the same afternoon cannot both be met at once: something moves, and the only real question is whether you decide which one or let the decision make itself at five o'clock.

So audit the urgency before you accept it. For every task claiming a deadline, ask two questions: who set this deadline, and what actually happens if it moves? Some deadlines are external and fixed, such as a client date, a filing window, or a shipping slot. Others were set by a colleague guessing, by a recurring meeting that wants a document in front of it, or by you, three weeks ago, under assumptions that have since changed. Both kinds look identical on a task list and behave completely differently when tested.

The audit usually thins the list. What is left is a smaller set of tasks with real consequences attached, and those can be ranked on consequence: which one causes the most damage downstream if it lands late, and who is blocked while it waits. A task that other people are waiting on outranks a bigger task that concerns only you, even when the bigger one looks more substantial, because the blocked work keeps accumulating while it sits.

Then renegotiate what is left, and renegotiate scope before you renegotiate dates. Most work has a version that costs a fraction of the effort and delivers most of what the requester actually needs: a one-page summary instead of the full report, a working draft instead of a finished document, the section people actually read instead of the whole chapter around it. Offering that version is a much easier conversation than asking for another week, and it is usually accepted, because the person on the other end wanted the decision the document supports, not the document.

When a date really does have to move, move it early and say so plainly. A deadline renegotiated on Monday is a scheduling detail; the same deadline missed quietly on Friday is a problem for everyone downstream of it. Name the conflict, name what you are doing first and why, and give the new date. This is the part of prioritizing that gets skipped most often, and it is the part that does the most work: a ranking you keep to yourself only orders your own day, while a ranking the people around you know about orders theirs too.

Weeks where everything is urgent are also worth logging. If the same category of work turns up urgent every week, the problem sits upstream of the ranking: a standing commitment that never gets planned, a handover that always arrives late, a review step with no slot of its own. That is a scheduling question rather than a prioritizing one, and it is usually fixable once, instead of being sorted out again every Monday.

The five prioritization methods

Frequently asked questions