How to Prioritise Tasks Effectively When Everything Feels Important

When everything feels important, the problem is usually not that you have failed to make a sufficiently detailed to-do list.

The problem is that a list records work without deciding between competing claims on your time.

Twenty tasks can all be legitimate.

They cannot all be first.

Prioritisation begins when you accept the trade-off hidden inside every decision: doing one thing now means delaying something else.

A useful priority system therefore does not ask:

“What do I need to do?”

It asks:

“Given the time and capacity I actually have, which outcomes deserve attention first?”

That distinction turns prioritisation from list-making into decision-making.

Task prioritisation at a glance

A task list is inventory, not a decision

A to-do list is useful because it prevents work from being forgotten.

But it does not automatically tell you what deserves attention.

A list containing:

• renew an important contract,

• reply to six emails,

• approve a design,

• prepare a major presentation,

• submit an expense report,

• book an appointment,

• update a spreadsheet,

• and begin a long-term strategy document

treats all of these items visually as equivalent.

They are not.

Some have large consequences.

Some have hard deadlines.

Some unblock other people.

Some are merely easy.

Some can wait.

Some may not need to be done at all.

Prioritisation begins only when those differences are made explicit.

Why urgency can overpower importance

Urgent work attracts attention because its time limit is visible.

A message marked “urgent” creates pressure.

A deadline later today creates pressure.

A notification creates a cue to act.

Important work can be psychologically weaker because its payoff may be larger but further away.

Research by Meng Zhu, Yang Yang and Christopher Hsee described a mere-urgency effect. Across five experiments, participants sometimes preferred lower-payoff tasks when those tasks appeared to have shorter completion windows, even when the urgency itself did not justify choosing the inferior option.

This does not mean people always make irrational decisions when something is urgent.

Real deadlines matter.

It means urgency can have psychological appeal independent of actual consequence.

That helps explain a familiar working pattern:

You begin the day intending to make progress on an important project.

Then an email arrives.

Then another.

A colleague asks for something “quick.”

A notification appears.

A small administrative issue develops a deadline.

By the afternoon, you have completed many tasks but barely touched the work that mattered most.

Urgency supplied constant cues.

Importance required deliberate judgement.

Step 1: Define the consequence

The first useful question is not:

“How urgent does this feel?”

It is:

“What changes if I complete this?”

Possible consequences include:

• generating or protecting revenue,

• avoiding financial loss,

• preventing a legal or compliance problem,

• reducing safety risk,

• helping a customer,

• moving an important project forward,

• unblocking another person,

• preserving a valuable opportunity,

• improving health,

• meeting an educational requirement,

• or creating important knowledge.

This converts “importance” from a feeling into something more concrete.

Compare:

“I really need to finish this report.”

with:

“This report determines whether the client approves the next phase of a £200,000 project.”

The second statement makes the consequence visible.

Step 2: Ask what happens if the task is delayed

Importance and urgency are related but different.

A useful way to evaluate urgency is to ask:

“What specifically changes if I do this tomorrow instead of today?”

That question exposes many false emergencies.

Deadlines can be divided roughly into three categories.

Hard deadline

Missing it produces a meaningful consequence.

Examples might include:

• a regulatory filing,

• an application deadline,

• an examination,

• a contract expiry,

• a payment cutoff,

• or a time-sensitive customer commitment.

These deserve serious weight.

Coordination deadline

The task may not have an external legal or commercial deadline, but another person or process is waiting.

For example:

• a designer cannot proceed until you approve a layout,

• finance cannot issue an invoice until you provide data,

• an analyst is waiting for access,

• or a colleague needs your decision before speaking with a client.

A five-minute task can therefore become important because it unlocks several hours of other people's work.

Preference deadline

Someone would like the work quickly, but little meaningful changes if it arrives later.

Preference deadlines are still legitimate.

They simply should not automatically outrank work with larger consequences.

Step 3: Identify dependencies

Task value cannot always be judged in isolation.

Some work has unblocking value.

Imagine you have two tasks:

Task A requires three hours and advances your own project.

