Change management fails most often in the middle, not at the announcement and not at the finish line. The launch is a single event a leader can rehearse. The trough that follows is months long, and it is where structure either holds people through the work or quietly abandons them to it.
The Middle Is Where Change Actually Happens
Every change initiative gets measured by its launch and its outcome. The part that determines both is the middle, the stretch of weeks or months after the announcement wears off and before the new way of working feels normal. Almost no organization designs anything specific for that stretch.
The middle is unglamorous. There is no kickoff energy left and no finish line in sight yet. People are doing the new process badly while still capable of doing the old one well, and that gap is where most initiatives quietly die.
Launch Day Is the Easy Part
A launch event is straightforward to plan. Leadership picks a date, drafts a message, and delivers it with visible enthusiasm. Everyone in the room claps, and for a week or two the energy from that room genuinely carries the work forward.
The mistake is treating that energy as durable. It is not. It decays on a schedule leaders rarely track, and by week six the organization is running on habit and whatever structure someone thought to put underneath the announcement.
The Anti-Pattern: A Kickoff and Then Silence
The common anti-pattern is a strong launch followed by silence. Leadership assumes the message landed once and does not need repeating. Employees, left without further guidance, quietly revert to whatever behavior felt safest before anyone announced anything.
Silence is not neutral. In the absence of continued communication, people fill the gap with their own explanation. The explanation they reach for is usually that the change was not actually a priority. That belief takes far longer to reverse than the original silence took to cause.
Where the Trough Begins
The trough begins the moment the new process gets harder before it gets easier. A new system is slower to use than the one people already knew, error rates tick up, and old workarounds start to look appealing again. This is the exact moment leaders are most tempted to declare success and move on.
Declaring success at this point is premature and costly. The trough has barely started. Leaving now hands the organization back to the old habits at the precise moment those habits were about to lose their grip.
A Calm Read of Who Is Struggling and Why
The right response to a rough middle is not more enthusiasm. It is a calm, specific read of who is struggling with which part of the change, and why. Some resistance is skill-based, some is workload-based, and some is simple grief for a way of working that used to be familiar.
Treating all three the same way wastes effort. A skills gap needs training. A workload gap needs temporary relief. Grief needs acknowledgment, not a slide deck, and confusing the three prolongs the trough well past its natural length.
RACI and a Visible Board for the Messy Middle
Structure in the trough starts with a RACI that survives past launch day. It names exactly who answers questions, who fixes breakages, and who decides when a workaround is acceptable. That structure is a simple accountability framework, not a bureaucratic overlay, and without it employees improvise their own answers.
A simple Kanban board tracking open issues, in progress, and resolved gives the middle a visible pulse. It shows the organization that someone is still watching, which matters more during the trough than at any other point in the change. Organizations that name an owner for every open issue generally find problems close faster than when responsibility stays informal.
What Structure Looks Like Inside the Trough
Concretely, structure means a standing weekly checkpoint, a single channel for surfacing problems, and a named person accountable for closing each one within a set number of days. None of this is glamorous, and none of it depends on elaborate new systems. It depends mostly on someone remembering to show up at the same time every week.
The checkpoint does not need to be long. Fifteen minutes of honest reporting on what is breaking accomplishes more than an hour of reassurance that everything is fine when it plainly is not. Brevity signals that the meeting exists to solve problems, not to perform confidence.
Coaching as the Load-Bearing Wall
Coaching during the trough is different from training before launch. Training explains the new process once, using a fixed model of what correct looks like. Coaching sits with someone struggling through their third failed attempt and helps them find the specific step where they keep losing the thread.
This is the load-bearing wall of the entire change effort. Remove it, and the structure above it, the announcements, the dashboards, the executive sponsorship, all rest on nothing. Employees carry the actual weight of adoption, and coaching is what keeps that weight from crushing them.
Trust Spent Before the Trough Even Starts
Employees who lived through a previous change that was announced with fanfare and then abandoned enter the next one already skeptical. That skepticism is not resistance to this change specifically. It is trust spent on a prior initiative that was never properly finished.
Rebuilding that trust takes longer than building it the first time would have. A leader who wants a smoother middle this time has to account for the debt left over from the last unfinished one. Naming that debt out loud, rather than pretending this initiative starts from zero, is usually the faster path back to credibility.
What an Abandoned Middle Costs in People
An unsupported trough costs more than a missed deadline. It costs the discretionary effort of the people asked to carry the change. That is the extra hour they would have given willingly if someone had shown up to help, and the hour they stopped giving once nobody did.
Protecting human capital during a transition is not a soft add on to the project plan. It is where stakeholder value actually gets built, one supported employee at a time. Skip it, and the next transition starts from a deeper deficit of goodwill than this one did.
Evidence Structure Held People Through the Trough
A regional healthcare provider rolled out a new scheduling system and watched adoption stall at sixty percent through week five, the classic signature of an unsupported trough. Leadership added a daily fifteen minute checkpoint and named a single owner for every open issue, following a straightforward methodology rather than reinventing the response each week.
Adoption reached ninety four percent by week ten. Teams that install a visible structure inside the trough consistently report faster recovery than teams that simply wait for the discomfort to pass on its own. The daily checkpoint cost fifteen minutes and, by the provider’s own estimate, saved roughly six weeks of stalled adoption.
Composure When the Middle Gets Loud
The middle of a change effort is when complaints peak, well before results are visible enough to justify the discomfort people are feeling. Composure here means resisting the urge to defend the decision loudly or retreat from it quietly. Both reactions signal that leadership is rattled, which invites more of the same pressure.
Consistency matters just as much. A leader who wavers on the direction the first time pushback gets loud teaches the organization that complaining works better than adapting. That lesson outlives the current change effort by years.
When to Add Structure and When to Let the Trough Run Its Course
If adoption metrics are flat or falling three weeks after launch, add structure immediately rather than waiting for the numbers to recover on their own. If complaints are rising but adoption is climbing steadily, the trough may simply be running its natural course. That distinction is worth checking weekly rather than assuming it from memory.
Where multiple changes are landing on the same team at once, treat that overlap as the priority problem, not the individual change itself. Sequencing overlapping initiatives matters more than adding structure to any single one of them in isolation. A team absorbing three simultaneous changes needs a sequencing decision before it needs another checkpoint.
Sequencing Support Across the Length of the Change
Support should not be front-loaded entirely into the launch and then removed. It should taper. Support stays heavy in the first weeks of the trough, gets lighter as adoption climbs, and remains available on request after the initiative is declared complete on paper. That taper preserves continuity between the trough and whatever comes next, keeping the team aligned through every stage of the shift.
Ending support the moment metrics look acceptable teaches the organization that improvement is punished with abandonment. Leaders who taper support gradually typically describe steadier adoption curves than leaders who withdraw it all at once. The taper costs little and buys considerable goodwill heading into the next initiative.
Holding People Through the Trough
Structure through the trough protects the people who have to live inside the gap between the old way and the new one. Those are the weeks when neither approach quite works and both feel exhausting. That protection is the actual deliverable of a change management program, not the launch slide.
Change management is not judged fairly by its announcement, and it should not be designed around one either. It is judged by what happens in the unglamorous middle, when the applause has faded and the new way of working still feels foreign. Build for that stretch with a shared account of what is changing, and the launch and the outcome tend to take care of themselves.
Related
The ten underlying principles that keep an initiative from stalling in that stretch are laid out in the guide to what change management actually requires.
