Prioritising When Everything Is Urgent

A crowded workday can make every request sound like the one that must come first. A colleague needs an answer, a deadline is approaching, and a project with lasting consequences has no one urgently chasing it. If you rank work by who asks loudest, important commitments can slip. If you treat every deadline as equal, you lose the chance to make a deliberate tradeoff. This chapter gives you a repeatable way to sort competing work. First, you will distinguish a real time constraint from a preferred response time, and separate urgency from consequence. Then you will compare impact, deadlines and dependencies to decide what should happen first. Finally, you will practise making your reasoning visible so colleagues can respond to a tradeoff rather than guess why work has moved. The aim is not to predict every complication. It is to explain your choice, revisit it when facts change, and protect attention for work that matters.

Urgency and consequence answer different questions

Urgency asks, “How soon must someone act?” Consequence asks, “What changes if this work is done well, late, or not at all?” A request can be urgent but have little effect beyond the person waiting. A consequential task can have a distant deadline and still deserve protected attention because it affects a decision, customer, team, or major commitment. Treating these as separate judgements helps you avoid a common trap: assuming that a quick response is always the most valuable response. A preferred response time is not automatically a firm deadline. “Could you send this today?” may be a preference, a convenient target, or a genuine constraint. Ask what event depends on the answer and when that event occurs. A firm deadline is tied to a real point after which the result changes: a review meeting, a handover, a release, or an agreed commitment. You do not need to challenge the requester’s motives. You need enough context to rank the work sensibly.

Sort by consequence, then test the clock

For each request, make two quick judgements. First, estimate the consequence of delay. Would delay block another person, change a decision, create rework, affect a customer, or put a commitment at risk? Second, identify the timing constraint. Is there a fixed deadline, a preferred response time, or no stated time? These are practical questions, not a formal scoring system. Use plain language, and check your assumptions with the person who owns the work. Consider Aisha Rahman, a procurement analyst in Bengaluru. At mid-morning, a colleague asks her to reformat a slide deck before a team discussion later that day. Her team lead also needs a supplier comparison for a decision meeting the following morning. The deck request sounds immediate. Yet the supplier comparison could shape a purchasing decision and needs time for review. Aisha asks when the slides must be ready and learns the colleague can use the existing version for the discussion. She confirms that the comparison is needed before the morning meeting. The deck remains useful, but it no longer has the same time pressure.

Apply the distinction in conversation

• Name the work and the person or outcome it affects.
• Ask for the latest useful delivery time, not only the requested time.
• Check whether delay blocks a decision, handover, customer response, or other work.
• Compare the cost of delay with the value of the work already under way.
• If the facts are unclear, agree a short check-in rather than silently guessing.

A frequent mistake is to dismiss an urgent request as unimportant. An urgent task may protect a customer relationship or unblock a colleague. The reverse mistake is to let urgency erase consequence. Responding promptly can mean acknowledging the request, clarifying timing, and giving a realistic commitment. It does not always mean stopping your current task. Another error is to make the judgement alone when the requester knows a dependency you cannot see. A brief question can change the order of work. This distinction matters during ordinary interruptions, not only during crises. It helps you preserve attention for work whose effects last beyond the next message. It also gives colleagues a fair explanation. You can say, “I can send the revised slides after the supplier comparison. Is there a decision today that depends on them?” That response recognises their need while checking the actual constraint.

Compare the work, not just the dates

Once you have separated urgency from consequence, compare the tasks on three dimensions. Impact is the effect of completing or delaying the work. Deadline is the latest useful time, including whether that time is fixed or flexible. Dependency is the way one task enables another person or piece of work. A task with modest impact can still come first if it unblocks several people. A high-impact task may need an early start even when its final deadline is not close, especially if it requires review or input from others. Do not turn the comparison into false precision. A numbered ranking can help when several tasks compete, but the numbers are your working judgement, not an objective measurement. Start with the facts you know. Mark unknowns as questions. Then compare the cost of waiting. This makes it easier to spot the task that should start now, the task that needs a conversation, and the task that can safely wait.

Use a short comparison before you commit

• Impact: Who or what is affected, and what changes if the work slips?
• Timing: What is the firm deadline, and what is merely the requested response time?
• Dependency: What work or decision is waiting on this task?
• Effort and uncertainty: What remains to be done, and what information could change the order?

