10 Jul Why Lasting Organizational Change Doesn’t Require Big Programs
The most effective change is minimally invasive — it works with your system, not against it
When a crisis looms, management pulls the plan out of the drawer. The plan is usually already finished. A cost-cutting program, a reorganization, a change initiative with a catchy name, and a target year far enough out to sound confident. Everything looks decisive. Almost none of it works. Anyone who wants to understand why minimally invasive organizational development isn’t a compromise, but the more honest structural answer, first has to understand why the opposite fails so reliably.
That’s not down to poor execution. It’s down to the model behind it.
Contents
Why Cost-Cutting Programs and Change Programs Share the Same Root Problem
Dr. Gerhard Wohland describes classic cost-cutting programs with the image of a hot air balloon in trouble. In panic mode, both the sandbags and the gas canisters get thrown overboard. From the management cockpit, both look like weight. On the ground, the difference is existential. Sandbags are a waste. Gas canisters are what keeps the balloon in the air.
The same root problem sits inside large change programs. There, too, the approach is too coarse. “Lack of agility,” “low employee motivation,” “innovation deficit.” Descriptions like that aren’t problems. They’re descriptions of a state. And building an intervention on a state description means building on sand.
The result is programs that cost a lot, run for a long time, and never touch the actual cause of the problem. Not because the people behind them are incompetent. Because the model underneath is wrong. It’s the same model that explains why classic organizational development rarely works in most companies.
The model goes like this: if we describe the problem clearly enough, we can know the path to the solution in advance. We just have to plan carefully enough and execute consistently enough.
I made this mistake myself. In an earlier project, we spent months working through a new organizational structure, discussed it with everyone involved, refined it on flipcharts, and set a launch date. What happened afterward wasn’t what we had planned. The system reacted in a way nobody in the planning room had foreseen. That wasn’t an execution problem. That was the behavior of a complex system under intervention.
What Organizations Have in Common With Living Systems
An organization is not a mechanism. You can’t flip a switch and expect the system to behave differently afterward. Niklas Luhmann described organizations as communication systems that reproduce themselves. Specifically, through the way decisions get made, communicated, and connected to one another. The system follows its own logic. External interventions get processed, interpreted, and sometimes ignored.
That’s not a weakness. That’s the condition that makes a stable organization possible in the first place.
What follows from that: the path from A to B only becomes visible while you’re walking it. Anyone who draws it beforehand is drawing fiction. Accepting that changes your basic stance toward intervention. Not: how do we push the program through? Instead: what’s the smallest possible intervention that hits the relevant cause? And how do we observe what happens next?
This isn’t a method problem. It’s a knowledge problem. Under high dynamics, nobody can have the knowledge it would take to fully plan the path in advance. That applies to external consultants just as much as to management. The difference between good and bad interventions, then, isn’t depth of planning. It’s the accuracy of diagnosis, and the willingness to actually look closely after the intervention.
It also means: interventions have to be observable. Anyone who starts an intervention and then doesn’t systematically check how the system reacted has only done half the job. The intervention is the first step. Observation is the second. Correction, if needed, is the third. Anyone who sees this as a weakness hasn’t understood the model yet. Anyone who recognizes it as a strength stops relying on plans. They start relying on the ability to learn instead.
Four Test Questions for Minimally Invasive Organizational Development
If large programs can’t work for structural reasons, you need a different yardstick. Not for the intervention itself, but for the question of whether an intervention is the right one in the first place. I work with four test questions before I intervene in an organization.
1. Does the Intervention Contribute to Value Creation?
That sounds trivial. In practice, it isn’t. Many measures inside organizations can’t be directly connected to what the company actually delivers to its market. HR initiatives, culture programs, also investments in leadership development can be worthwhile. But only if you can name the specific problem in value creation they address.
“We want a stronger feedback culture” isn’t an acceptable answer to that question. “The error rate in product development is rising because problems get escalated too late” comes much closer. A connection to value creation doesn’t mean every measure has to touch the product directly. HR, finance, and IT exist, ultimately, because there’s value creation that they enable. But the connection has to be demonstrable. If it isn’t, the measure is probably unnecessary.
2. Does the Intervention Address the Cause or the Symptom?
Almost every problem presented inside organizations is a symptom. That’s not due to a lack of intelligence among the people involved. It’s because you rarely see the root cause from inside your own system. You see what hurts.
A concrete example: a company complained about a lack of innovation speed. Workshops were planned, methods were introduced, outside speakers were booked. What a closer look revealed: certain decisions that would have been essential for innovation simply weren’t being made. Not out of disinterest. Because informal power structures made sure every relevant decision had to pass through certain people who had no interest in making it. Leadership was formally in charge but, in practice, a figurehead. No workshop would have changed that.
Patterns like that often shape an organization’s everyday life long before anyone says the words company culture. They also explain why company culture cannot simply be decided.
Finding the root cause takes time and attention on the ground. But it saves all the resources that would otherwise flow into measures that just shift the problem around.
3. Is the Effort Worth It?
An intervention doesn’t have to be big to be effective. The opposite, actually. Precise, small interventions often have more leverage than expensive programs. They sit closer to the cause and destabilize the system less.
The decisive question isn’t: how big is our change budget? The question is: what’s the economic value of the change relative to what the intervention costs, in time, money, attention, side effects? If that math doesn’t work out, the intervention isn’t justified. No matter how convincing it looks in the steering committee.
Large programs often get approved precisely because they’re large. Because scale signals seriousness. Because phase plans and milestones create a feeling of control. That’s understandable. But it isn’t a mark of quality.
4. Is This the Biggest Problem?
Scarce resources belong on the biggest levers. That sounds obvious. In practice, though, the most urgent problem gets addressed, not the most important one. The most urgent problem is whatever is loudest right now. The most important one is whatever limits the organization’s value creation the most.
Those two are rarely the same thing. Whoever tackles the biggest problem creates room for further steps. And they build trust, because a real difference becomes noticeable, not just communicated.
Conclusion: Why Minimally Invasive Organizational Development Is Not a Cost-Cutting Model
Minimally invasive sounds like doing less. That’s the misunderstanding.
It’s not about doing less so less can go wrong. It’s that under high dynamics, the claim that you can fully plan the path in advance simply can’t be honored, structurally. Anyone who accepts that stops investing resources in planning architectures built on a flawed model. And starts concentrating resources where they actually move something: at value creation, at the cause, with a clear economic case.
This isn’t worse change management. It’s more honest change management.
Get in Touch
If you notice that change programs in your organization cost a lot and move little, that initiatives launch and quietly fade out a few months later, it’s worth a different approach. Start smaller. Get closer to the actual cause. Keep a clear connection to value creation.
In an initial conversation, I look together with you at where the real leverage points are in your organization. No charge, no pitch, no obligation.