Most leaders can describe their organisation in formal terms. They can show you the structure, name the divisions, explain the strategy and identify the people who hold authority. Yet none of those things tells you how the organisation really works. The real organisation lives somewhere else. It lives in the unwritten rules about which decisions require permission, whose voice carries weight, what happens when bad news travels upwards, which meetings matter, what gets rewarded, and what everyone has quietly learnt not to challenge.

This is the organisation viewed as a system. It is not an abstract idea, and it is not the same thing as an organisation chart. It is the pattern created by thousands of repeated interactions between people, processes, incentives, information and power. Every organisation has such a pattern. The only question is whether it has been designed with care or allowed to drift into being.

Drift is more common than most leadership teams admit. A process introduced to solve yesterday’s problem becomes permanent. A talented executive becomes the informal route around a weak function. A monthly meeting survives because nobody wants to question it. A temporary approval layer becomes part of the furniture. A founder’s personal preferences harden into organisational doctrine. Each decision may have been understandable at the time. Taken together, they produce an operating system that nobody chose but everybody must navigate.

The strategy on paper and the system in practice

Every organisation has a declared strategy. It also has an enacted strategy. The declared strategy sits in plans, presentations and speeches. The enacted strategy is revealed by where time, money, attention and permission actually flow. When the two diverge, the embodied system usually wins.

A leadership team may say that innovation matters while requiring six approvals for a modest experiment. It may speak warmly about accountability while rescuing senior people from the consequences of missed commitments. It may champion collaboration while setting targets that cause functions to compete. It may encourage candour while reacting defensively to uncomfortable information. People do not take their deepest cues from slogans. They study consequences. They learn what the system truly values by watching who progresses, who is heard, which risks are tolerated and which failures are remembered.

This is why culture cannot be separated from operating design. Culture is not simply what people believe. It is what the system repeatedly teaches them to believe. If the official message says one thing and the lived machinery says another, the machinery is more persuasive.

Leaders can find this unsettling because it challenges a familiar explanation for underperformance. It is easier to say that people need to be more proactive, collaborative or accountable than to ask whether the organisation makes those behaviours rational. When people behave consistently in ways leaders dislike, the first question should not be, ‘What is wrong with them?’ It should be, ‘What is the system making sensible?’

Drift has a logic

Organisational drift is rarely the product of negligence. It usually begins with adaptation. People create workarounds because formal routes are too slow. Managers hold on to decisions because capability is uneven. Teams protect information because they have been exposed before. Leaders involve themselves in operational detail because past delegation ended badly. These responses make sense locally, but local sense can create institutional nonsense.

Consider a growing organisation in which the chief executive becomes the final point of reference for difficult decisions. At first this feels efficient. The chief executive has context, judgement and authority. Decisions are made quickly, and quality is protected. Over time, however, colleagues stop building their own decision muscles. Ambiguous issues travel upwards. Meetings become preparation for the chief executive rather than places where leaders resolve matters together. The chief executive works harder, the organisation moves slower, and everyone concludes that further central involvement is necessary. A reinforcing loop has formed.

The problem is not the chief executive’s commitment. Nor is it the team’s character. The problem is the architecture of dependence. Unless that architecture is redesigned, exhortations to ‘step up’ will achieve little. People cannot be empowered by language while the system continues to withdraw authority, information or protection.

The same dynamic appears in mature institutions. A compliance failure leads to more controls. More controls create delay and encourage informal shortcuts. The shortcuts create new risk, which leads to further controls. The organisation becomes simultaneously more bureaucratic and less controlled. Nobody intended this outcome. It emerged from a sequence of individually reasonable responses.

From symptoms to patterns

Systems thinking asks leaders to resist the seduction of the isolated incident. A missed deadline matters, but the more useful question is whether similar delays recur and under what conditions. A conflict between two executives matters, but the deeper question is whether accountabilities overlap, information is asymmetric, or incentives place them in structural competition. One resignation may be personal. A pattern of strong people leaving the same interface is organisational data.

This does not mean individuals are never responsible. They are. Systems do not absolve people of judgement, conduct or performance. But individual accountability without system accountability is incomplete. If several capable people struggle in the same role, the role may be badly designed. If decisions repeatedly stall at the same point, the decision route may be faulty. If a value is routinely compromised under pressure, the organisation may be rewarding the compromise.

I have often found that leadership teams know many of these truths before any formal diagnosis begins. The knowledge exists in fragments. One executive sees the bottleneck in approvals. Another sees the damage caused by conflicting priorities. A third understands why frontline information arrives late. What is missing is not intelligence but synthesis. The pieces have not been assembled into a shared picture of the system.

That shared picture matters because isolated fixes often move the problem rather than solve it. Improving one function’s efficiency can overload another. Centralising procurement may save money while slowing delivery. Adding a performance dashboard may increase visibility while encouraging people to manage the numbers rather than the work. The relevant unit of analysis is not the intervention. It is the intervention plus the reactions it produces.

Design is a leadership responsibility

Once leaders see the organisation as a system, their role changes. Leadership is no longer only about setting direction, inspiring people or making difficult calls. It is also about designing the conditions in which good work becomes more likely.

Those conditions include clear decision rights, useful information flows, coherent incentives, credible consequences, healthy governance rhythms and deliberate opportunities to learn. They include the way meetings are structured, the quality of management conversations, the connection between strategy and resource allocation, and the speed with which the organisation detects error. None of these is administrative detail. Together they determine whether strategy can travel through the institution.

Good design does not mean engineering away all uncertainty. Organisations are social systems, not machines. People interpret, adapt and surprise. Informal networks will always exist. New patterns will emerge. The aim is not perfect control. It is greater intentionality, better feedback and a stronger capacity to adjust before unhelpful patterns become entrenched.

This also means that design cannot be delegated entirely to HR, operations or a transformation office. Those functions may provide essential expertise, but the system is shaped by the collective behaviour of the senior team. Every exception they make, every conflict they avoid, every issue they pull upwards and every priority they add teaches the organisation something. Leaders are always designing the system, even when they believe they are merely responding to events.

A practical test for leadership teams

A useful starting point is to compare the organisation you say you have with the organisation people experience. Where are decisions actually made? How does inconvenient information travel? Which activities consume attention without changing outcomes? Where do capable people need heroic effort to get ordinary work done? What behaviour is rewarded in practice? Where does the system rely on memory, goodwill or a particular individual?

Then look for loops rather than lists. Ask what reinforces what. Does weak delegation produce low confidence, which produces closer supervision, which further weakens confidence? Does pressure for rapid results reduce reflection, causing poor decisions that create still more pressure? Does fear of failure suppress early warning, ensuring that leaders learn about problems only when failure is unavoidable? Loops reveal why familiar problems survive repeated attempts to fix them.

Finally, identify a small number of leverage points. These are not necessarily the largest projects. A clearer decision protocol can release weeks of delay. A different review question can change the quality of accountability. Removing a redundant approval can signal trust. Protecting the bearer of bad news can improve the information available to the entire executive team. Small changes matter when they alter a repeated pattern.

The most important shift is conceptual. Stop treating the organisation as a collection of departments and initiatives. See it as a living pattern of relationships, choices and consequences. The system already exists. It is producing exactly the behaviour it is currently organised to produce.

That may be the most challenging insight of all. It is also the most hopeful. If performance is shaped by a system, leaders are not limited to demanding more effort from people trapped within it. They can redesign the conditions. They can make authority clearer, information more honest, learning faster and accountability more real. They can move the organisation from accidental pattern to intentional institution.

Your organisation is already a system. The strategic question is whether you are prepared to lead as its architect.