Most organisations do not fail because the people in them are incompetent. They fail because incentives, governance, structures, processes and leadership no longer point in the same direction. Everyone optimises locally and rationally. The organisation loses globally.
This is an uncomfortable idea, because it removes the most convenient explanation available to a leadership team: that the problem is a person, a department, or a lack of commitment. It is usually none of those. It is design.
Behaviour is designed, not managed
Every organisation perfectly produces the behaviour it is designed to create. Not intentionally — structurally. If escalation is faster than ownership, people escalate. If reporting is rewarded and refusal is not, people report. If the consequence of a decision lands somewhere other than the authority to make it, decisions become slow, defensive and expensively documented.
None of this requires bad intent. It requires only that the system quietly makes one behaviour easier than another, every day, for years.
If responsibility is not designed into the system, it will depend on individual heroics.
This is why the standard repertoire — another transformation programme, another values initiative, another round of leadership training — so often produces activity without capability. It addresses the behaviour directly, and leaves untouched the conditions that produce it. Six months later the organisation has more meetings, more dashboards and the same pattern.
Responsibility has to be designed
Responsibility cannot simply be assigned. Assignment produces a name in a document. Design produces a situation in which the person named can actually act: with the authority to decide, the information to decide well, the incentive to decide honestly, and the consequence landing close enough to matter.
Where those four do not meet in the same place, one of two things happens. Either the organisation depends on individuals who compensate for the gap through personal effort and reputation — heroics — or it stops deciding altogether and calls the paralysis alignment.
Heroics are seductive because they work. They are also the most fragile capability an organisation can have. They do not scale, they do not transfer, and they disappear the moment the hero leaves, burns out, or is simply on holiday during the wrong week.
Pressure is the only honest audit
Under normal conditions, almost any system looks adequate. Slack absorbs contradiction. Informal networks route around broken governance. Experienced people quietly do three jobs.
Pressure removes the slack. Growth, transition, crisis, succession and transformation are not merely difficult periods; they are the moments in which an organisation finds out what its system can actually carry. What surfaces is rarely a surprise to the people inside it. It was visible for years. It simply had no consequence until it did.
This is why I would rather examine a system before the pressure arrives than explain it afterwards. A controlled test — a stress test, a simulation, a hard diagnostic conversation at board level — produces the same findings at a price the organisation chooses.
Endurance is a design question
The phrase Systems for Eternity is not a promise that anything lasts forever. It is a design standard: build so that what you build does not depend on you.
The true measure of leadership is what still works after you have left. By that standard, a founder-led company where every meaningful decision passes through the founder is not strong; it is borrowed. A transformation that requires its architect to stay is not finished. An advisory engagement that ends with a dependency has failed on its own terms, regardless of the quality of the advice.
The ultimate success of a system designer is becoming unnecessary.
Designing for endurance changes what you build. Decision rights are written down, because tacit authority does not survive a leadership change. Governance is designed to be usable under stress, not only in a steering committee. Roles are defined by the decisions they own rather than the tasks they perform. Feedback loops are installed so that the system can notice its own drift without an external observer pointing it out.
None of this is exotic. It is simply unusual, because it is rarely anyone's job.
What this means in practice
Taking system design seriously has consequences that leadership teams tend to feel before they welcome them.
- Some conflicts stop being interpersonal and become structural — which makes them solvable, but also makes them visible.
- Some processes are removed rather than improved. Every unnecessary process creates friction; every unnecessary decision creates dependency.
- Some authority moves downwards, and the reporting that compensated for its absence moves away with it.
- Some of what was called culture turns out to be an incentive structure, and can be changed on purpose.
The work moves in three movements: orientation, insights, implementation. Orientation creates one honest picture of the situation. Insights turn that picture into decisions rather than observations. Implementation translates decisions into the structures that keep producing the intended behaviour after the mandate ends — which is the only part that ultimately counts.
The question worth asking
There is one question I have never seen a leadership team answer quickly, and never seen it regret answering.
What behaviour is your organisation perfectly designed to produce?
Not what it intends to produce. Not what its strategy describes. What its system — as it stands today, with its current incentives, decision rights and consequences — is reliably producing right now.
The gap between those two answers is the work.