Task B requires ten minutes and allows three colleagues to continue working.

It may be rational to complete Task B first even if Task A is strategically more important overall.

This is why good prioritisation asks:

Who or what is waiting on this?

Dependencies can involve:

• people,

• approvals,

• equipment,

• data,

• payments,

• bookings,

• decisions,

• external suppliers,

• or later stages of the same project.

A small task can have disproportionate value when it sits at a bottleneck.

Step 4: Compare value with effort

Effort matters, but it should not control the entire system.

A useful four-way distinction is:

High value, low effort

These are often excellent early wins.

Do them quickly when they genuinely create meaningful progress.

High value, high effort

These usually need protected calendar time.

If they remain only on a to-do list, smaller work will repeatedly push them aside.

Low value, low effort

Batch, automate, delegate or complete during low-energy periods where appropriate.

Low value, high effort

Challenge the task.

Ask whether it should be done at all.

The mistake is turning “quick wins” into a productivity philosophy.

If you always choose the easiest task with a positive payoff, difficult but transformative work may never start.

The goal is not to maximise the number of completed tasks.

The goal is to maximise useful progress.

Step 5: Connect tasks to outcomes

Tasks become easier to rank when they are attached to larger outcomes.

Instead of thinking:

“Prepare slides.”

connect it to:

“Secure approval for the new project.”

Instead of:

“Analyse customer data.”

think:

“Identify why renewal rates are falling.”

Instead of:

“Study Chapter 7.”

think:

“Prepare for Friday's examination.”

This prevents tasks from becoming detached fragments of activity.

Goal-setting research provides useful background here. A 2017 systematic review and meta-analysis of randomised trials found a small positive effect of goal setting on behaviour across many contexts.

That evidence supports the usefulness of clear goals.

It does not prove that one universal method exists for ranking every work task.

Prioritisation still requires contextual judgement.

Step 6: Protect important work before it becomes urgent

One of the best ways to manage urgency is to prevent important work from becoming urgent in the first place.

Long-term tasks often lose because their deadlines are distant.

Then the deadline approaches.

Suddenly the strategically important project also becomes an emergency.

Weekly planning can help.

A 2023 field experiment examined a planning approach involving goal setting, specifying work steps and developing alternative plans. Employees in the planning intervention subsequently reported fewer unfinished tasks and less weekly rumination, along with greater cognitive flexibility.

The practical lesson is not that weekly planning guarantees productivity.

It is that planning important work before the week fills with reactive demands can be useful.

At the beginning of the week, ask:

Which two or three outcomes would make this week meaningfully successful?

Then reserve time for them.

Do not rely on the hope that “I will work on it when I get time.”

Unallocated time rarely stays empty.

Step 7: Limit the number of daily priorities

A list called “Top 12 priorities” usually contains twelve tasks, not twelve priorities.

Priority requires scarcity.

One practical structure is:

Primary priority:
The single outcome that matters most today.

Secondary priorities:
One or two additional important items.

Maintenance work:
Routine administration that still needs to happen.

This does not mean only three tasks will be completed.

It means only a small number receive protected priority status.

Everything else must fit around them rather than compete equally with them.

Step 8: Put priorities on the calendar

A priority that has no time allocated to it is still vulnerable.

Suppose you decide that preparing a proposal is today's most important task.

But your calendar contains:

9:00 meeting
10:00 messages
11:00 calls
12:00 lunch
1:00 meeting
2:00 administrative work
3:00 follow-ups
4:00 meeting

The proposal may be cognitively first but operationally nowhere.

Priorities should therefore translate into time commitments.

For example:

9:00–10:30 — proposal draft

Now the priority has capacity attached to it.

This is especially important for high-value, high-effort work.

Step 9: Reassess new work instead of automatically accepting it

New work often receives an unfair advantage simply because it is new.

A request arrives and gets added to the list.

Another arrives.

The original priorities remain technically unchanged, but the workload grows.

This creates impossible plans.

When new work appears, ask:

What is the consequence?

What is the actual deadline?

