Transformation begins before the world can see it

Inside a chrysalis, nothing appears to happen for days. The casing hangs still. From the outside it looks like waiting. Inside, the caterpillar's body is being taken apart and rebuilt — most of the old structure broken down, and new structures assembled from small clusters of cells that were there all along, held in reserve for exactly this moment.

Organisations go through the same phase, and it is the one leaders find hardest to manage. A transformation has been announced. Money and attention have been committed. People have been told that things will be different. And for weeks, sometimes months, nothing visible changes. The old ways of working are still running. The new ones are not yet ready to be seen.

This is not a failure of the transformation. It is the transformation. The most important work of change happens before anyone outside the work can see it — in decisions about what to stop, in the redesign of how work flows, in the slow shift of what people pay attention to and what they believe will be rewarded. By the time change is visible, most of it has already happened.

The problem is that the quiet phase looks, from a distance, exactly like a stalled programme. And leaders under pressure to show progress often do the one thing that damages it most: they reach for something visible.

Every transformation begins with a promise, and every promise creates an audience waiting to see it kept. Boards want a milestone. Teams want a sign that the disruption is worth it. Sceptics want evidence either way. Silence is uncomfortable for all of them, and most uncomfortable for the person who made the promise.

So the visible gestures arrive. A new name for an old team. A launch event for a process that has not been tested. A dashboard of activity — workshops held, people trained, documents published — that measures effort rather than change. Each of these is understandable. Each tells the organisation that the transformation is about appearances, and each takes energy away from the slower work underneath.

The deeper risk is that the organisation learns the wrong lesson. If what gets celebrated is the announcement, people learn to produce announcements. If what gets measured is attendance, people learn to attend. The new behaviour the transformation needed — the one that takes longest to form and is hardest to see — is quietly crowded out by the behaviour that is easiest to report.

It helps to be specific about what the invisible work consists of, because naming it is the first step to protecting it. In most organisational change, the quiet phase contains four kinds of work.

None of this produces a headline. All of it determines whether the transformation will hold when it finally becomes visible.

Leading through the quiet phase is less about doing more and more about protecting the right things. Five practices make the difference.

The single most useful thing a leader can do is tell people, at the start, that there will be a period when the change is real but not yet visible. Say how long it is likely to last. Say what it will feel like: slower, more uncertain, occasionally frustrating. Say what you will be watching for instead of visible results.

When the quiet phase arrives, it then arrives as something expected rather than something wrong. The same weeks that would have produced anxiety produce patience, because the organisation was told what they would look like.

Outcomes — cost, speed, customer satisfaction, quality — lag behind change by months. If those are the only measures, the quiet phase will always look like failure. Leading indicators are closer to the work and move earlier.

These are imperfect measures, and they should be treated as signals rather than targets. But they give leaders something true to report while the outcomes are still forming, and they keep attention on the behaviour that will eventually produce the results.

In every transformation there is a small group carrying a disproportionate share of the load: the people trialling the new process, absorbing the friction, translating the intent into daily practice. They are usually not the most senior and rarely the most visible.

They need three things. Time, taken explicitly from something else rather than added on top. Cover, so that the temporary dip in their performance during the change is understood rather than penalised. And recognition that is specific — not "thanks to everyone involved", but a clear account of what they solved and why it mattered.

If these people burn out or give up in the quiet phase, the transformation loses the reserve it was going to be built from.

Silence during the quiet phase is filled by rumour. The answer is not more announcements but a steady, modest rhythm: a short update at the same time each fortnight that says what has been learned, what has changed, what has proved harder than expected and what happens next.

The honesty matters more than the frequency. An update that admits a setback builds more confidence than one that reports only success, because people can see for themselves that not everything is going to plan. When leaders describe the quiet phase accurately, people believe them when they later describe the results.

The quiet phase will test whether the new principles are real. A deadline will tempt someone to bypass the new process. A senior stakeholder will ask for an exception. A familiar shortcut will reappear because it is quicker this week.

Each of these moments is small, and each one is watched. Holding the standard — politely, consistently and with an explanation — tells the organisation that the change is not cosmetic. Granting the exception tells it the opposite, far more persuasively than any communication plan can undo.

Not every silence is productive. Some programmes are not in the quiet phase; they have simply stopped. The difference is usually visible to anyone willing to look closely.

A transformation in its quiet phase is full of small movement: problems surfacing and being solved, the language people use beginning to change, a growing number of people who can describe the new way of working without notes. A stuck transformation is still. The same issues come up in every meeting. The new process exists on paper but not in practice. The people who were most engaged at the start have gone quiet.

If the signs point to stuck, the answer is rarely a relaunch. It is usually to go back to the smallest part of the change that worked, understand why it worked, and extend it carefully — rebuilding confidence from something true rather than something announced.

Eventually the casing splits. The new process is simply how work is done. Results begin to move. Someone outside the programme remarks that things feel different, without being prompted.

This is the moment many leaders mistake for the beginning of success. It is closer to the end of the most important part. The work that made it possible was done weeks or months earlier, mostly unseen, by people who carried on without much evidence that it was working.

The leaders who navigate transformation well are not the ones who make change visible quickly. They are the ones who can tolerate — and help others tolerate — the period when it is not visible at all. They prepare people for the quiet phase, they measure what is really changing, they protect the people doing the work and they hold the standard when it is inconvenient.

Then, when the world finally sees the change, they make sure the credit goes to the people who built it in the dark.