When everything feels urgent, do not start by trying to work faster.

First separate four things that have probably become tangled together:

What is genuinely time-critical.
What is commercially important.
What actually requires you.
What can realistically be done with the capacity available.

Those are not the same question.

A customer shouting loudly does not automatically make their request the most important thing in the business.

An email marked URGENT does not create additional hours in your day.

A problem being important does not mean it must be solved today.

And something genuinely needing action today does not necessarily mean you need to do it.

That distinction is where prioritisation starts.

If your days have become an endless sequence of interruptions, escalations, messages, customer problems and internal requests, you probably don't need another colour-coded to-do list.

You need to rebuild the system that determines what earns your attention.

Why does everything feel urgent?

Usually because every commitment has ended up in the same place.

Your head.

Your inbox.

Your WhatsApp.

Slack.

Teams.

A notebook.

A half-completed task app.

People walking into your office.

Customers ringing your mobile.

Things your partner reminded you about over dinner.

Ideas you had while walking the dog.

Problems somebody mentioned in a meeting three days ago that you've been trying not to forget ever since.

None of those channels tells you how important something is.

They merely tell you that something has arrived.

When everything enters the same mental queue, your brain has to keep making the same decision repeatedly:

What should I do next?

And the easiest thing to react to is usually whatever feels most immediate.

That does not necessarily mean it matters most.

Urgent and important are not synonyms

This is the first distinction to restore.

Something is urgent because delay has a near-term consequence.

Something is important because the outcome matters.

Those can overlap.

Payroll failing tomorrow is both urgent and important.

A serious customer safety problem may be both.

A critical tender deadline at midday may be both.

But plenty of urgent things are relatively unimportant.

And many extremely important things are not urgent at all.

Recruiting the manager your business desperately needs may be important but not require completion today.

Fixing a broken pricing model may be extremely important but have no flashing deadline.

Training somebody to take work away from you may be strategically important while another fifty emails feel more immediate.

Improving cash forecasting may prevent a crisis three months from now, but nobody is currently shouting about it.

That is precisely why important work gets crowded out.

Experimental research has found what researchers call the mere urgency effect. Across five experiments, participants were sometimes more likely to choose a lower-value task simply because it appeared more urgent, even when the urgency did not make the task objectively more valuable. This was controlled experimental work rather than research specifically on business owners, so it should not be stretched beyond what it demonstrates. But it provides useful evidence for something most owners will recognise immediately: urgency itself can pull attention towards work that delivers a worse outcome.

Your job as the owner is to resist that pull.

Your inbox is not a priority system

Neither is your phone.

Yet a surprising number of business owners effectively let both decide what they do.

Email arrives.

React.

Phone rings.

React.

Employee appears.

React.

WhatsApp notification.

React.

Customer complains.

React.

Another email.

React.

By lunchtime you've been incredibly busy.

You have also made almost no deliberate choices about what your time was supposed to accomplish.

That is not prioritisation.

It is arrival-order management.

Whoever interrupts you next wins.

There are jobs where immediate responsiveness is essential.

But if you run a company, a significant proportion of your work should probably involve things that nobody is going to chase you about today.

Thinking.

Planning.

Reviewing performance.

Hiring.

Developing people.

Building systems.

Reviewing pricing.

Talking properly to important customers.

Looking at the numbers.

Removing recurring problems.

Those activities are easily displaced because they rarely announce themselves with a ringtone.

First: get everything out of your head

This is the Dump part of The DROP System.

Do not try to prioritise while also trying to remember.

Those are two different mental jobs.

Capture everything demanding attention.

Not beautifully.

Not in categories yet.

Not with fifteen labels and seven priorities.

Just get it somewhere trustworthy.

Tasks.

Commitments.

Problems.

Calls.

Ideas.

Promises you've made.

Things you're waiting for.

Things you need from other people.

Things other people apparently need from you.

Anything your brain keeps rehearsing because it doesn't trust you to remember it.

There is a useful body of research around what psychologists call cognitive offloading, where information or intentions are transferred into the external environment to reduce internal cognitive demand. A review by Evan Risko and Sam Gilbert describes examples including reminders and external cues that reduce the need to hold intentions entirely in memory.

