Organisations are not machines

A talented person leaves one company and joins another, and becomes almost unrecognisable. In the first they were disengaged, frustrated, quietly underperforming. In the second they are energised, inventive, alive to the work. Same person. Same skills. Same history. Nothing about them has changed. The conditions have.

Most of us have seen some version of this. And the strange thing is how little our usual language helps us explain it.

For more than a century we have borrowed our vocabulary for organisations from the industrial age. We talk about structures and operating models. Inputs and outputs. Levers, efficiency, productivity, mechanism. We design organisations as though they were machines, and manage them as though they were factories.

The metaphor has served us well. Until it doesn't.

Because the machine model cannot account for the things most of us have actually watched happen. Organisations buy new technology, redesign their processes and rewrite their operating models, only to find that very little changes and value is still hard to generate. And then a single leader arrives and changes everything — with no new systems, no restructure, no grand programme of change. No moving parts replaced. Yet somehow the whole place feels different. People behave differently. Decisions improve. Value emerges. Energy returns. Momentum appears from nowhere.

A machine doesn't behave like that. Perhaps because an organisation isn't one. Or perhaps because it isn't primarily made of the things we assume it is.

What an organisation is made of

At first glance the answer is obvious. People. Buildings. Technology. Processes. Products. Services. Code. Machines.

But walk into an office at midnight. The building is still there. The desks are still there. The monitors are still on the desks. And yet the organisation seems strangely absent. Something has gone home for the night.

What's missing is the conversation. The interpretation. The decisions being made, the trust being spent, the meaning being exchanged, the shared sense of what matters and what to do next. The organisation was never the furniture. It was the flow between people — the stories they told, the assumptions they shared, the information moving between them.

The longer I sit with this, the more an organisation looks less like a structure and more like an information system. Not information in the narrow sense of dashboards and reports. Information in the broad communication sense — knowledge, meaning, intent, signals, feedback, culture, the invisible patterns that quietly shape how everyone behaves.

The power of the invisible

Consider culture. Nobody has ever seen it. You cannot point to it on an org chart, photograph it, or install it. And yet it shapes almost everything — what gets said and left unsaid, what gets rewarded, what gets ignored, what feels possible and what feels dangerous. Culture has no substance outside human behaviour, and its effects are entirely real.

The same is true of trust. And purpose. And clarity. And the sense of safety that decides whether anyone says the difficult thing out loud. These don't behave like assets. They behave like conditions.

And conditions are powerful — a gardener understands this instinctively. When a plant is struggling, the first question is never "this plant is faulty, why is it not performing?" It is "what are the conditions?" How much light. How much water. What kind of soil. What, exactly, is holding it back. Is it healthy?

Value as an emergent property

This way of thinking gets interesting when it reaches value itself. Most organisations are built on a simple assumption: value is produced. Work goes in, value comes out, the way a machine turns raw material into finished goods.

But the forms of value that matter most don't seem to work like that. Innovation. Creativity. Trust. Learning. Commitment. None of these can be manufactured on demand. You cannot order a team to be innovative by Friday. You cannot mandate creativity in a policy document. You cannot install trust during a planning cycle. You can only create the conditions in which they become more likely to appear.

That distinction is the whole thing. Producing is different from cultivating. One is built on control and order. The other is built on conditions.

Where the machine is right

None of this is an argument against mechanism. Some of the work genuinely is machine-like, and should be. You want payroll to run like clockwork. You want the safety checks, the financial controls, the supply chain and the release process to be reliable, repeatable and somewhat boring. For the parts of an organisation that must never surprise you, the machine is exactly the right idea.

The error is reaching for that idea and then applying it to everything — including the work that only ever emerges. You cannot schedule an insight. You cannot process-map your way to trust.

So the real skill is telling the two apart. Mechanism buys you reliability. Conditions buy you everything reliability cannot — judgement, invention, commitment, care. A good organisation runs on both. It simply stops treating a conditions problem as though it were a mechanics problem, and then wondering why the new system changed nothing.

What a condition actually is

"Conditions" can sound like weather — vague, atmospheric, a word that means so much it risks meaning nothing. It is the opposite of that. A condition is specific, nameable, and almost always something you can change.

Picture two teams handed the same problem. In the first, a junior engineer suspects they are building the wrong thing, and says so. The room leans in. The assumption gets tested. Two weeks of wasted effort are caught before they begin. In the second team, the same engineer has the same suspicion, glances around the room, and decides to keep it to herself. The idea never leaves her head. Nothing on either org chart explains the difference. The difference is a condition: whether it is safe to be the one who says the inconvenient thing.

Or take attention. Give a team a hard problem and three uninterrupted days, and an idea has room to form. Give the same team the same problem in twenty-minute slivers wedged between six other meetings, and confusing priorities, and it never does. The talent is identical. The idea was always there to be found. The conditions decide whether it can ever take shape.

This is the layer beneath the visible organisation — the climate we rarely look at directly. What people know. What they believe is possible. Where their attention is allowed to rest. What happens to them when they tell the truth. Change those things and behaviour changes, often sharply, without a single box on the org chart being redrawn.

Which is why, when good work stalls, the obvious question is usually the wrong one. We ask who is underperforming. What process is broken. What controls do we need. The gardener would ask a different question — not what is wrong with the plant, but what is wrong with the soil. And often nothing is wrong with the plant at all. The soil, unlike talent or character, is something you can begin changing tomorrow.

The Impact Ladder

This also changes how we think about influence. Most leadership models organise themselves around authority. The Impact Ladder organises around something different — the level at which a person works on the system rather than merely within it.

A Contributor creates outputs. An Enabler shapes the decisions and conditions of others. A Systemic Thinker connects across the whole system. A Creator generates the ideas and concepts everyone else can carry forward. They look like four different roles. They may really be four different depths of interaction with the system.

As people climb, they spend less time producing things directly and more time shaping the environment from which things emerge. It explains something that otherwise looks like a paradox — why the most influential people often seem oddly removed from the work itself. They are not writing every line or making every call. They are shaping the conditions under which thousands of lines and calls become possible.

A different question

The machine metaphor asks one question above all others: how do we get more output? (Usually with fewer people and money).

The conditions metaphor asks another: what environment would make better outcomes almost inevitable?

They sound like cousins. They are not. One starts with control; the other starts with understanding. One assumes value is extracted. The other assumes value emerges.

Perhaps

I am not claiming an organisation is literally an information system. The buildings, the technology, the processes are real, and they matter. But they may not be the whole story — and perhaps not even the part that matters most.

Perhaps the parts that matter most are the ones we cannot see. The meanings people share. The stories they believe. The knowledge they exchange. The trust they build. The conditions they create for one another. Perhaps an organisation is not a machine that produces value, but an information system that creates the conditions from which value emerges — the ground the rest of the Idea to Value system stands on.

And if that is true, then leadership has less to do with controlling people, processes and spreadsheets, and more to do with cultivating the invisible patterns from which people do their best work. The patterns that, given time, harden into culture.

And culture, in the end, may simply be information that has settled into habit.