Then apply a simple decision sequence. First, identify any task whose delay creates a serious or hard-to-reverse consequence. Second, identify tasks that unblock time-sensitive work. Third, compare the remaining deadlines and effort. If two tasks still compete, ask the people affected to choose between the consequences rather than making an invisible promise to complete both. In Lisbon, Marta Silva is a product operations lead preparing a service change for a client support team. She has a draft staff guide due for review, a colleague’s request for a status summary, and a final set of changes to a customer-facing notice. The status summary is requested before lunch, but it will not inform a decision until the afternoon. The notice needs approval before the support team uses it. The guide is due for review later, yet a legal reviewer has not returned comments. Marta confirms when the notice will be used and asks the reviewer when comments are likely. She then completes the notice, sends the status summary with a clear delivery time, and revises the guide once the missing input arrives. Her order reflects impact, timing and dependencies, not the order in which messages arrived.

Make the ranking workable

A task list is useful only if it supports action. For each competing item, write a short reason beside its position: “first because the team cannot brief customers without the approved notice” is more useful than “high priority”. Include the next action, not only the final deliverable. If a task is waiting on information, record who owns the response and when you will check. If you have already promised a delivery time, include that commitment in the comparison. Existing commitments are part of the work, not background noise.

Common mistakes include ranking by deadline alone, overlooking work that needs review, and assuming that a dependency will resolve itself. Be alert to tasks that appear small but release substantial work for others. Also revisit the order when a deadline, risk, or dependency changes. A ranking is a current decision, not a permanent verdict. This comparison helps in planning meetings, project handovers and busy inboxes. It gives you a defensible reason for starting one task before another and makes room to adjust when new information arrives. The aim is a workable order that reflects the consequences of waiting, not a perfect forecast.

A priority choice affects other people

When you move one task ahead, something else usually waits. If you keep that tradeoff to yourself, colleagues may assume their request is under way, repeat it, or discover late that a shared commitment has slipped. Making the decision visible is not a defence of your workload. It is a way to coordinate expectations. State what you understand, the order you propose, and the consequence for the other request. Then give people a chance to correct a missing fact or choose between outcomes. A useful message is specific and neutral: “I’m completing the client handover before the analysis because the receiving team needs it for tomorrow’s launch. I can send the analysis on Thursday, or I can switch if the review meeting needs it sooner. Which consequence should I protect?” This explains your reasoning without blaming the requester or pretending both tasks can happen at once. Avoid vague promises such as “I’ll try to get to it”. They do not tell anyone what to expect.

Say what moves and invite a decision

A clear tradeoff conversation has four parts. Name the competing commitments. Explain the impact, timing or dependency that makes one come first. Say what will move and propose a realistic delivery time. Ask whether new information changes the decision. If the work affects several people, include the person who can choose between the outcomes. Keep your tone direct and respectful. You are discussing capacity and consequences, not judging whose work matters more as a person. In Nairobi, Peter Otieno is a finance manager preparing materials for a regional planning review. A senior colleague asks him to refresh a set of charts before a presentation. Peter is also due to send a forecast to department leads who use it to prepare their own plans. He checks whether the charts contain a decision that cannot wait and learns that the presentation can use the current version. He tells the colleague that he will send the forecast first, then update the charts later that afternoon. He names the reason and confirms that the colleague is comfortable with the revised timing. If the presentation need changes, they can discuss which task should move.

Keep commitments credible

When you cannot accept a request as stated, offer a useful choice if you can. You might propose a smaller deliverable, a later time, a different owner, or a quick decision about which commitment should move. Do not offer options you cannot deliver. If the tradeoff belongs to your manager or project lead, provide the relevant facts and ask for a decision instead of silently absorbing more work. If you own the decision, make it and communicate it promptly. Avoid two opposite errors. Saying yes to everything creates hidden delays and weakens trust when commitments slip. A blunt refusal can ignore a genuine dependency or leave the requester without a workable alternative. A respectful response acknowledges the need, states the constraint and identifies a path forward. Revisit the agreement if the facts change, and tell affected people early rather than waiting until the deadline is at risk.

Put the three judgements together

A sound priority decision distinguishes a firm deadline from a preferred response time, compares the impact of delay, and checks who or what is waiting. It also makes the resulting tradeoff visible. You do not need perfect information before acting. You do need to identify what you know, ask about a consequential unknown, and make a realistic commitment. If a new deadline or dependency changes the consequences, revisit the order and tell the people affected.