How to Prioritize Tasks | The Eisenhower Matrix and Three Other Frameworks

You have ten things to do and three of them will actually get finished today. What you pick decides what the day was worth. The reason prioritizing feels hard every single time is that you are working it out from scratch on the spot, without a standing criterion. This article covers four frameworks you can switch between depending on the situation, and what to do when none of them produces an order.

The Real Reason You Cannot Set Priorities

"It is all important, so I cannot choose" nearly always has the same cause underneath it: you have not decided what to drop.

Prioritizing is not rearranging an order. It is the act of confirming what will not happen today. Naming a number one is easy, but doing so is identical to declaring that the other nine are being deferred. If you will not accept that declaration, no framework will save you, and everything ends up marked high.

Put the other way around: once you can make the deferral call, almost any framework will get you close enough. The four below differ only in which situation they make that call easiest.

Choosing Between the Four Frameworks

• Eisenhower Matrix: clearing the tasks in front of you across a day or a week.
• MoSCoW: the deadline will not move and scope has to come out.
• Impact vs. effort: several possible moves exist and you get to choose whether to make them at all.
• Dependency-first: you are working in a team and your delay stops someone else.

1. The Eisenhower Matrix: Four Boxes from Importance and Urgency

The best-known framework of the four. Tasks are sorted into four quadrants along the axes of importance and urgency.

• Quadrant 1 (important, urgent): do it now. Same-day deliverables, incidents.
• Quadrant 2 (important, not urgent): schedule it. Building systems, learning, relationships.
• Quadrant 3 (not important, urgent): delegate it or reduce it. Most inbound requests and meetings land here.
• Quadrant 4 (not important, not urgent): do not do it.

The value of this framework is not in identifying quadrant 1 but in how you handle quadrant 2. Quadrant 2 has no deadline, so left alone it never gets started. That is why you do not stop at deciding to do it: you finish the thought by putting a block on the calendar. Whether you can schedule this quadrant is what separates two people a year from now.

One caution: urgency is handed to you by other people, while importance is something you have to define yourself. Unless you have already articulated a standard, such as whether the task connects directly to a quarterly goal, everything will look like quadrant 1 in the order it arrived.

2. MoSCoW: Cutting Scope When the Deadline Will Not Move

MoSCoW sorts the work into four bands.

• Must: without this it does not work at all. Dropping it means failure.
• Should: important, but it still works without it. Include wherever possible.
• Could: nice to have. Only if there is room.
• Won't: not this time. Excluded explicitly.

This is a tool for drawing an in-or-out line rather than a high-or-low one. Its defining feature is that Won't gets stated out loud. Quietly deferring something and formally recording that it is out of scope produce very different arguments later. And because the cut is documented, you can pick the item back up next time around.

As a rule of thumb, if Must exceeds about 60 percent of the total, you have not really sorted anything. Only what genuinely cannot be dropped belongs in Must. This also works as the concrete method for cutting scope when you realize you will miss a date. Placing the turning points themselves is covered in how to set milestones.

3. Impact vs. Effort: Choosing Among Several Moves

Plot the options on two axes, the size of the effect and the effort required, and start with the ones that deliver a large effect for a small effort.

• High impact, low effort: top priority. Start here.
• High impact, high effort: plan for it. Check first whether it can be broken down.
• Low impact, low effort: when there is spare capacity. Batch them together.
• Low impact, high effort: do not do it.

If you want more precision, replace the sense of large and small with numbers. Rate impact from 1 to 10, express effort in person-days, and sort by impact divided by effort. Even that much pulls the discussion out of competing opinions. Do not sink time into the scoring itself, though. A scoring sheet you cannot fill in within five minutes has stopped being a decision aid and become work.

Using this to select campaigns themselves is also covered in marketing project management.

4. Dependency-First: Who Are You Blocking?

When you are working in a team, one criterion outranks all three above: whether your task is the precondition for someone else starting theirs.

You postpone a thirty-minute review and someone sits idle for two days. In that structure, what is important to you is beside the point. There is one test: is there a person who cannot move until this is finished? If there is, it goes ahead of everything else on your list. The shorter the task, the larger the loss it tends to be causing while it waits.

Finding these is sometimes faster by asking than by studying your own list. A weekly "is anything blocked on me?" clears out most of this category. To map dependencies between tasks visually, see how to build a Gantt chart.

When No Framework Produces an Order

If none of the four gets you to an order, the framework is not the problem. It will be one of these three.

• You lack the information to decide: this is not a prioritization problem, it is a confirmation or decision that has not happened. Pull it out of your task list and track it as an issue.
• You do not have the authority to decide: you are alone with an ordering that is not yours to set. Hand the decision back to the requester or your manager.
• You have not abandoned the assumption that everything gets done: if nothing can be dropped, the only remaining levers are the deadline and the headcount.

In practice the third is the most common. It is a capacity problem rather than a priority problem, and frameworks cannot solve it. If reshuffling the order repeatedly still leaves you with no way through, stop ordering and switch to a conversation about the deadline or the staffing.

Three Rules for Making It Work in Practice

1. Pick three in the morning: write down three things that must finish today and put everything else in the "if there is time" pile. Three is a number you can hold to. Seven is not.
2. Hold priority as an order, not a column: high, medium, and low all drift toward high over time. A ranked list from one downward keeps working.
3. Throw the order away once a week: last week's priorities belonged to last week. Anything carried over gets chosen again from scratch.

An order you keep in your head is gone by the next morning. How to build the shared list a team works from is covered in how to build a task tracker, and the personal habits that keep it current are covered in what people who are good at task management have in common.

Once priority has to be judged against campaign budget and results, reordering tasks on their own is no longer enough. Xtrategy manages campaign schedules alongside budget and KPIs on a single screen, so you can see across campaigns where resources should go. For managing work at the campaign level, see the marketing campaign management template as well.

Summary

• Prioritizing means confirming what will not get done.
• For clearing the work in front of you, use the Eisenhower Matrix. The key is scheduling quadrant 2.
• For cutting scope against a fixed deadline, use MoSCoW. Record Won't explicitly.
• For choosing among possible moves, use impact vs. effort. Do not spend long on the scoring.
• For working in a team, go dependency-first. Who you are blocking outranks everything.
• If no framework works, you are short on information, authority, or capacity.