That does not mean writing something down magically solves overload.

It means you can stop using your brain as storage and start using it for evaluation.

That matters enormously.

You cannot make sensible priority decisions about work you are frightened of forgetting.

Then review the whole picture

This is where most traditional task management goes wrong.

People capture tasks and immediately start doing them.

You have not yet prioritised anything.

You have merely created a written version of your panic.

The Review stage asks better questions.

For every significant item, ask:

What happens if this is not done today?

Not:

Will somebody be annoyed?

What actually happens?

Does revenue disappear?

Does a legal or contractual deadline pass?

Does somebody become unsafe?

Does a customer suffer a material consequence?

Does a decision block ten employees?

Does a project miss a critical dependency?

Or will somebody simply receive it tomorrow instead?

The difference matters.

A large number of things masquerading as urgent become considerably less frightening once you identify the real consequence of waiting.

Separate real urgency from social urgency

Business owners experience two kinds of urgency.

Real urgency

Something changes materially if you delay.

Examples:

A payment deadline.

A safety issue.

A customer operation genuinely stopped because of your failure.

A submission closing at noon.

A delivery problem affecting today's work.

A major employee issue requiring immediate intervention.

Social urgency

Someone would quite like you to respond quickly.

They emailed again.

They used capitals.

They copied your colleague.

They asked whether you had “had a chance to look”.

They phoned because emailing fifteen minutes ago apparently felt too slow.

Social pressure can feel remarkably similar to operational urgency.

It isn't always the same thing.

The business owner who cannot distinguish between them gradually becomes available to whoever is most persistent.

Ask who created the deadline

Another useful question:

Where did this urgency come from?

Sometimes it is real and unavoidable.

Sometimes it came from a customer.

Sometimes regulation.

Sometimes a genuine change in circumstances.

Fine.

But sometimes the deadline exists because:

Nobody planned.

Someone forgot.

A manager left something until the last minute.

A salesperson promised something impossible.

The owner said yes without checking.

A customer has learned that shouting moves them to the front.

A recurring process is badly designed.

This does not mean refusing to help people because they planned badly.

Occasionally you absolutely should rescue the situation.

But if the same type of emergency appears every week, stop treating it as an emergency.

It is a system.

Fix the system.

Importance needs a commercial definition

If everything is described as important, the word becomes useless.

For an established business owner, I would judge importance against outcomes.

Does this work materially affect:

• Revenue
• Gross profit
• Cash
• Customer retention
• Delivery
• Capacity
• People
• Risk
• Strategy
• Your ability to remove future dependency on you

That last one is easy to underestimate.

Spending two hours training somebody may produce no immediate revenue whatsoever.

Yet if those two hours remove five hours of recurring owner workload every month, the commercial value can be enormous.

The important work is often the work that changes what happens next week, next month or next year.

Urgent work tends to preserve today.

You need both.

Next question: does it actually require you?

This is the Offload part.

Business owners frequently mistake:

This needs doing

for:

I need to do this.

They are completely different statements.

Suppose a customer needs an answer today.

Fine.

Why does that answer require the owner?

A supplier needs chasing.

Why you?

A quotation needs producing.

Why you?

Somebody wants a decision.

Does the decision genuinely require your authority, or has everyone simply learned to escalate?

A member of staff has encountered an unusual situation.

Do they need your answer, or do they need clearer boundaries within which they can decide?

This is particularly dangerous for capable owners because capability attracts work.

You solve the problem once.

People remember.

Next time, they come straight back.

You solve it again.

Eventually the company develops a very efficient system for routing uncertainty towards you.

You become the business equivalent of an emergency department.

Everything comes in.

Everything gets triaged by you.

And eventually everything feels urgent because you are carrying everyone else's unresolved decisions alongside your own.

Urgency is often a symptom of owner dependency

I know this one because I've lived it.

There was a period when almost everything in the company seemed to find its way back to me.

Problems.

Clients.

Staff.

Calls.

Emails.

Decisions.

