Applying the lens in a large company
Most transformation programs fail not from lack of budget, but from treating a living system like a machine to be re-engineered.
Where large organizations rust
Two thirds or more of German digital transformation programs miss their goals, and the failures repeat so reliably they can be catalogued. The money was there — German companies held record cash reserves through the 2010s. What failed was the model of change itself: transformation treated as a machine upgrade, announced from the top, executed by decree.
The board announces "we are agile now"; middle managers run the ceremonies and keep the control. Stand-ups happen, decisions don't move. The org chart changed costume while the incentive structure — who gets promoted, who gets blamed — stayed untouched, so behavior stayed untouched too.
SOURCE · specs/digitalization_in_germany.md · leadershipEach department optimizes its own KPI, and the sum is a company nobody chose. Cross-functional value streams die in the gaps between org-chart boxes — not from malice, but because every agent is playing the game it was given.
SOURCE · specs/digitalization_in_germany.md · alignmentDecades of patched core systems make every change risky, so the IT department becomes a gatekeeper whose rational answer is "not until we replace system X" — a multi-year project that keeps not finishing. The people running the old systems become invested in their continuation.
SOURCE · specs/digitalization_in_germany.md · legacyWhat the lens says
A corporation is not a machine with levers but a complex adaptive system: thousands of agents responding to local incentives, producing behavior nobody decreed. That is why culture change cannot be announced — culture is the pattern of what gets rewarded, repeated daily. Change the loops and the incentives, and the culture follows; change the vocabulary, and nothing does.
2016 Incentives, networks, emergence → 2026 Play the coordination games →
What to do instead
Replace the annual program review with a monthly demo of working results — not slides, the thing itself. Your slowest loop is currently a year long; make it thirty days and watch what the organization suddenly notices.
M4 Make failure cheap.Fence off one unit, one quarter, one budget line — and decide before it starts which result ends it. Then praise the team that reports the honest negative: whatever happens to the first failed pilot is what everyone learns to do with failure.
M5 Skin in the game.Let the team that builds it run it — and feel it when it breaks. Handovers to 'operations' sever the loop that makes builders careful.
M7 Decentralize decisions.Give the people closest to the customer real decision rights with a budget line, not a suggestion box — then count how many decisions still queue for the board each month, and treat that number as your speedometer.
Retire these
Announcing culture change in a town hall— culture is what is rewarded, not what is said.Five-year detailed transformation roadmaps— plan the direction, not the path; the path will not survive contact.Buying an innovation lab instead of changing incentives— the lab becomes a zoo the organization visits.Waiting for the big system replacement before improving anything— strangle the legacy system with working seams, piece by piece.