Stop Running Your Backlog Like an Emergency Room

The 3P Triage Framework: why purpose and design come before urgency—and how that changes everything about backlog prioritization.

You know the feeling. Another feature. Another bug. Another stakeholder request that can’t wait. You fight the fire.

And somewhere at the end of the week, you look at your changelog and realize you’re no closer to where you wanted to be.

That feeling is the ER mindset. And if you’re building software, managing a product or owning a business, there’s a good chance it’s running your backlog.

The ER Is Not the Problem

The emergency room excels at prioritization under pressure. Triage nurses make life-or-death decisions in under 60 seconds. They sort by urgency and severity. They don’t treat the loudest patient first. They treat the one who needs it most.

But here’s what often gets missed: the ER is part of a bigger system.

A hospital doesn’t only treat emergencies. It prevents emergencies before they happen and treats patients who need real care. The ER is one room in a much larger building. A dedicated room with a purpose.

The problem isn’t the ER. The problem is when your entire backlog becomes one.

When everything is urgent, nothing is. You respond. And respond. And respond. And the work that deserves real attention—the strategic work, the preventive work, the work that would stop the emergencies from happening in the first place—never gets done.

What the ER Gets Wrong

The ER triages everyone who walks through the door. That’s by design. It has to.

But your backlog shouldn’t.

Most prioritization frameworks—like the Eisenhower Matrix, MoSCoW and RICE—jump straight to scoring. Urgency. Importance. Effort. Impact. They assume that everything entering the system deserves to be evaluated.

That is an expensive assumption. Because most backlogs are approached from an operational perspective. What’s urgent. What’s important. What’s next. Useful, but it skips the bigger picture. The vision, the version you’re building toward.

And that’s exactly what you need to ask: Should this be in the system at all?

The 3P Triage Framework

This is what I call the 3P Triage Framework. Purpose. People. Profit. Three-stage triage. Each one a filter before the next.

Purpose

Purpose is the viability check.

“On purpose” means the work is intentionally aligned with where you’re going. Not just relevant. Directional. Walking the line toward what you’re actually building.

“By design” means you have a clear version defined that you’re building today. Not someday. Not “we could.” Clarity on what version of the vision you are releasing next. One check. One big question:

• Is it on purpose and by design? Yes / No

If the answer is no, the item doesn’t fit. It gets filtered out before it’s ever scored. You assign it to a future version or remove it altogether.

This is an important step to add in backlog triage and the one often skipped. Without it, you triage everything. And when you triage everything, you’re back in the ER.

People

People is the desirability check. This is where urgency and importance come in.

How critical is this right now? What’s the impact if we don’t act? Who needs it? What does it unlock or block?

This is the proven system. The meat of prioritization. Eisenhower had the right instinct here. The problem wasn’t the framework. It was applying it without context.

When every item in your backlog has already passed a purpose check, urgency and impact become meaningful signals. When they haven’t, everything feels urgent.

Score both on a simple scale:

• Urgency: Low / Medium / High / Critical
• Importance: Low / Medium / High / Critical

Profit

Profit is the feasibility check. The final lens of reality.

Can we actually do this? What’s the effort? What’s the risk? What might we break, slow down or delay by taking this on? What do we gain? What’s the return on investment?

Not just “can we build it?” but “can we afford to build it right now, given everything else?” And is it profitable to do so?

Size up all three:

• Effort: S / M / L / XL
• Risk: S / M / L / XL
• Revenue: S / M / L / XL

I’ve seen teams spend a sprint fixing a bug that affected three users, while a performance issue slowing down everyone quietly compounded in the background. I’ve seen initiatives invented to add capabilities to a part of the product our vision was trying to make obsolete in the industry.

Sometimes the most strategic move is removing something entirely. Maximize work not done.

With this 3P Triage Framework, you now know the value, the priority of a task. But when do you work on it?

Priority Is Not Order

This is the distinction that changes how you use all of this.

• Priority is an understanding of value. It tells you what matters most.
• Order is a commitment to act. It tells you what’s next.

They are not the same thing.

A low-priority item can hold a high order position, because of timing, dependencies or readiness. A high-priority item might sit lower in the order because the conditions aren’t right yet. Confusing priority with order is where backlogs fail.

When they’re treated as the same thing, urgency drives execution. Again. Technical debt never gets solved. Prevention never gets resourced. You’re back building a response system instead of a product.

And the emergencies keep coming. Because nothing is preventing them.

Closure

The ER isn’t the problem. The ER mindset is. The emergency room responds to urgency. Your backlog shouldn’t.

Real triage starts with a check: Is this aligned with our purpose? Does it fit the design we have? Only then does urgency and impact matter. Only then does feasibility make it worth it.

That’s the difference between a team that responds and a team that builds. On purpose. By design.