How to Prioritize Tasks When Everything Is P0

How to Prioritize When Everything Is P0

Time to face a harsh truth: most prioritization advice online is useless.

You can force your to-do list into an Eisenhower Matrix, color-coded Kanban board, a list of alarms on your phone, or whatever productivity framework is having its moment. But none of them answers the question that actually makes prioritization hard:

What do you do when multiple things are genuinely P0?

A board deck is due Friday. Your biggest customer needs an answer today. The product team cannot move until you make a decision.

None of this is fake work. None of it can be ignored. And depending on who you ask, each one is correctly considered the company’s top priority.

When everything is P0, the goal is not to discover which tasks matter most because, spoiler alert, they all do. 

The goal is to build two systems: one that forces tasks into an explicit order using consistent logic every time, and one that cleanly manages what gets delayed as a result.

The first tells you what happens now. The second ensures that everything still happens later.

Why Everything Feels Urgent

Most productivity systems assume your work starts as a list, but executive work usually starts as a request: a board member wants revisions before Friday. Sales needs help saving a customer. Product is waiting on a decision before they can ship.

On top of being never-ending, these requests almost always arrive with an “urgent” label attached to them.

Sales sees the revenue at risk.

Product sees the team sitting idle.

The board sees the deadline.

You are the person expected to see all three.

That is what makes prioritization difficult: you are not just sorting one clean list of tasks by importance. You are reconciling competing commitments made to different people, often across meetings, Slack, email, and work you already delegated.

And because those commitments are scattered, the loudest or most recent request tends to win by default.

But, as you know very well, that is not true prioritization.