How a transition actually works
Most change programmes fail in a predictable way: a plan is made at the top, communicated downward, and then people are asked to accept it. The alternative inverts almost every part of that — and is uncomfortable for exactly that reason.
Why the usual approach fails
The standard change project has a recognizable shape: a steering committee, a target picture, a phased plan, a communication campaign, a pilot in one department. It feels responsible. It also fails often enough that "change management" has become a field mostly occupied with explaining why.
Three of its habits are the actual problem.
Slicing
Run it in one department first, then roll it out. But a cell in a company that still budgets, still measures individuals and still escalates upward is not a pilot of the new model — it is a cell fighting the old one. The pilot fails, and the conclusion drawn is that the model does not work.
Open-ended timelines
"We'll take the time we need" reliably means a project that never ends. The counter-proposal is uncomfortable and specific: fix the time, not the scope. If you set ninety days, it takes ninety days.
Waiting for acceptance
The most common and most expensive habit: first get everyone on board, then act. Agreement in advance is the wrong thing to wait for — it does not arrive, and the waiting itself signals that nothing is really happening. Agreement comes from acting together, not before it.
Five principles that invert it
Principled, not a toolkit
- Start from a coherent set of principles, not a menu of methods.
- The principles have to be talked about constantly — they are not a poster.
Timeboxed
- Fix the time, let the scope adjust.
- Roughly 90 days of core work, about 180 in total.
Radically inviting
- Participation is opt-in; declining carries no penalty.
- Sounds inefficient, and is the opposite: the people who show up are the ones who want to work.
Whole system
- Everyone may take part, across every function and level.
- No pilot department, no "agile HR" slice.
All at once
- The organization flips together rather than in waves.
- Partial states are the most expensive place to stand still.
⚠️ One sponsor with real authority
- One person with formal authority who genuinely wants this.
- Not a committee consensus, not a mandate delegated downward.
- Without it, none of the above holds — this is the single most common reason the whole thing stalls.
What 180 days look like
OpenSpace Beta, the best-specified version of this, is published under a Creative Commons licence and is free to use. Its shape:
The counter-intuitive part is that the two large meetings have no prepared agenda. Whoever comes brings the topics. It is the format's way of demonstrating on day one that this is not a plan being administered.
Two claims worth arguing with
"There is no resistance to change." Pflaeging's provocation: people do not resist the new, they resist being changed, losing status, or being treated unfairly. What gets labelled resistance is usually an accurate response to a bad method. Useful as a corrective — but it can also become a way of dismissing legitimate objections as method problems. Someone who fears for their livelihood is not exhibiting a facilitation failure.
"Change is a flip, not a journey." The pattern changes at once, like milk in coffee, rather than progressing through stages. This is a good antidote to multi-year roadmaps. But note that the same author also describes transformation as a sequence of many small flips repeated a thousand times — which is a great deal more like a journey than the slogan admits.
The honest counter-position
This whole approach rests on a premise the field genuinely disputes: that there is one target pattern worth flipping to.
Beyond Budgeting takes the opposite path. Convert one process at a time, in the order that suits your context, and stop where it stops making sense. That is a great deal easier to sell to a board, and its proponents argue it survives contact with reality better than an all-at-once flip.
Dave Snowden goes further. An idealized future state is, in his account, the classic reason change initiatives fail. He would replace the target picture with direction and speed measured from where you actually are, plus small safe-to-fail experiments — some deliberately contradictory — and let the structure emerge from what works.
If you take one thing from this article, make it the timebox and the invitation. Those two survive translation into almost any approach — including the incremental one.
Where BetaOS fits — and where it does not
A transition is a social process, and software has no useful role in the middle of it. What a tool can do is hold the picture: what the value creation structure looks like today, what changed, and what the numbers did afterwards. The structural views and the rolling trends are useful precisely because they show movement rather than distance from a target.
There is deliberately no transformation module — no phase plan, no progress bar, no maturity percentage. That would turn an invitation into a rollout being tracked, which is the failure mode this article is about.
Sources
- Silke Hermann, Niels Pflaeging: OpenSpace Beta. 2nd edition — the 180-day format, CC-licensed.
- Niels Pflaeging: Secrets of Very Fast Organizational Transformation. BetaCodex Network White Paper No. 15, 2019 — the five principles and the sponsor constraint.
- Niels Pflaeging: Change as Flipping. BetaCodex Network White Paper No. 16, 2019.
- Harrison Owen: Open Space Technology. — the underlying meeting format.
- Bjarte Bogsnes: Beyond Budgeting at 25. 2023 — the incremental counter-position.
- Dave Snowden, Alessandro Rancati: Managing complexity (and chaos) in times of crisis. EU JRC, 2021 — against deterministic target states.
More from the Beta Library: betaos.org/library