There’s a particular kind of week almost every leader recognizes: the to-do list has fifteen items on it, and somehow twelve of them are marked “urgent.” If you’ve been in that spot recently, here’s something worth hearing — that feeling almost never means you genuinely have twelve equally urgent things happening at once. It usually means your prioritization criteria have quietly broken down, and everything is defaulting to “urgent” because nothing has a clearer label anymore.
That’s actually good news, because a broken prioritization system is a much easier problem to fix than an impossible workload.
Why everything starts to feel urgent at once
Urgency, properly used, is supposed to be a relatively rare label — reserved for things where a real, specific cost attaches to delay. But in a lot of organizations, “urgent” quietly becomes the default way people signal “this matters to me” or “I need you to pay attention to this now,” regardless of whether a delay would actually cost anything measurable. Once that starts happening, urgency stops being useful information. Everyone’s list fills up with things marked urgent, and there’s no way to tell, just from the label, which ones genuinely can’t wait a week and which ones just got labeled that way because someone wanted them handled quickly.
This is, in a smaller and more personal way, the same underlying problem behind decision debt — a lack of shared, explicit criteria for what actually matters most, which leaves everyone defaulting to instinct, volume, or whoever asked most recently and most insistently.
A simple two-question framework
Here’s the fix we walk clients through, and it’s deliberately simple enough to use in real time, not just in a quarterly planning session.
For every item competing for your attention, ask two questions:
What actually happens if this gets delayed by two weeks? Not “would it be nice to have this sooner” — what specifically breaks, gets worse, or becomes harder to fix if it waits. If the honest answer is “not much,” that’s genuinely useful information, even if the request came in labeled as urgent.
What am I not doing if I do this instead? Every yes is an invisible no to something else. This question forces the trade-off to the surface instead of letting it stay hidden, which is usually where the real prioritization mistake happens — not in picking a bad task, but in not noticing what got silently deprioritized to make room for it.
Score everything on your list against just these two questions, even roughly, and a genuine hierarchy usually appears within a few minutes — not because the framework is magic, but because it forces the specific, concrete cost of delay to the surface instead of letting a vague feeling of urgency stand in for it.
A quick worked example
Say your list this week includes: a client escalation that’s been sitting for three days, a new hire’s onboarding paperwork, a competitor’s product launch that just landed in your inbox, and a recurring internal report that’s due Friday.
Run the two questions across all four. The client escalation: delay costs real trust and possibly the relationship — high urgency, real cost. The onboarding paperwork: delay by a few days costs some inconvenience but nothing structural — lower urgency than it feels in the moment. The competitor launch: worth a read, but delaying your response by a week almost never actually costs you anything material — this is urgency borrowed from someone else’s timeline, not your own. The recurring report: ask honestly whether anyone would notice if it arrived Monday instead of Friday — if not, that’s a strong signal it doesn’t deserve the “urgent” energy it’s quietly been getting by habit.
Suddenly, a list where everything felt equally pressing has a real order to it — not because the tasks changed, but because the criteria for judging them got explicit instead of staying vague.
A note on the things that don’t score high but still need to get done
Not everything that scores low on urgency should be dropped — some things are genuinely important without being urgent, and it’s worth being careful not to let this framework quietly become an excuse for deferring important-but-not-urgent work indefinitely. The point of the two-question test isn’t to eliminate anything that isn’t on fire. It’s to stop letting things that aren’t actually urgent borrow the emotional weight and attention that should be reserved for things that are. Important, non-urgent work still deserves protected time on the calendar — it just shouldn’t be competing directly, in the moment, with something genuinely time-sensitive.
Why this matters more at the leadership level than the individual one
Everything above works for an individual’s to-do list, but the real cost of “everything is urgent” shows up at the team and organizational level, where it compounds. When leadership doesn’t have shared, explicit criteria for urgency, every team ends up making its own local judgment call about what deserves priority — which means different departments end up pulling in genuinely different directions with total confidence that they’re each doing the urgent thing. We wrote more about how this specific failure shows up at the strategic level in our piece on the Roadmap Trap — the same underlying dynamic, just at a bigger scale.
We ran a prioritization reset for a professional services client whose leadership team had, by their own admission, eleven “top priorities” — which is a contradiction in terms. Using this exact two-question framework in a single working session, they got that list down to three real priorities everyone could actually agree on, plus a much shorter secondary list. Read how that reset played out in our professional services prioritization case study.\
The takeaway
The next time your whole list feels urgent, resist the instinct to just work harder or faster through all of it. Run the two-question test instead. In our experience, it takes less than ten minutes, and it almost always reveals that the real problem wasn’t the volume of work — it was the absence of a shared, explicit way to tell what actually mattered most.