Issues that apparently couldn't wait.

I became extremely good at solving them.

That was part of the problem.

The better I became at firefighting, the more sensible it appeared for everybody else to bring me fires.

That does not create a high-performing business.

It creates a highly capable bottleneck.

If every decision comes back to you, prioritising your personal workload will only get you so far.

You need to reduce the amount that should have reached you in the first place.

Decide what only you can do

One of the most useful owner-level filters is:

Does this genuinely require the owner?

There will always be some things that do.

Strategy.

Certain financial decisions.

Particular hiring decisions.

Sensitive people issues.

Major commercial negotiations.

Leadership.

Decisions carrying meaningful risk.

But ordering printer toner probably doesn't.

Neither does approving every £80 purchase.

Neither does reviewing every quote.

Neither does answering questions that a competent manager could resolve if you gave them the authority.

Your task list is partly a reflection of your organisation design.

If it contains dozens of routine operational decisions every day, don't only improve the list.

Improve the organisation.

Then decide what deserves your best attention

Now we reach the Plan stage.

You have captured the work.

Reviewed its consequence.

Removed or reassigned what should not belong to you.

Now decide what happens when.

I do not believe you need a complicated algorithm.

For significant owner-level work, I would use four questions:

1. What genuinely has to happen today?
2. What important outcome will deteriorate if I keep postponing it?
3. What can only I do?
4. What piece of work would make other work easier, unnecessary or less likely to become urgent?

That fourth question is where agency appears.

Because sometimes the best thing you can do today is not complete another task.

It is change the system producing the tasks.

The priority reset

When everything feels urgent, take 20 to 30 minutes and do this.

1. Dump

Capture every open commitment currently occupying your attention.

Do not organise yet.

2. Identify genuine deadlines

For each item claiming to be urgent, write the actual deadline.

Not “ASAP”.

Not “urgent”.

A real point in time.

3. Write the consequence of missing it

Be specific.

What actually happens?

This quickly exposes artificial urgency.

4. Identify ownership

Mark each item:

Me

Someone else

Needs a decision

Doesn't need doing

5. Offload immediately

Delegate.

Clarify.

Ask somebody else to decide.

Renegotiate the deadline.

Delete work that should not exist.

Do not carefully prioritise tasks you should not be carrying.

6. Choose today's genuine priorities

Not twelve.

A small number.

Your capacity determines the number, but for most owners three meaningful outcomes is already substantial if the work requires proper thought.

7. Protect space for at least one important, non-urgent action

This is critical.

If every available minute is consumed by today's urgency, tomorrow will eventually look exactly the same.

Do not prioritise 27 things

Priority means something comes before something else.

A list containing:

Priority 1
Priority 1
Priority 1
Priority 1
Priority 1

contains no priorities.

It contains denial.

You have to choose.

That means accepting that some work will wait.

This is emotionally uncomfortable for high-performing owners because postponement can feel like failure.

It isn't.

A decision to do A before B is the definition of prioritisation.

If everything must happen first, you have not made a decision.

Your calendar needs to reflect your priorities

A task list can claim that strategy is important.

Your calendar tells the truth.

If the entire week is filled with meetings, calls and reactive operational work, strategic priorities are not priorities.

They are aspirations.

Book time for work that requires proper attention.

Treat it seriously.

Not because calendar blocking is some revolutionary productivity technique.

Because important work with no protected space is extremely easy to displace.

Research on task switching gives another reason to be careful about fragmenting that time. Experimental work has repeatedly found performance costs when people switch between tasks, with costs affected by factors such as task complexity and the need to activate new task rules.

Separate research by Sophie Leroy found that switching away from unfinished work can leave what she called attention residue, with attention continuing to remain partly attached to the previous task and subsequent performance suffering.

That research does not mean a business owner should sit undisturbed in a monastery for eight hours.

It means thirty fragmented minutes are not always equivalent to thirty protected minutes.

Protect important thinking accordingly.

Create an interruption threshold

If people can interrupt you for anything, they will.

Not maliciously.

Because asking you works.

Create a simple threshold.

What genuinely deserves interruption?

