How to Prioritize When Everything Is Urgent
When every stakeholder says their request is critical, "urgent" stops meaning anything. Here's how to cut through it without burning relationships.
"This is urgent." "We need this by Friday." "The CEO asked for it." "The client will churn if we don't ship this."
By week three in any PM role, you've heard all of these. By month two, you've stopped taking them at face value. Here's the framework I use when everything is on fire.
First: Separate Urgent from Important
Urgency is a time claim. Importance is a value claim. They're frequently confused because stakeholders use urgency as leverage when they can't prove importance.
Before prioritizing anything, separate the two questions:
- If we don't do this in the next two weeks, what actually happens? (Tests urgency.)
- If we never do this, what do we lose? (Tests importance.)
Things that are both urgent and important go first. Things that are urgent but not important are interrupts — handle them quickly or not at all. Things that are important but not urgent belong on the roadmap with a real date.
The One Question That Cuts Through Everything
"If we can only ship one thing this sprint, and it has to be this — what doesn't get done?"
I ask this in every conversation where someone is pushing for reprioritization. It forces the conversation from "add this" to "trade this for that." People who have thought through the tradeoff will answer clearly. People who haven't will ask for more time to think.
Both outcomes are useful.
Prioritization is never "what should we build?" It's always "what should we build instead of the other things we could be building?"
RICE Isn't the Answer (But It's a Good Start)
RICE scoring (Reach × Impact × Confidence ÷ Effort) is useful for making implicit tradeoffs explicit, not for making the decision for you.
The problem with pure RICE: it's easy to game. People inflate reach estimates and compress effort estimates for things they want to build. And RICE doesn't capture strategic alignment — a feature that scores 12 might be off-strategy, and one that scores 6 might be the thing that keeps your biggest customer.
Use RICE to pressure-test decisions, not make them. If RICE gives a high score to something that doesn't feel right, figure out what the model is missing. That gap is where the real conversation happens.
When the CEO Says It's Urgent
This deserves its own section because it's the hardest version of the problem.
The mistake is treating CEO urgency as information about priority. It's information about political pressure, which is different. CEOs get excited about things they saw at a conference. They promise features to investors before talking to product. They respond to the last customer they spoke to.
The right move: take it seriously as a signal, validate it quickly, and bring back the data. "You asked about X last week. Here's what I found about user demand for it, and here's what it would trade off against. Here's my recommendation." This is more useful than either blindly executing or pushback.
The Last Resort: Make the Urgency Visible
If all else fails, publish your sprint plan with the explicit tradeoffs documented. "We are shipping A, B, and C this sprint. D and E are deferred because doing them this sprint means A doesn't ship until [date]."
Visible tradeoffs change the conversation. People who are fine with "everything is urgent" become much more specific when they can see exactly what urgency costs.