How to Prioritize When Everything Feels Urgent

When everything feels urgent, ranking will not save you. A sorted list of nine hours of work still contains nine hours of work, and your afternoon still holds four. The reason prioritising feels futile in that state is that it is: you are being asked to order a set whose total nobody has checked.

So the first move is not to rank. It is to find out by how much you are over, because that number determines whether you have a prioritisation problem or a conversation to have. Add up what you believe today's work will take, in rough fifteen-minute steps. Compare it to the hours you genuinely have after meetings, messages and the gaps between things. If the overage is twenty minutes, rank and get on with it. If it is four hours, no ordering of the list produces a finished day, and the useful work is elsewhere.

Why the matrix is not enough

Almost every answer to this question starts with the Eisenhower matrix: sort by urgent and important, do the urgent and important first, schedule the important, delegate the urgent, delete the rest. It is a genuinely useful idea and it has one structural flaw for this particular problem.

It has no denominator. A matrix will cheerfully tell you that fourteen hours of work are urgent and important, and feel helpful doing it. Every quadrant is a judgement about an item in isolation, and the thing that is killing your day is the total.

It has a second problem. Urgent versus important is a comparison between two properties an item is assumed to have, and "urgent" is not a property an item has. Urgency is a claim about consequences over time. The moment you ask what the consequence actually is, most of the urgency on a typical list evaporates.

That is the practical answer to how to prioritize tasks at work when the list is full of things other people called urgent: stop grading the items and start grading the delays.

Ask what happens if you delay

Instead of sorting into two bins, ask one question per item: what actually happens at one hour, one day and one week of delay?

Write the answer in a few words. It takes about fifteen seconds an item, and it separates four genuinely different things that the word "urgent" flattens into one.

Hard-gated

The consequence is immediate and external. The filing deadline is 5pm, the flight is at seven, the client call is in ninety minutes. Delay has a cliff edge. These are rare, and they go first, and you will notice there are usually only one or two of them.

Cumulative

The consequence grows with time but nothing breaks at any specific moment. A broken signup form costs money every hour. An unanswered customer gets crosser. Fixing the form is often a fifteen-minute task carrying a bigger consequence than a three-hour project with no deadline, and it should beat it.

Flat

Nothing in particular happens at an hour, a day or a week. The report is read on Monday whenever it was written. Most of the list is here, which is the finding that matters: on a list where everything felt urgent, most of it turns out to have a flat consequence curve and could move with no cost beyond your own discomfort.

Manufactured

The urgency is somebody's tone of voice, or a self-imposed deadline, or the fact that it arrived most recently. Freshness is the most common thing people mistake for priority, and an item that arrived ten minutes ago has no special claim on the next hour.

The one priority rule nobody mentions

There is a category that beats everything above and fits in no quadrant of any matrix: work that unblocks someone else.

A boring twenty-minute review that lets two colleagues continue is worth more than a three-hour piece of important work only you are waiting on. It is not more important, and by any ordinary reading it is not more urgent either. It is a dependency. The cost of delaying it is multiplied by the number of people standing behind it.

So before ordering anything, pull out the items where somebody else cannot proceed until you have acted. Do those first, unless something is hard-gated.

This one habit changes how a team experiences working with you more than any other prioritisation decision, and almost nothing written about priority mentions it.

A worked list

Nine items, a Tuesday afternoon with 210 minutes of real task time.

That is 400 minutes against 210. Here is the order and, more importantly, the line.

Approve Dan's deployment first, at ten minutes, because two people are behind it. Then the angry customer and the signup link, 40 minutes between them, because both consequences are growing while you read this. Then the VAT return at 40 minutes, because the week has a cliff edge in it and today is the day with room. That is 110 minutes.

The board slides are the hard call. They are genuinely hard-gated, but on Thursday, and at 120 minutes they do not fit in the remaining 100.

The right move is neither to start them nor to ignore them. Put 100 minutes of them in today and the rest tomorrow morning, which means checking that tomorrow morning really has 20 minutes free. If it does not, the slides start now and something else moves.

Below the line: the careers page, the analytics research, the loud email. The survey gets Friday, because it has a real deadline and a flat curve until then.

Total planned: 210 minutes, which is exactly full, which means it is slightly over. In practice I would move the VAT return to tomorrow and leave 40 minutes of slack, because a day planned to exactly its capacity fails the first time anything runs long, and something always does.

When the top three still do not fit

This is the case every article skips. You have cut the flat items, dropped the manufactured urgency, ordered by consequence, and the remainder is still bigger than the day. At that point the work is not prioritisation. It is renegotiation, and the reason people avoid it is usually that they do not know what to say.

Say something specific. The difference between a vague "I am swamped" and a concrete trade is enormous. The first asks the other person to solve your problem. The second hands them a decision, with the information needed to make it.

Four things that work:

Offer the trade. "I have four hours today and these three things need six. I can get you the pricing deck by two, or the forecast by three, but not both. Which helps more?"

Name the cost of the interruption. "I can do this today if the migration review moves to Thursday. Happy either way, but one of them moves."

Ask for the real deadline, not the stated one. "Is Friday the deadline, or is Friday when you would like it? If Monday works, I can do a better job of it."

Deliver a smaller version on time. "A full analysis takes two days. I can give you the three numbers you will actually act on by five today." This is often the answer people wanted anyway, and it is far better than a complete piece of work delivered late.

None of these is a trick, and none of them works if you have not done the arithmetic first. The reason they land is that you can say "four hours and six hours" with a straight face, because you counted.

The hardest case

Sometimes nothing can move. Hard external deadlines, a manager who assigned all of it, caring responsibilities that are not negotiable. The arithmetic says the day does not fit and renegotiation is not available.

There is no planning technique that fixes that, and it would be dishonest to offer one. What the arithmetic gives you in that situation is still worth having: you know which things will not get done, so you can choose them rather than discover them, and you can tell the people affected before rather than after. Choosing badly on purpose beats failing by accident, and it is the difference between a hard day and a damaged relationship.

If that is every week rather than one week, the problem has stopped being about priority. The number you now have, the gap between committed hours and available hours, is the most useful thing you can bring to that conversation.

Where the tooling helps

The ranking above is judgement and no software will do it for you. The arithmetic is not, and that is the part worth automating, because it is the part that gets skipped.

In Todonado, tasks carry effort estimates, and the Today view totals what you have scheduled against the capacity you set and warns you before the day starts rather than after it fails. Priority is a field, so the consequence judgement you made above is recorded rather than re-derived every morning. Imported calendar events consume the same capacity, so an afternoon of meetings visibly shrinks the task budget instead of quietly competing with it. When work has to move, Week planning places it against the next seven days' real capacity, so "Thursday" is a Thursday you have checked.

The honest limit: nothing in it decides what is urgent. It will tell you that 400 minutes do not fit into 210, and the consequence curve is yours to draw.

If the deeper problem is the size of the list rather than today's order, start with organizing a huge to-do list. If it is that you cannot get moving at all, getting things done when you have too much to do is the one to read first.