Who depends on it?

Can it be delegated?

Does it outrank an existing commitment?

Most importantly:

If I accept this as a higher priority, which existing task moves down?

That last question restores reality.

Capacity has not increased because someone sent another request.

Step 10: Make trade-offs visible

Competing priorities often become a communication problem.

Several managers or stakeholders may each believe their request is first.

An employee may try to satisfy everyone by saying yes to all of them.

The result is often late work rather than clear prioritisation.

A better response makes the trade-off visible:

“I can complete A today. If B needs to become the priority, I can move A to tomorrow.”

This is not necessarily refusal.

It is capacity management.

It allows the person requesting work to participate in the prioritisation decision rather than assuming everything can happen simultaneously.

Use scoring when judgement feels inconsistent

For a crowded task list, a simple scoring method can reduce ambiguity.

Rate each task from 1 to 5 on three dimensions:

Consequence or value

How much does completing this matter?

Deadline pressure

How serious is the consequence of delay?

Dependency value

How much other work does this unlock?

Then record effort separately.

For example:

The score is not objective truth.

Do not let arithmetic replace judgement.

Its value is that it exposes assumptions.

If a task receives a high priority only because one stakeholder is loud, that becomes easier to see.

When the Eisenhower Matrix helps

The Eisenhower Matrix separates tasks using two dimensions:

urgent / not urgent

and

important / not important.

Its main value is conceptual.

It forces you to recognise that urgent and important are not the same thing.

That is particularly useful for people whose days are dominated by notifications, requests and short deadlines.

But the matrix is a heuristic, not a complete decision system.

Two tasks can both be important and urgent while differing dramatically in:

• risk,

• value,

• effort,

• strategic importance,

• dependencies,

• reversibility,

• and opportunity cost.

Use the matrix for rapid triage.

Use richer judgement for high-stakes decisions.

Do not confuse psychological relief with strategic value

Small tasks are seductive because they produce visible completion.

Reply to five messages.

Rename three files.

Update one spreadsheet.

Clear notifications.

The list becomes shorter.

That feels productive.

A difficult analysis may require two hours before anything looks finished.

This creates an emotional bias toward work that produces rapid closure.

Completion is not meaningless.

Reducing a backlog can genuinely lower cognitive load.

But ask:

“Am I doing this because it matters, or because finishing it will make me feel better?”

Sometimes the answer will still be “do it.”

The point is to distinguish emotional relief from strategic priority.

A productive day can end with many small tasks unfinished if the most consequential work advanced significantly.

Separate maintenance from progress

Another useful distinction is between work that maintains the system and work that moves the system forward.

Maintenance might include:

• routine reporting,

• inbox processing,

• recurring administrative work,

• file organisation,

• standard approvals,

• and basic housekeeping.

Progress work might include:

• developing a new product,

• learning an important skill,

• writing a major proposal,

• redesigning a process,

• solving a persistent problem,

• or building a new client relationship.

Both matter.

Maintenance prevents deterioration.

Progress creates change.

The danger is allowing maintenance to consume all available capacity because it produces constant urgency.

Priority changes are normal

A good priority system is not rigid.

Information changes.

A customer problem becomes more serious.

A deadline moves.

A new opportunity appears.

A dependency changes.

A risk disappears.

A task that mattered yesterday may legitimately fall today.

Reprioritisation is not evidence that planning failed.

The important rule is:

When one priority rises, another must fall.

The schedule must change with the decision.

Otherwise you have not reprioritised.

You have simply added more work.

Use reversibility as a tie-breaker

When two tasks appear similarly important, consider how difficult delay would be to reverse.

Missing an appointment booking window may create a two-month delay.

Postponing an editable internal document for one day may have almost no lasting cost.

A useful question is:

“If I delay this and discover tomorrow that I made the wrong decision, how difficult will it be to recover?”

Tasks with irreversible or expensive consequences of delay may deserve additional priority.

This is especially helpful when simple urgency and value scores produce a tie.

Prioritisation is different in teams

Individual productivity advice often assumes one person controls the entire task list.