For example:

Interrupt immediately

• Serious safety issue
• Major customer operation stopped
• Significant financial or legal exposure
• Critical decision blocking substantial work
• Serious employee welfare issue

Can wait until the next available decision point

• Routine approvals
• Standard pricing questions
• Minor customer queries
• Non-critical supplier issues
• Ideas
• Updates
• Problems somebody else has authority to solve

Your exact categories will differ.

The point is to stop treating everything as though the building is on fire.

Introduce decision windows

One reason owners get fragmented is that people need decisions throughout the day.

Instead of allowing every decision to create a separate interruption, batch what can reasonably wait.

For example:

11:30am and 4:00pm become decision windows.

Managers collect non-critical questions.

You deal with them together.

Emergencies still interrupt.

Everything else waits.

You have immediately changed the architecture of your attention without becoming unavailable.

That is often far more effective than downloading another productivity app.

Stop giving everybody direct access to your nervous system

Notifications deserve mentioning because they turn other people's timing into your timing.

Email alert.

Teams ping.

WhatsApp.

Calendar notification.

Text.

CRM notification.

LinkedIn.

Project management software.

Another WhatsApp group somebody created because apparently the existing six were insufficient.

Every notification says:

Look at me now.

Usually that is a request.

Not a command.

Design your availability deliberately.

Turn off notifications that do not justify interruption.

Check channels intentionally.

Give people clear expectations about when you respond.

Create escalation routes for actual emergencies.

This is not about becoming difficult to reach.

It is about making sure everything cannot reach you in exactly the same way.

Beware of easy urgent work

There is another reason urgent tasks win.

They often feel good.

Reply.

Done.

Approve.

Done.

Send.

Done.

Call.

Done.

Tick.

Tick.

Tick.

By comparison:

Redesign management structure.

Review pricing.

Plan next quarter.

Analyse why margins have deteriorated.

Develop succession plan.

Think.

Those don't provide rapid completion.

You can spend two hours on a strategic problem and finish with more questions than you started with.

So the brain naturally gravitates towards little urgent tasks because they provide visible progress.

You can end the day with 42 completed tasks while the three things capable of changing the business remain untouched.

Busyness can be extremely reassuring.

That does not make it useful.

Important work creates fewer emergencies later

This is one of the biggest reasons to defend it.

Consider:

Training a manager.

Documenting a process.

Clarifying decision authority.

Improving your cash-flow forecast.

Replacing an unreliable supplier.

Reviewing recurring customer complaints.

Recruiting before the team reaches breaking point.

Building management information.

Setting proper payment terms.

Reviewing capacity before sales increase.

None necessarily feels urgent today.

But neglect enough of them and they eventually come back wearing flashing lights.

The employee quits.

Cash becomes tight.

The customer leaves.

The project fails.

Everyone burns out.

The owner gets dragged back into operations.

I think of this as priority debt.

Every time genuinely important work is repeatedly displaced by immediate noise, you borrow against the future.

Eventually the future collects.

Sometimes everything genuinely is urgent

This needs saying.

Occasionally the answer is not better prioritisation.

There is simply too much genuine work for the capacity available.

Three major customers have problems.

A key employee has gone off sick.

Cash is tight.

A regulatory deadline is approaching.

Payroll needs resolving.

And a critical supplier has just failed.

All of it matters.

All of it really does require action.

No matrix fixes that.

At that point you have a capacity and consequence problem, not a personal productivity problem.

Your choices become:

Add capacity.

Renegotiate deadlines.

Reduce scope.

Ask for help.

Defer something.

Accept a lower standard somewhere.

Communicate delays.

Temporarily stop less important work.

You cannot prioritise twelve hours of genuinely essential work into eight hours.

Something has to move.

Pretending otherwise merely turns an operational constraint into personal guilt.

Use consequence, not anxiety, to rank work

This is perhaps the simplest rule in the whole article.

When several things feel urgent, ask:

Which delay creates the greatest real consequence?

Not:

Which one is making me most anxious?

Which customer is shouting loudest?

Which employee is standing nearest?

