When everything is a priority, chaos wins
- phil427
- Jul 3
- 7 min read
When organisations become overwhelmed, the problem is not always a lack of effort. More often, people are working extremely hard. Projects are moving, meetings are happening, reports are being written, decisions are being escalated and teams are doing their best to keep important work moving forward.
The problem is that too many important things have become competing priorities.
Each priority may be entirely valid in isolation. A financial target, a customer commitment, a regulatory requirement, a digital transformation programme, a workforce issue, a service improvement, a new product, a supplier problem or a risk that needs managing may all matter. In a complex organisation, there will always be more than one thing that deserves attention.
The difficulty begins when these priorities are not connected through a coherent strategy, a realistic view of capacity and an integrated plan. When that happens, they begin to compete for the same money, people, time, governance and leadership attention. Over time, priority overload becomes one of the practical ways organisational chaos is created.

A priority is not simply something important
A priority is not simply something important. It is the thing that comes first when choices have to be made.
That distinction matters because, in many organisations, the word “priority” has become a polite way of saying “something we care about” or “something someone senior wants done”. The problem is that when everything is described as a priority, the word starts to lose its meaning.
A real priority should help people make decisions. It should help leaders decide where to allocate capacity, help teams understand what matters most now, help programmes understand what must be delivered first and help governance forums resolve conflicts. It should also help organisations decide what to stop, delay, combine or sequence differently.
If a priority does not help people make choices, it is not really a priority. It is simply another demand being placed on the system.
Priority overload is a system problem
Most organisations do not have one clean source of priority. Priorities emerge from strategy, finance, operations, customers, regulators, risk, technology, workforce pressures, market conditions, suppliers, boards, investors, partners and the day-to-day reality of keeping the organisation running.
Each of these perspectives can generate its own view of what matters most. The finance team may have a priority. The operations team may have a priority. The technology team may have a priority. The commercial team may have a priority. The board may have a priority. Customer-facing teams may have a priority. Regulators, commissioners or external stakeholders may also have priorities of their own.
The result is not always alignment. Very often, it is competition.
The problem is not that any one of these priorities is necessarily wrong. Many will be legitimate, urgent and important. The problem is what happens when they are not brought together into a coherent view of what the organisation is trying to accomplish and how the different pieces of work fit together. That is when priorities start to collide.
The NHS provides a very visible example of this, because it has to respond to national targets, local population needs, financial pressure, workforce constraints, regulation, operational performance, clinical risk, digital transformation and political expectation all at the same time. But the same pattern appears in many organisations. The context may differ, but the underlying problem is the same: too many legitimate demands competing for the same finite capacity.
Competing priorities create hidden cost
When priorities compete, the cost is not always visible at first. It shows up gradually in delivery delay, overloaded teams, duplicated work, shifting deadlines, unclear decisions and constant re-planning. It also shows up in the number of meetings required to manage the tension between different parts of the organisation.
A digital programme may be treated as a priority, but if the operating model has not changed, the expected benefits may never be realised. A cost reduction target may be treated as a priority, but if it removes capacity needed to improve flow, the wider organisation may become less productive. A customer improvement initiative may be treated as a priority, but if it conflicts with operational constraints, workforce capacity or technology limitations, it may create more frustration than value.
These are not abstract management problems. They are practical delivery problems.
When priorities are not aligned, people are forced to reconcile the conflicts locally. They compensate, negotiate, create workarounds, escalate issues, chase decisions and try to keep everyone happy. Much of this effort is invisible because it sits inside the day-to-day work of delivery teams, managers and operational leaders. But it consumes real capacity, and much of that capacity could otherwise have been used to improve performance, service, productivity or value.
Value must be the anchor
In any complex organisation, choices about priority should ultimately be guided by a clear view of value. Depending on the organisation, that may mean customer value, patient value, public value, commercial value, shareholder value, staff value or social value.
The important point is that value must be clear enough to guide decisions.
That does not mean every decision becomes simple. It does not mean ignoring financial control, regulation, quality, safety, workforce pressures, customer experience, technology, risk or operational reality. All of those things matter. But they need to be aligned around a coherent view of what the organisation is trying to accomplish, how it will know whether it has succeeded and how competing demands will be resolved when they collide.
Value should not be a slogan at the end of a strategy document. It should be the central test of priority.
A useful priority should help leaders ask whether a piece of work improves outcomes, supports the strategy, makes work easier or more effective, reduces avoidable duplication and delay, or creates value across the whole system rather than simply protecting a local interest. These are the kinds of questions that turn priorities from a list into a discipline.
Strategy must drive priority
This is where strategy matters.
Strategy should be the mechanism that allows an organisation to decide what matters most, what comes first, what supports it and what must wait. At its simplest, strategy should answer three basic questions: what are we trying to accomplish, by when, and how will we know whether we have accomplished it?
Those questions are not complicated, but they are often surprisingly difficult to answer clearly. Many organisations have strategies, but not always a clear line of sight from strategy to priorities, from priorities to delivery, and from delivery to measurable value.
That gap matters because if strategy does not shape priority, priority is shaped by pressure.
The loudest issue becomes the priority. The most urgent problem becomes the priority. The strongest local interest becomes the priority. The most visible target becomes the priority. The programme with the most senior sponsor becomes the priority.
Some of those may be right, but without an overarching strategy and integrated plan, the organisation has no reliable way of knowing.
Disconnected priorities drive chaotic evolution
Disconnected priorities are one of the engines of what I call Chaotic Evolution.
Chaotic Evolution is the way organisations become more complex, fragmented and difficult to lead over time when change accumulates without enough coherence, ownership or deliberate design. It creates a pattern where every part of the organisation is busy, but the system as a whole does not move coherently.
People work hard, but not always in the same direction. Programmes deliver outputs, but not always outcomes. Governance monitors activity, but not always value. Technology goes live, but does not always improve the way work is done. Finance controls spend, but does not always improve productivity. Operational teams keep things running, but do not always have the capacity to redesign the work.
This is how an organisation can be full of effort and still feel stuck. It is also how well-intentioned change creates more complexity.
Priority discipline
Most organisations do not need fewer important things to care about. They need greater discipline in deciding what comes first, what supports it, what must wait and how conflicts between priorities will be resolved.
That is priority discipline.
Priority discipline does not mean ignoring complexity. It means making choices within it. It means being honest that not everything can be done at once, understanding the capacity required to deliver change, sequencing work properly and aligning strategic, operational, financial, digital, workforce and customer priorities around the same outcomes.
It also means making trade-offs visible, rather than allowing them to be hidden inside delivery teams. In large organisations, stopping is often harder than starting. New initiatives are announced more easily than old ones are closed. New governance is created more easily than old governance is removed. New reports are requested more easily than existing reports are challenged. New priorities are added more easily than existing priorities are deprioritised.
That is how complexity accumulates, and it is why priority discipline is one of the practical ways to reduce chaos.
The questions leaders should ask
If organisations want to reduce chaos, they need to ask better questions about priorities. It is not enough to ask, “What are our priorities?” The more important questions are about choice, alignment, capacity and value.
Which priority genuinely comes first? What strategic outcome does it support? What value will it create? What will we stop, pause or delay to create the capacity to deliver it? Which other priorities depend on it, and which priorities conflict with it? Who owns the outcome, how will we know whether it has been achieved, and what will change in the way work is done?
These questions matter because they turn priority-setting from a negotiation into a delivery discipline.
From priority overload to coherent delivery
The route out of chaos is not to pretend an organisation has only one thing to care about. Complex organisations will always have many legitimate demands.
But legitimate demands still need to be integrated, sequenced and aligned. Otherwise, they compete with each other, consume the same capacity, pull leaders into conflicting conversations and ask delivery teams to achieve everything at once. The result is friction, delay, duplication, workarounds and failure demand.
That is not because people are not trying hard enough. It is because the system has not been clear enough about what comes first.
Organisations do not need another long list of priorities. They need clearer priority discipline: a way of connecting strategy, operational reality, delivery capacity and measurable value.
Because when everything is priority one, nothing really is.
And when nothing is truly priority one, chaos wins.


Comments