How to Decide What to Drop When Everything's Urgent
When several things compete for your time at once, the instinct is to work on whoever asked most recently or pushed hardest. That feels responsive, but it means the actual highest-consequence task can quietly slip while you're handling whoever happened to be loudest. A manager juggling a client deliverable, a direct report's overdue review, and a Slack channel full of pings can end up spending the morning on Slack simply because it was the thing making the most noise.
Warning
Urgency you feel and urgency that's real aren't the same thing. The request that feels most pressing is often just the one that arrived most recently, not the one with the most at stake.
The loudest task and the most important one are rarely the same task. Treating them as if they are is how the important one slips.
Why reacting to volume isn't the same as reasoning about stakes
Responding to whoever pinged last feels productive because something's getting done. What it doesn't do is compare what actually happens if each competing task slips, and that comparison, not response speed, is what should decide the order. A quiet task with a real deadline, like a performance review a direct report is waiting on before a compensation conversation, carries genuine weight even though it never sends a follow-up ping the way an impatient client does.
Take someone with three things due this week: a client deliverable Friday, a direct report's performance review Wednesday, and twenty unread emails accumulating pressure just by sitting there. The emails feel urgent because they're visibly piling up, but most of them probably don't carry real consequences if they wait a day. The performance review, quiet and easy to deprioritize, actually blocks someone else's decision on the other end. Reacting to visible volume alone would put the emails first and the review last, exactly backward from what the actual stakes suggest.
Before: work on whoever asked most recently or most insistently, let the quieter but higher-stakes task wait.
After: list out everything actually competing for your time with real deadlines and consequences, and get an honest, reasoned order from Claude, including what's safe to let slip.
A process for deciding under real pressure
- 1
List everything genuinely competing, not just what's loudest right now
Include the quiet but consequential task alongside the one that just pinged you. If it's not on the list, it can't factor into the decision, and the tasks that don't ping you are exactly the ones most likely to get left off by accident.
- 2
Give the real deadline and consequence for each
State what actually happens if each one slips, not just when it's due. Two tasks due the same day can have very different stakes if one slipping is a minor delay and the other is a missed commitment to someone else who's waiting on it.
- 3
Ask for an order with the reasoning shown, not just a ranking
Request why each item landed where it did, not only the final order. The reasoning is what lets you sanity-check the ranking against something you know that Claude doesn't, like a client relationship that's more fragile than the deadline alone suggests.
- 4
Ask directly what's safe to let slip
Get an honest answer about which item can genuinely wait without real cost, not just which one ranked last. Knowing what's safe to drop is as useful as knowing what to do first, since the goal isn't doing everything well, it's doing the things that matter well.
I have three things due this week: a client deliverable due Friday, a performance review for a direct report due Wednesday, and a backlog of 20 unread emails. Help me decide what order to tackle these in, and be honest about what I should let slip if I can't do all three well.
”When a new item shows up mid-week, it's worth re-running the comparison against everything already on the list rather than just slotting the new request in wherever it feels urgent, since a fresh request often feels more pressing than it actually is simply because it's the newest thing you're aware of.
A new request just came in: a same-day ask from my manager to pull together numbers for an exec meeting tomorrow. Re-rank it against the three items from before, and tell me honestly whether it actually outranks the performance review or just feels more urgent because it's new.
”Inside Claude Tutorial
Reasoning through real consequences instead of reacting to volume is transferable.
Deciding based on actual stakes, instead of whoever asked loudest or most recently, applies well beyond a busy week at work. The app has a full lesson on it, with practice that carries over to any moment where several things are competing for the same limited time.
When two priorities have genuinely equal stakes
Sometimes the honest comparison shows two things really are equally important, and no amount of reasoning produces a clean winner. That's a real answer, and it's better to know that going in than to force a false confidence in one over the other. Treating a genuine tie as if one option obviously wins can lead to second-guessing the choice later, when the actual issue was that there was never a clean winner to begin with.
Tip
Ask Claude to name a tiebreaker that isn't about importance, whichever one takes less time, or whichever has a harder deadline. When stakes are genuinely tied, a practical tiebreaker beats forcing a ranking that isn't really there.
You've said these two are genuinely close in importance. Since neither clearly outranks the other, suggest a practical tiebreaker, time required, hardness of the deadline, whatever makes sense, and tell me which one it points to.
”It's also worth checking whether a task that looks like one big commitment can actually be split, doing the highest-value half now and the rest later, rather than treating every item as all-or-nothing when time is tight.
Is there a way to split the client deliverable so I can deliver the most important part on time and push a lower-stakes section to early next week instead of delaying the whole thing?
”Continue reading
- Turning a Messy To-Do List Into a Plan You'll Actually Follow: the daily version of this same sorting discipline, applied to a single day's task list.
- Planning a Week You Can Actually Stick To: building these prioritization decisions into an actual weekly schedule.
- Drafting an Email Reply That Actually Sounds Like You: handling the lower-priority messages quickly once you've decided they can wait.
