When Everything Is Priority One, Nothing Is

Open most roadmaps and you'll find the same thing. Fifteen items. Twelve of them marked urgent. A team quietly drowning, doing a little bit of everything and finishing almost nothing. Nobody sat down and decided this was the plan. It just happened, one "can we squeeze this in too" at a time.

Here's the thing about a list where everything is urgent: nothing actually is. Urgency only means something when it's relative. Once every item wears the same red label, the label stops doing its job. You're back to guessing, just with extra paperwork.

This week's prompt is built for the exact moment that becomes unbearable. Decide what to cut when everything on your roadmap feels urgent forces a real ranking instead of another meeting where everyone nods and nothing gets cut.

How it actually works

You paste in your current "urgent" list, your real capacity for the period, and whatever the actual top goal is (if you even have one). The prompt sorts everything into three tiers: genuinely time-sensitive with a real deadline attached, important but flexible, and urgent only because someone said so loudly in a meeting.

Then it does the part most people skip. For anything landing in that third tier, it makes you say, specifically, what happens if it waits. Not "it'll be fine." An actual answer. Most of the time there isn't one, and that's the tell.

A quick example

Say your list has nine "urgent" items and capacity for four this sprint. Feed it in, and you might get something like: two items with a genuine external deadline (a compliance fix, a client contract commitment), two more that are important but have no real date attached, and five that got labeled urgent purely because whoever raised them was persistent. For those five, the prompt asks what breaks if each one waits two weeks. Usually, nothing does.

What you're left with is a list sized to what you can actually finish, plus an honest deferred pile instead of a silent one. That difference matters more than it sounds. A task dropped without a word resurfaces later as "wait, whatever happened to X," and someone has to explain why it vanished. A deferred task with a reason attached is just a decision someone can see and argue with if they want to.

Where the real value sits

The time saved isn't really the point. The point is what a fake-urgent list costs a team: constant context switching, half-finished work everywhere, and a nagging sense that nothing's actually moving even though everyone's busy all day. A team working from four honestly-ranked priorities usually ships more in a month than a team splitting attention across fifteen "urgent" ones, even though it looks like they're doing less.

There's a second benefit too. Once you've forced this ranking once, the next roadmap conversation gets easier. You've got a working definition of what "urgent" actually means on this team, beyond a word everyone uses to jump the queue.

How to use it

1. Pull up the prompt and paste your current list exactly as messy as it is. Don't pre-sort it yourself first, that defeats the point.
2. Be honest about capacity. If you fudge the number to look more productive, the output just lies back at you.
3. Use the deferred list in your next planning conversation, out loud, as the actual list of things you chose not to do this round, and why.

Grab the roadmap-cutting prompt before your next planning meeting, not during it. Fifteen minutes with this beats another hour arguing about which fire is the realest one.