Real organisations are more complicated.

Tasks may be:

• assigned by several managers,

• dependent on colleagues,

• connected to customers,

• constrained by shared resources,

• or politically sensitive.

In those environments, prioritisation should sometimes be explicit and collective.

A manager who assigns new urgent work should understand what existing commitment it replaces.

Teams can also benefit from agreeing on definitions.

What counts as:

critical?

urgent?

high priority?

If every request is labelled urgent, urgency loses meaning.

The weekly priority review

At the end of the week, examine the system rather than only the completed tasks.

Ask:

Which important task was repeatedly postponed?

Which supposedly urgent task turned out not to matter?

Where did I underestimate effort?

Which request should have been delegated?

Which recurring task could be automated?

Which deadline became urgent because I started too late?

Which task occupied substantial time without producing meaningful value?

Which stakeholder repeatedly creates avoidable emergencies?

These questions turn prioritisation from daily firefighting into process improvement.

Priority is ultimately a decision about sacrifice

Prioritisation sounds like deciding what to do first.

More fundamentally, it means deciding what will not receive attention yet.

That is why genuine prioritisation can feel uncomfortable.

If there is no cost to choosing Priority A, then A may not actually be competing with anything.

Real priority decisions often involve:

• disappointing someone,

• delaying desirable work,

• leaving an inbox partially unanswered,

• declining a meeting,

• postponing a low-value request,

• or admitting that current capacity cannot satisfy every demand.

A good priority system does not make every task disappear.

It makes the trade-offs visible enough that limited time is allocated according to consequence rather than noise.

The most useful final question may therefore be:

“If I complete this first, am I comfortable with what I am choosing to delay?”

If the answer is yes, you probably have a real priority.

If the answer is no, reconsider the order.

Frequently Asked Questions

What is the best way to prioritise tasks?

Start by comparing consequences, real deadlines, dependencies and effort. Then identify a small number of high-value priorities and allocate actual calendar time to them.

How many priorities should I have each day?

There is no scientifically fixed number, but a very long priority list defeats the purpose. One primary task plus one or two secondary priorities is a practical structure for many people.

What is the difference between urgent and important?

Urgency concerns time pressure and the consequence of delay. Importance concerns the value or consequence of completing the task. A task can be urgent without being highly important, or important without yet being urgent.

What is the mere-urgency effect?

The mere-urgency effect is a behavioural finding in which people may favour tasks that appear urgent even when those tasks provide lower objective payoffs than less urgent alternatives.

Does the Eisenhower Matrix work?

The Eisenhower Matrix can be a useful heuristic for separating urgency from importance. It should not be treated as a complete or precise ranking algorithm because real tasks also differ in value, dependencies, risk and effort.

Should easy tasks always be completed first?

No. High-value, low-effort tasks can be useful quick wins, but consistently choosing easy work can delay difficult tasks that produce much greater value.

How do I prioritise when my manager says everything is urgent?

Make the trade-off explicit. Ask which existing task should move if the new request becomes the highest priority. This turns competing demands into an actual capacity decision.

How should I prioritise several high-value tasks?

Compare deadlines, dependencies, opportunity costs and how difficult the consequences of delay would be to reverse. Then schedule protected time rather than keeping all of them on an undifferentiated list.

Should I change priorities during the day?

Yes, when meaningful new information appears. But whenever a new task moves up, explicitly decide which existing task moves down.

Why do I keep doing small tasks instead of important work?

Small tasks often provide immediate closure and visible progress. Important work may have delayed rewards and require sustained effort. Recognising that difference can help prevent completion count from replacing actual value.

Conclusion

Effective prioritisation is not about finding the perfect productivity framework.

It is about making better trade-offs.

A strong system repeatedly asks:

What consequence matters most?

What deadline is real?

What work is blocked?

What requires substantial protected effort?

What can wait?

What can be delegated or removed?

And what must move down when something else moves up?

The purpose is not to complete every available task.

It is to make sure that scarce attention, energy and time are being used on the work whose consequences justify receiving them first.