Your Detailed Change Plan Is the Most Dangerous-Looking Safe Thing You Own

You built the plan because it felt responsible. Milestones, dependencies, a clear sequence from where you are to where you want to be. Your team felt reassured. Your board felt reassured. And then, somewhere around month six, the plan and reality quietly stopped speaking to each other. You kept managing the document. The change drifted.

If that pattern is familiar, you may have applied the right tool to the wrong kind of problem, and discipline may have had little to do with it.

The research that surprised the people running the study

In 1994 two change consultants, Peter Jones and Gina Lawrie, set out to confirm what they assumed every senior leader believed: that structured, programmed planning is what makes organizational change work. They interviewed top managers across thirteen organizations in utilities, banking, health, retail and engineering, all of them well into major change programs.

The answer came back unanimous, and with feeling. From experience, detailed structured planning for change does not deliver the goods, is unresponsive, is unrealistic, and, in their words, can make you look stupid. One manager put it plainly:

"Grand plans do not look intelligent from the bottom, and are bad for morale."

These were people accountable for results who had watched the binder lose contact with the building, not anti-planning cynics.

Why control is mostly an illusion here

An organization is a complex system. Hundreds of people make choices based on their own needs. Feedback loops reinforce or kill the changes you introduce. The environment shifts while you act. In that setting two things are always true: each action has consequences you did not plan, and each step reveals information you did not have when you started.

A fixed plan assumes the opposite. It assumes you can decide the outcomes in advance, specify the sequence, and run a smooth transition to a known future state. For a closed problem that assumption holds. For organizational change it does not, and pretending otherwise is what makes the plan brittle. As Jones and Lawrie put it, the more certainty you assume at the outset, the lower your chances of bringing about useful, sustained change.

The alternative is not drift

The obvious fear is that giving up the detailed plan means muddling through. The research draws a sharp line between an emergent approach and aimlessness, and the line has four words: purpose, insistence, learning, rigor.

Purpose gives the change direction even when the path is unknown. Insistence keeps it an imperative, so the team does not retreat to the comfort of how things were. Learning treats each move as exploratory and reads what comes back, including the resistance. Rigor is the honest, hard thinking that earns the next step. Borrowing Henry Mintzberg's image, you craft the strategy the way a potter crafts at the wheel: you know whether you are making a jug or a plate, and you let the specifics form under your hands.

The practical reframe is to stop planning for change and start building an agenda for it. Work the live issues, challenges, intentions and aspirations the organization has right now. Act on them. Learn. Reset the agenda. The energy comes from real tension in the business, not from a document written eighteen months ago.

What this looks like in practice

Run a simple sort on your current priorities. Some are bridges: closed, well-defined, with a knowable order. Ship the release. Pass the audit. Plan those tightly, because a tight plan is exactly right there.

The rest are organizational change: how people decide, collaborate, and behave. For those, hold a clear objective and a rhythm to learn, not a fixed thirty-six-month map. This is also why an operating cadence matters more than a planning offsite. The quarterly loop, set a direction, act, review what you learned, re-aim, is emergent planning with rigor built in. It is the difference between a living agenda and a dead plan.

The leaders who struggle most are usually the ones who grew up succeeding at bridges, then reached for the same toolkit when the problem changed shape.