How to Prioritize Tasks When Everything Is P0

How to Prioritize When Everything Is P0

Real talk: most prioritization advice is garbage.

You can shove your to-do list into an Eisenhower Matrix, a color-coded Kanban board, seventeen phone alarms, or whatever productivity framework has main character energy this month. None of it answers the one question that actually makes this hard:

What do you do when multiple things are genuinely P0?

The board deck is due Friday. Your biggest customer needs an answer today, like an hour ago. Product is dead in the water until you make a call. None of this is fake work. None of it can wait forever. And depending on who you ask, each one is obviously the most important thing happening at your company right now.

Here's the plot twist: when everything is P0, your job isn't to find the "real" priority. Spoiler: they're all real.

Your job is to build two systems instead: one that puts things in order, and one that makes sure "later" doesn't quietly become "never."

System one tells you what happens now. System two makes sure everything else still happens later.

Why Everything Feels Urgent

Most productivity systems assume your work shows up as a tidy list. Executive work doesn't. It shows up as a request, usually mid-sprint, usually with a deadline already attached: a board member wants revisions before Friday, sales needs a save on a customer who's about to churn, product can't move a single ticket until you decide.

And every single one of these arrives pre-labeled "urgent," because to the person sending it, it is.

Sales sees the revenue walking out the door. Product sees an entire team sitting on their hands. The board sees the calendar. You? You're the lucky person who has to see all three at once, plus the fourteen other things already on fire (yay!).

That's the actual problem. You're reconciling promises you made to different people, at different times, in different Slack threads, half of which you forgot you even said yes to. And when commitments are scattered like that, the loudest or most recent one wins by default.

Which, as you already know deep in your soul, is not prioritization. That's just whoever pinged you last.

System One: The Rule That Actually Sorts P0s

Here's the fix, and it's stupidly simple: stop asking what's important. Realistically speaking, everything is. Ask this instead:

What gets worse the longer it waits?

That one question does more work than any matrix ever will, because it ranks things by consequence instead of by decibel level. Three ways to apply it:

1. Actively getting worse beats staying exactly the same. A customer mid-breakup with your company outranks a board deck that will look identical whether you touch it today or tomorrow at 9am.

2. Blocking other humans beats blocking only you. If product is stalled until you decide, every hour you sit on it is an hour of someone else's paycheck evaporating into Slack limbo, not just yours.

3. Irreversible beats recoverable. A choice you can still undo with an apology and a follow-up email is not in the same league as a choice that slams a door shut forever.

Run today's chaos through those three filters and the order usually just... appears. Not because the rest stopped mattering, but because you finally have one consistent reason for what goes first, instead of "whoever has the scariest title" or "whoever texted me twice."

System Two: Where "Later" Actually Goes

Cool, so you picked what to do first. Congrats. The other two things did not evaporate. The customer still needs a reply. The board still needs slides. Product is still refreshing Linear every ten minutes.

This is the part almost nobody builds on purpose, and it's the reason "later" has such a bad reputation. A delayed answer and a missing answer feel completely different on the receiving end. "Tomorrow morning, here's exactly why" keeps a customer. Silence loses one.

So system two isn't a framework, it's a habit: the second something gets bumped, it gets a real, specific new time — and someone tells the person waiting before they have to come chasing you for it. Not "soon." Not "circling back!" An actual time, said out loud, like a functioning adult.

You got this!

Do both of these, and "everything is P0" stops being a five-alarm fire you're putting out every day. It just becomes a queue. A very full queue. But a queue you're running, instead of one running you :)

Frequently Asked Questions

Q: What does P0 actually mean?

A: P0 means "priority zero" — the highest urgency tier, above P1 and P2. In practice, most teams use it to mean "drop everything," which is exactly why it stops working once multiple things get labeled P0 at once.

Q: How do you prioritize when everything is P0?

A: Stop ranking by importance and rank by consequence instead: ask what gets worse the longer each thing waits. Whatever is actively deteriorating, blocking other people, or irreversible if delayed goes first — regardless of who asked or how urgently they asked it.

Q: What's the actual difference between urgent and important?

A: Urgent describes how badly someone wants a response right now; important describes what actually happens if they don't get one. Most inboxes conflate the two because saying "urgent" is a free way to jump the queue — which is why the label itself should never be the deciding factor.