If everything is a priority, what does the word priority actually mean?

It sounds like a simple question. But in many organisations, it exposes a much bigger problem.

• Everything is important.

• Everything is urgent.

• Every stakeholder has a legitimate reason why their work cannot wait.

• Every initiative has a sponsor.

• Every team is busy.

And yet, surprisingly little seems to finish.

I explored this tension in the latest episode of the Organisational Friction Series.

🎧 Hopefully you have already listened to the podcast. If not, you can find it here: https://agileproducthub.com/podcasts

The episode "When Everything Is a Priority, Nothing Can Flow" looks at why too many priorities do not create more progress. They create more competition for attention. And eventually, more friction.

The problem is not that the work is unimportant

This is what makes prioritisation difficult.

Most organisations are not overloaded because people keep inventing pointless work.

The opposite is usually true.

• A regulatory requirement may genuinely matter.

• A revenue opportunity may genuinely matter.

• A technical resilience issue may genuinely matter.

• A customer problem may genuinely matter.

• A cost-reduction initiative may genuinely matter.

• An executive-sponsored change may genuinely matter.

The problem is not that these things are unimportant. The problem appears when the organisation assumes that because several things matter, they must all happen now.

Important does not mean concurrent.

That distinction matters.

An organisation can recognise the importance of ten things while still deciding that only three should receive focused attention today.

Without that choice, prioritisation becomes little more than labelling.

A priority should change something

Many organisations have become very good at ranking work.

• They use scoring models.

• They create prioritisation matrices.

• They maintain long backlogs.

• They assign numbers, categories and strategic themes.

But a ranked list is not necessarily a prioritised system. You can rank forty initiatives from one to forty and still start twenty-five of them.

Real prioritisation requires something more uncomfortable.

• It requires exclusion.

• It requires sequence.

• It requires saying: This matters, but not yet.

That is why one of the most useful ways to think about prioritisation is: A priority only becomes meaningful when it changes what you choose not to do.

If a new urgent initiative is added and nothing else changes, the organisation has not really reprioritised.

It has stacked another demand onto the existing system. And that is where flow begins to break down.

Stacking is not prioritisation

Imagine a team already working on several meaningful initiatives. Then a new competitive threat appears. Leadership quite reasonably decides that a response is urgent. The new work is added. But none of the existing work is paused. No deadline moves. No commitment changes. Nobody tells an existing stakeholder that their work will wait. The new priority has simply been stacked on top.

From a leadership perspective, this may feel responsive.

From the team’s perspective, the consequences are very different. Attention fragments. Specialists become stretched across several streams. Reviews queue. Dependencies multiply. People stop and restart work. More coordination is required simply to keep everything moving.

The organisation becomes busier. But each individual piece of work takes longer to finish. This is not a failure of commitment. It is a predictable consequence of too much concurrent work.

Why organisations avoid the trade-off

So why does this happen so often? Because saying yes is easier than choosing between legitimate outcomes.

• A stakeholder may already have made a commitment.

• Funding may already have been approved.

• A deadline may have been communicated.

• A leader may be protecting a local target.

• Stopping work can look like failure.

• Deferring work can feel political.

Starting everything creates reassurance, It allows the organisation to tell every stakeholder: “Yes, we are working on it.”

The difficulty is that activity can hide the absence of an actual decision. Everyone receives a yes. Nobody receives enough focus. The trade-off still exists. It has simply been pushed further down the organisation.

Eventually teams are left to make it informally through context switching, delay, incomplete work and repeated negotiation.

When six priorities become six streams of unfinished work

Consider a typical product area carrying six active initiatives.

• One is regulatory.

• One addresses customer experience.

• One improves technical resilience.

• One is expected to increase revenue.

• One reduces cost.

• One has strong executive sponsorship.

Each has a reasonable case. Leadership decides all six are priorities. The team begins all six. At first, this may appear productive. Progress starts everywhere. But very quickly, the system changes. The same specialist is needed by three initiatives. A design decision waits for technical input. A technical change waits for a business decision. A regulatory question pauses another stream. People switch between tasks. Meetings multiply. Work starts, stops and restarts.

Then, several weeks later, someone asks: “Why is everything taking so long?”

The answer is not that the team has failed to prioritise. The organisation has confused importance with concurrent priority.

Teams cannot create organisational focus on behalf of leadership

This is why I think discussions about prioritisation too often become team-level conversations.

We talk about backlog management. Sprint planning. Kanban boards. WIP limits. Better estimation. Those things can help locally.

But teams cannot solve organisational overload if the system around them continues feeding competing commitments into the same space.

Strategy may contain too many simultaneous objectives. Funding may encourage initiatives to start because money has already been allocated. Governance may ask whether every initiative is progressing rather than whether the whole system is overloaded. Measures may reward activity rather than completed outcomes. Different leaders may protect different commitments without a shared mechanism for resolving the collision.

Each part can appear reasonable on its own.

Together, they create organisational friction.

The organisation tells teams to focus.

The operating system keeps adding work.

Flow requires sequencing

Healthy prioritisation does not mean refusing to change direction. Priorities should change when evidence changes.

• Markets move.

• Customer needs evolve.

• Risk appears.

• Opportunities emerge.

The issue is not changing priorities. The issue is adding them without changing anything else.

A healthier response to a new priority is to ask: What should move because this has become more important?

That simple question changes the conversation. It moves the organisation from stacking to replacing. It forces trade-offs into the open. It makes sequencing visible. It protects focus. It also creates much more honest conversations with stakeholders.

Rather than pretending everything can happen simultaneously, the organisation can explain what is happening now, what comes next, and why.

That is not a lack of ambition. It is a recognition that meaningful work requires attention.

Healthy prioritisation is an organisational capability

Healthy prioritisation tends to have a few common characteristics. There are fewer things active at once.

• Trade-offs are explicit.

• Sequence is visible.

• Someone clearly owns priority decisions.

• Teams have permission to pause work rather than keeping everything artificially alive.

• Priorities are reconsidered when evidence changes.

• And leaders actively protect focus instead of continually adding work.

This does not require rigid planning. Quite the opposite. It creates room to adapt because the system is not already overloaded.

A new opportunity can enter. But when it does, the organisation consciously decides what changes.

A useful principle is: Changing a priority is healthy. Adding another priority without changing anything else is where overload begins.

This is where Harmony matters

Harmony does not mean every part of the organisation wants the same thing.

That would be unrealistic.

• Product may see a customer opportunity.

• Engineering may see a sustainability risk.

• Finance may see an investment constraint.

• Sales may see a commercial opening.

• Compliance may see a regulatory requirement.

Those tensions are normal. The question is whether the organisation turns those competing perspectives into coherent choices.

A harmonised organisation does not eliminate difficult trade-offs. It makes them visible enough to act on.

Strategy, funding, governance and leadership behaviour begin to reinforce the same priorities rather than each introducing another competing signal.

That coherence is what helps work move.

A question worth asking

Look at everything currently labelled a priority in your organisation.

Then ask:

If all of these things cannot happen at the same time, who is actually deciding what happens first?

And then:

Is that decision being made intentionally, or is the organisation leaving teams to discover it through overload?

If the answer is unclear, the problem may not be that the team needs to work faster. The organisation may simply need to choose.