To prioritize tasks when everything feels urgent, start with the deadline, the consequence of delay and any work that other people cannot begin until you finish. Do not rank tasks by who sent the most messages. Choose the work with a real time limit or a meaningful downstream effect, then tell the affected people what will happen to the rest.
Separate a deadline from a preference
“Could you do this today?” can mean several different things. It may be a genuine deadline. It may mean the sender would simply prefer not to think about it tomorrow.
Before moving a task to the top of the list, ask:
- What happens if this is completed tomorrow instead?
- Is there a fixed deadline outside the team?
- Is someone waiting to begin their part?
- Does delay affect a customer, payment, legal obligation or scheduled event?
A task with a real consequence belongs above a task with a vague sense of urgency. This is not about dismissing the second request. It is about being honest about the order.
Look for the task that unblocks other work
Some work is important because it is short but opens the door for several other people. Approving a draft, answering one specific question or confirming a date can be more valuable than spending an hour polishing something that nobody needs yet.
Make dependencies visible. If your answer lets three people continue, it may deserve attention before a longer task that only affects your own progress.
When the choice involves a wider piece of work, write down the decision and the next owner. A short record prevents the team from having the same prioritisation discussion again tomorrow. Our guide to keeping track of decisions at work explains a simple way to do that.
Put the work into three groups
A long numbered list can create the impression that every item has been thoughtfully ranked. Often it has not. Try three working groups instead:
- Do now: Has a fixed deadline, a serious consequence or is blocking someone else.
- Schedule: Matters, but can be assigned a realistic time without causing harm.
- Clarify or decline: Is unclear, duplicated, outside your responsibility or not worth doing now.
This is not a permanent classification. Move tasks when new information arrives. The point is to stop treating your whole workload as one undifferentiated emergency.
Tell people what will wait
Priorities become difficult when nobody communicates them. A brief reply can protect both the work and the relationship:
“I’m finishing the customer update before noon because the team needs it for the call. I can review your draft after 2 pm. If you need it sooner, tell me what deadline I should work against.”
That message explains the order without making the other person defend their request. It also gives them a chance to share information you may not have had.
If two requests genuinely conflict, name the conflict early. Ask the person who owns the deadline to decide which outcome matters most. Do not quietly work late to make an impossible list appear possible.
Recheck your list when the day changes
A priority list is a tool for the next decision, not a promise that nothing new can matter. Review it when a deadline moves, a customer issue appears or a dependency is resolved.
But avoid rebuilding the whole plan whenever a new message arrives. Check whether the new item changes the consequences, deadline or dependency you used to make the original choice. If it does not, put it in the appropriate group and return to the task already in progress.
Urgency is useful information, but it is not a ranking system on its own. Choose the work that protects a real deadline, prevents a real problem or lets someone else move. Then make the trade-off visible.