Which email arrived most recently?

Which task is easiest?

What creates the greatest consequence?

Suppose you have:

A customer wanting a proposal early.

A manager awaiting approval for a £200 purchase.

A major debtor whose payment deadline has passed.

A senior employee considering leaving.

A strategic proposal due tomorrow.

The emotional loudness of those things may bear almost no relationship to their commercial importance.

Consequence gives you a better basis for comparison.

Add reversibility to the decision

When consequences are similar, ask:

Which decision becomes harder to reverse if I delay?

Some work has options that disappear.

A deadline closes.

A candidate accepts another job.

A customer commits elsewhere.

A booking disappears.

A contractual right expires.

Other tasks remain broadly identical tomorrow.

That helps break ties.

Prioritise disappearing options before work whose options remain intact, assuming the commercial importance is otherwise comparable.

Add leverage

Another useful tie-breaker:

Which action unlocks the most other progress?

One approval might release an entire project.

One conversation might remove a week of uncertainty.

One hiring decision might free three managers to move forward.

One clarified process might stop ten recurring questions.

This is leverage.

Do not measure tasks only by the effort required to complete them.

Measure what completion changes.

A practical owner priority hierarchy

When the day becomes genuinely messy, I would broadly work through this order:

1. Immediate safety, legal or catastrophic risk

Deal with real threats first.

2. Time-critical issues with substantial commercial consequence

Deadlines, serious customer impact, material cash issues, major operational blockers.

3. Decisions that unlock other people's work

Especially where one owner decision is leaving several people idle.

4. Important owner-only work

Strategy, leadership, key commercial decisions and problems only you can reasonably solve.

5. Important work that reduces future urgency

Systems, delegation, training, recruitment, process improvement.

6. Routine work

Messages, administration, lower-value approvals, minor requests.

That is not an inflexible universal sequence.

Context matters.

It is a way of preventing category six from consuming the entire bloody day.

What if somebody disagrees with your priority?

They will.

Because everybody experiences the business from their own position.

Sales thinks the proposal is most important.

Operations thinks capacity is.

Finance wants the overdue debtor resolved.

The customer thinks their request is obviously first.

Your job is not to keep everybody equally happy at every moment.

Your job is to make the best decision for the whole system.

That means occasionally telling somebody:

Not yet.

Explain why where appropriate.

Give them a realistic commitment.

Then honour it.

A clear “Thursday by 2pm” is often considerably better than pretending something will happen immediately and disappointing them for three days.

What keeps becoming urgent?

Your weekly review should include this question.

Look back over the emergencies.

Which were genuinely unpredictable?

Which were completely predictable?

If the same problem keeps appearing, investigate it.

Late quotes.

Stock shortages.

Payroll questions.

Customer escalations.

Missing information.

Staff asking for approvals.

Projects finishing late.

Supplier failures.

Calendar chaos.

If an emergency repeats, it is providing data.

Use it.

Ask:

What invisible system keeps producing this outcome?

That question is more valuable than becoming slightly faster at cleaning up the consequences.

Better beats busier

This is where prioritisation connects with agency.

Work ethic asks:

How much of this can I get through today?

Agency asks:

Why does all of this work exist, and is there a better way?

Those questions produce very different businesses.

Sometimes the answer is to work hard and get through a difficult day.

I have never believed otherwise.

But if every day is a difficult day, effort is not solving the underlying problem.

The objective is not to become world-class at carrying an impossible workload.

It is to build a company that produces less unnecessary workload in the first place.

When everything feels urgent, use this sequence

Dump it.

Get the commitments out of your head.

Review it.

Identify genuine deadlines, consequences and commercial importance.

Offload it.

Remove work that doesn't require you, delegate decisions and eliminate tasks that should not exist.

Plan it.

Choose what actually deserves your limited attention and protect the time required to do it properly.

Then look at whatever keeps coming back.

Because if your priority system is working perfectly but fifty new emergencies arrive tomorrow, personal productivity is not the problem anymore.

The business design is.

You do not need to complete everything.

You need to make deliberate choices about what deserves to happen first.

That is prioritisation.