"Is This Actually a Priority?" A Real Filter for Competing Asks

A new request arrives, delivered with real urgency, maybe from someone senior — and it's remarkably easy to accept it as a genuine priority without actually checking whether it is one, purely because of how it was delivered rather than what it actually represents.

Five questions worth asking before accepting a new priority

1. What's the actual consequence of not doing this right now? Not "would it be good to do this" — everything reasonable would be good to do. What specifically breaks, and for whom, if this waits a week? A vague answer here ("it would just be better to have it") is itself informative — it usually means the urgency is more about how the request was framed than a genuine deadline behind it.

2. What is this displacing? Every new priority added without an explicit conversation about what gets deprioritized is, by default, either extending total workload past a sustainable level or silently pushing something else — something that was presumably agreed to matter, at some point — further down the list without anyone deciding that on purpose.

3. Who decided this is more important than what's already committed? Sometimes the honest answer is "no one actually compared the two — this just arrived and felt urgent in the moment." Naming that explicitly, out loud, is often enough on its own to prompt a more deliberate decision instead of a reflexive one.

4. Is the urgency in the request itself, or in how it was delivered? A request delivered with real energy or visible stress can feel urgent regardless of whether a genuine deadline or consequence actually sits behind it. Separating the tone from the substance is exactly what this filter is for.

5. What would happen if this waited until the next planning cycle? For a meaningful share of requests that feel urgent in the moment, the honest answer is "probably nothing serious" — which is itself a useful, if quietly deflating, piece of information.

Using this without becoming difficult to work with

The point of this filter isn't to resist every new request — it's to make the tradeoff explicit rather than invisible. Something genuinely can be more important than what's currently planned; the filter doesn't argue against that. It argues against absorbing new priorities silently, without ever surfacing what's actually being pushed aside to make room, which is how a series of individually reasonable requests adds up to an unsustainable total workload that nobody consciously decided to create.

A real script for using this with your own boss or client

"Happy to take this on — to make room, should [current item] move to next week, or is there someone else who could pick that up instead?" This isn't a refusal. It's a genuine question that forces the actual tradeoff into the open, and it very often produces a more thoughtful answer than either silently absorbing the new request or refusing it outright.

What this filter reveals over time

Applied consistently, this filter tends to reveal a pattern worth noticing: some requesters' asks routinely hold up under these five questions, and some routinely don't — the second group often benefits from being asked these questions directly and consistently, since it usually shifts how they frame requests going forward once they learn the questions are coming. This isn't about distrust; it's about building a shared, more honest habit around what "urgent" and "priority" actually mean in a specific working relationship.

Where this fits alongside broader prioritization

The impact/effort matrix is the right tool once you have a full list of competing priorities to sort and rank. This filter is the earlier, faster check — applied the moment a new request arrives, before it's even added to that list — for whether it genuinely belongs there in the first place, or whether it's riding on urgency that doesn't survive five direct questions.

What to do when the filter reveals a genuine conflict

Sometimes running these questions confirms that two things really are both important and both time-sensitive, with no honest way to defer either one. In that case, the filter's job is done — it's surfaced a real, explicit tradeoff rather than resolving it — and the actual decision belongs with whoever has the authority to weigh both priorities against each other, ideally in a short, direct conversation rather than left for one side to guess at unilaterally.

Applying this to requests you make of other people, not just ones you receive

The same five questions are worth turning around and applying to your own requests of others before making them — asking yourself honestly whether a request you're about to send someone else would actually survive this filter, or whether it's riding on urgency you're projecting rather than urgency the situation genuinely warrants. Applying the filter in both directions, not just defensively to protect your own time, tends to reduce how often it needs to be invoked at all.

The short version

Requests that feel urgent in the moment don't always survive a direct check against what they're actually displacing and what genuinely happens if they wait — and running that check consistently, rather than accepting urgency at face value, protects existing commitments from being silently and repeatedly bumped by whatever arrived most recently or most forcefully. The goal isn't refusing new priorities; it's making sure the tradeoff is a real, visible decision rather than an invisible one nobody actually chose to make.