> ## Content Index > Fetch the complete content index at: https://www.ariet.net/llms.txt > Use this file to discover other available public pages before exploring further. # Chapter 3: The one difference that changes everything - URL: https://www.ariet.net/chapter-3-the-one-difference-that-changes-everything/ - Published: 2026-10-09T15:41:51.000Z - Updated: 2026-10-09T15:41:51.000Z - Author: Richard Thackeray - Tags: Book > “Purposes are deduced from behavior, not from rhetoric or stated goals.” > Donella H. Meadows, Thinking in Systems: A Primer ## So far Part One asks why operating models keep disappointing. Chapter 1 set out how they fail and why the usual explanations do not account for it. Chapter 2 showed that the formal design is a thin layer over an adaptive system, which responds to the signals it receives rather than to what the design intended. This chapter asks why that gap exists at all, and traces it to one difference between organisations and natural ecosystems. ## And onto chapter 3…… A tempting analogy runs through much organisational thinking: organisations are like ecosystems. They are complex and self-organising, with interdependencies that cannot be fully mapped, and they respond to interventions in ways nobody predicted. Trying to control them directly tends to produce unintended consequences. The analogy is useful, and mostly true; but it has a limit that matters more than any of the ways it is true. Natural ecosystems do not have a purpose placed on them from outside. A forest does not exist to do something; it exists. The feedback loops that keep it viable (nutrient cycles, predator and prey dynamics, the slow accumulation of soil) were not designed. They emerged because systems without them did not survive, so viability itself was the selection mechanism. The conditioning is part of the system, and there is no separation between the ecosystem and what keeps it alive. Organisations differ in one way that changes everything that follows: someone imposes purpose on them. An organisation exists to do something, whether that is serving customers, delivering a mission, generating value or fulfilling a mandate. That purpose did not emerge from the system; it was imposed from outside by the people who created it or now lead it. The adaptive system underneath (the people, the coalitions, the informal norms, the accumulated habits) does not naturally tend toward that purpose. It tends toward its own continuation and interests, which is different. This is how adaptive systems work, and the people in them are doing what people do: adapting to the conditions they find. If the conditions reward the appearance of progress over progress itself, people will produce the appearance of progress. If it is safer to avoid difficult conversations than to have them, those conversations will not happen. If local optimisation is allowed at the expense of enterprise intent, it will happen. None of this requires cynicism or a lack of commitment. The capacity to adapt is one reason we have done well as a species. We read our surroundings and adjust without waiting to be told, and that served us long before anyone drew an organisation chart. Adaptiveness is neutral. It is always accurate, but accurate to the signals people receive rather than to the purpose the organisation has stated. The problem is not that people adapt; it is the mismatch between what the system adapts toward and what the organisation needs it to adapt toward. --- This is the gap that formal design cannot close. You can write the purpose into the mission statement, the values document, the operating model and the performance framework, and you can communicate it in town halls and cascade it through management layers. The adaptive system will read all of that and adapt; but it adapts to the signals those things produce, not to the intentions behind them. If the performance framework rewards individual delivery, the system adapts toward individual delivery, whatever the values document says about collaboration. If the town hall communicates urgency without honesty, the system adapts toward managing the appearance of urgency. The formal design specifies what the organisation says it values; the adaptive system responds to what conditions reward. The two almost always diverge, because conditions are produced by thousands of daily decisions that no one fully coordinates, and when they diverge, the adaptive system wins. The design need not be wrong for this to happen. By itself, design cannot produce the conditions that would orient the adaptive system towards the purpose it was given, so something else has to do that. That something sits between the structure and the people. It lives in the working relationships and shared habits that determine which signals people pay attention to and how they interpret them, placing it outside both the formal design and the values printed on the wall. Most organisations have some of it without having built it on purpose, and they notice it only once it has gone, or more often notice the symptoms of its absence. --- This is also why the neat model is the wrong model. When we treat organisations as systems that can be engineered (where getting the structure right produces the right behaviour, where each layer uses the services of the one below, where clean interfaces and defined accountabilities produce coherent outcomes) we import an assumption from a domain where it holds into one where it does not. In engineering, components do what they are specified to do. In an organisation, components adapt; they read the conditions around them, route around constraints, and develop workarounds nobody designed or can fully see. The organisation is always doing something. The question is whether what it is doing bears any relation to what it was designed to do. Layered models of the OSI kind work because the interfaces between layers are fixed; a network layer does not renegotiate its contract with the layer above. In a human system the interfaces are themselves adaptive. What looks like a clear boundary between strategy and operations, or between leadership and workforce, is renegotiated continuously by the people on both sides of it. The machine model persists for reasons that have little to do with whether it works. The people who rise to lead organisations are the ones who coped with the conditions they found. Their coping strategies come to feel like how things work, and they attribute what they could not see to other people. A model that treats structure as the main lever matches that experience, because the structural levers are the ones they remember pulling. Nobody chose the machine model after comparing it with the alternatives; it persists because the people who decide how organisations are run are the people for whom it appeared to work. Design still matters, and structure provides something organisations need. Borrowing a framing from strength and conditioning, it helps to think of structure as what it provides in a dynamic system: - Mobility, the range of motion the organisation needs; - Stability, the ability to hold position against forces pulling in other directions; - Strength, the capacity to overcome resistance; - And power, the ability to act decisively when action is needed. Structure, in this sense, works like a skeleton; it lets the organisation move. A skeleton without the conditions that keep it oriented and coordinated is only a set of parts that happen to be near each other. The conditions are what turn the parts into a system capable of pursuing a purpose, and those conditions are what this book calls the fabric. Organisations are ecosystems with an imposed purpose, and that imposition makes the fabric necessary. A forest needs nothing beyond its own survival, so nobody needs to tend the conditions that keep it alive. An organisation needs its adaptive system to serve an end the system did not choose. Without deliberate attention to the conditions, the system pursues its own logic, and the formal design becomes an artefact while the organisation carries on doing exactly what it was designed to do, intentionally or not. --- ## A moment to pause If you are living inside this system: the next time a new structure is announced and nothing much changes, you will know why. The structure met the system underneath it, and the system won, which is how adaptive systems work. The question worth asking is what conditions existed, or did not, that would have made the difference. If you are leading: the operating model you commissioned was necessary, but it was not sufficient. What was missing were the conditions that would have let it take root. Those conditions can be built, but they have to be built deliberately, and they have to come first. If you are working to change this: every time you have felt that the real problem sat underneath the structure, you were right. This chapter begins the explanation for that feeling, and the rest of the book is what to do about it.