The transformation is complete. The project has been handed over, the new structure is in place, the systems are running. The board presentation shows green lights. On paper, everything is fine. <\/p>\n\n
And then you look into the faces of your team.<\/p>\n\n
\nThe most dangerous phase of a transformation is not the storm. It is the silence afterward, when the tension subsides and what the change truly cost becomes visible. <\/strong><\/p>\n<\/blockquote>\n\n
A managing director I advised after an eighteen-month restructuring described it this way: “We achieved everything we set out to do. But my team is burned out. The best people<\/a> seem apathetic, sick leave has increased, and when I mention the next strategic initiative, I see only resignation in their eyes.” He had won the transformation and nearly lost his team in the process. <\/p>\n\n
This is not an isolated case. Organizations invest enormous energy in planning and executing change. There is rarely a plan for the phase afterward. The assumption is: once the change is complete, normal operations resume. This assumption is wrong. After an intensive transformation, an organization needs time to stabilize before it can handle the next change. Ignoring this risks not only the results of the just-completed transformation, but the organization’s overall capacity for change. Three levers help to consciously shape this phase. <\/p>\n\n
Lever 1: Acknowledge the cost before looking forward<\/h2>\n\n
Ronald Heifetz of Harvard Kennedy School distinguishes between technical and adaptive challenges. Technical problems can be solved with existing knowledge: implementing a new system, changing a process, adjusting a structure. Adaptive challenges require people to change their habits, beliefs, or ways of working. Most transformations are adaptive challenges, even when they are planned as technical projects. <\/p>\n\n
The cost of adaptive change is real: people have abandoned routines that gave them security. They have lost roles that shaped their identity. They have said goodbye to colleagues they worked with for years. They have functioned under pressure<\/a> for months, alongside daily operations. Acknowledging this cost is not sentimentality. It is leadership. <\/p>\n\n
A division head I accompanied after a site consolidation took a simple but powerful step: she dedicated the first team meeting after the official project completion exclusively to the question “What did this cost us?” Not financially, but humanly. Her team spoke openly for the first time about what the past months had truly meant. It was not a comfortable conversation. But it was the moment when exhaustion shifted from something unspoken to something acknowledged. And only then was the team ready to look forward. <\/p>\n\n
The most common leadership mistake in this phase: immediately announcing the next initiative. “We completed Phase 1, now comes Phase 2.” That sounds like momentum. To an exhausted team, it sounds like change fatigue, like endless change without breathing room. Research on transformation fatigue<\/a> shows: it is not the individual change that exhausts, but the compression without recovery. <\/p>\n\n
Lever 2: Stabilize before you accelerate<\/h2>\n\n
After a transformation, there is a phase that appears in no project plan: consolidation. The new processes must settle, the new structure must become established, people must arrive in their changed roles. This takes time, and this time is almost never planned. <\/p>\n\n
Stabilization does not mean standstill. It means consciously directing energy toward anchoring what has been achieved rather than toward the next change. In practice, this means: ensuring that the new processes actually work and are not just on paper. Making improvements where implementation has gaps. Supporting people in changed roles, rather than leaving them alone with the new job description. Making successes visible<\/a>, so the team sees that the effort was worthwhile. <\/p>\n\n
Kurt Lewin, the pioneer of organizational psychology, called this final phase “Refreeze.” His model Unfreeze, Change, Refreeze describes what most transformation projects forget. If you do not freeze the new form, the transformation will melt away in the heat of daily operations. The organization falls back into old patterns, quietly and imperceptibly, until someone realizes that everything is back to how it was before. John Kotter calls it “Anchoring Changes in Corporate Culture” and warns against declaring victory too early. Most transformations do not fail at implementation, but at anchoring. If the new ways of working do not become culture<\/a>, then the transformation was a temporary project, not lasting change. <\/p>\n\n
How long this phase lasts depends on the depth of the change. A process change takes weeks. A cultural change takes months. A restructuring that simultaneously changed roles, reporting lines, and ways of working takes six months, sometimes more. The rule of thumb: the deeper the change has intervened in the organization’s fundamental assumptions, the longer the stabilization takes. <\/p>\n\n
Lever 3: Dose the next change wisely<\/h2>\n\n
Eventually the next initiative comes. The question is not whether, but when and how. And here good leadership separates from reckless leadership. <\/p>\n\n
Honestly assess whether your organization is ready. The signals are usually clear: if the team reacts to the mention of a new initiative with cynicism rather than curiosity, it is too early. If sick leave is still above normal levels, it is too early. If the results of the last transformation are not yet stably anchored, it is definitely too early. Pace<\/a> is important, but pace without regeneration leads to exhaustion, not results. <\/p>\n\n
When the time is right, dose consciously. Not every change must be a transformation. Not every improvement needs a major project. Sometimes a targeted adjustment is enough, a quick win<\/a> that shows that change can also be easy. After a major transformation, the organization needs the experience that not every change is exhausting. Otherwise a Pavlovian reaction develops: “Change” = “Pain.” And then you have a resistance problem<\/a> that has nothing to do with the quality of your next initiative, but with the scar of the last one. <\/p>\n\n
Communicate transparently what is coming and what is not. Uncertainty after a transformation is poison. If the team does not know whether the next major change is coming in three months or three years, it remains in crisis mode. Say clearly: “We are stabilizing now. For the next six months we will not change any structures. We are focusing on anchoring what we have achieved.” This provides security. And security is the prerequisite for people to engage again, rather than just function.<\/p>\n\n
Reality Check<\/h2>\n\n
First: Was your last major transformation less than six months ago? Then ask three of your team leaders honestly how their team is doing. Not whether the KPIs<\/a> are right, but whether the people still have energy. <\/p>\n\n
Second: After completing your last transformation, did you consciously plan time to stabilize what was achieved, or did you immediately start the next initiative? If the latter, check whether the transformation results are actually anchored or already eroding. <\/p>\n\n
Third: Ask yourself honestly: Does your team still react to the word “change” with curiosity or already with resignation? If resignation, then your next project is not the problem, but the missing recovery time after the last one. <\/p>\n\n
The Uncomfortable Truth<\/h2>\n\n
Organizations do not become strong through permanent change. They become strong through the alternation of change and anchoring<\/a>, of tension and recovery. Those who chase their team from transformation to transformation, without pause, without acknowledgment, without stabilization, destroy precisely the capacity for change they need. <\/p>\n\n
The best leadership performance after a successful transformation is not the next big idea. It is the discipline to give the team the time it needs. <\/p>\n\n
Further Insights<\/h2>\n\n
Transformation Fatigue<\/a><\/strong> \u2013 Why more and more change leads to less and less impact and how you control the dosage.<\/p>\n\n