I have watched three turnarounds unwind after the outside operator left. Two of them were mine. The stabilization was real. The numbers moved. The board celebrated the results. And then, six to eight months after exit, the operation slid back to something close to where it started.
The reason was always the same and it was always the last thing anyone wanted to hear: the handoff was weak. Not the diagnostic. Not the stabilization. Not the operating rhythm we built in months two through nine. The final 30 days, the part everyone treats as a formality, was the part that decided whether the gains held or unwound.
That lesson has changed how I run engagements. The exit is now designed on day one of the contract. Every meeting in the final month is scripted. Every dashboard has a named internal owner before I leave. And the last four weeks of the engagement are the most important four weeks of the whole nine or eleven month arc. What follows is the ritual I use now.
Why the last month is the most fragile
Three things are happening simultaneously in the final weeks of a turnaround, and each of them creates a specific fragility.
The internal team is exhausted. They have been running a rebuilt operation with a heavier weekly cadence for nine months. They are ready for the outside operator to be done, and that readiness makes them under-invest in the transition itself. Everyone wants to declare victory and go back to normal work.
The general managers have gotten comfortable with the current arrangement. They know how to escalate to the outside operator. They know what the weekly P&L review looks like when the outside operator runs it. When that structure changes, even to a competent internal successor, they instinctively test the new arrangement to see if it will hold. If it does not hold in the first three weeks, they revert to old habits.
Ownership is beginning to focus on other priorities. The rescue was the fire that had their attention. Once the fire is out, they naturally shift to growth, capital allocation, and other operational areas. That shift is correct and healthy, but it removes some of the accountability pressure that was helping the rhythm stick.
The last month is not a slow ramp down. It is a specific project with its own scope, its own deliverables, and its own risk of failure. Treat it as the deliverable it actually is.
What decays first when you leave
If you know what will decay first, you can build against it. From watching three engagements slip, the sequence is remarkably consistent.
Fig. 1 · What holds and what slips, month by month, after the operator leaves.
Weeks one to three: the weekly P&L review dies
This is the first thing to go. The weekly P&L review requires someone to prepare the numbers, someone to call the meeting, and someone to hold the general managers accountable for the previous week. If the successor has not been running it for at least a month before you leave, the first weekly review after exit gets postponed. The second one gets shortened. The third one gets skipped. By week four it is a monthly meeting again, which means it is no longer a working meeting.
Weeks four to six: the dashboard stops being updated
Live dashboards need someone to own the data pipeline. If nobody on the internal team was responsible for the weekly refresh, the dashboard stops updating around week five. General managers stop opening it in week six. By week eight it is a broken link in a browser tab, and the leading indicators of drift are invisible again.
Weeks six to twelve: labor variance returns
With the weekly review gone and the dashboard dark, labor variance is the first line to slide. Schedules revert to the pattern of the previous week, then the pattern of the previous month, then the pattern that existed before the turnaround. By month three the labor line is halfway back to the original problem, and by month six it is basically where it started.
Months three to six: the culture reverts
This is the deepest one and the hardest to reverse. When the operating rhythm decays, the culture that the rhythm was producing decays with it. General managers stop naming their P&L levers because nobody asks. Line staff stop hearing weekly updates because nobody sends them. The whole tone that made the turnaround work quietly disappears, and by month nine the operation feels like it did before you arrived, even if some of the numbers still look better on paper.
The exit ritual, week by week
Here is what the last two months of an engagement look like when the exit is designed properly.
Week minus eight: successor formally takes lead
The internal successor, named at contract signing, has been shadowing every recurring meeting for months. Now they become the visible primary. Every general manager one-on-one, every weekly P&L review, every monthly regional review is run by the successor. The outside operator sits in the back, takes notes, and debriefs for 15 minutes after each session.
The debrief is the important part. It is where the successor asks questions they would not ask in front of the general managers, and where the outside operator flags the things they would have done differently. Two months of these debriefs compresses about a year of trial and error.
Week minus six: introduce the successor to every general manager individually
One-on-one, in each general manager's own unit, over a coffee or a walk-through of the floor. The framing is deliberate: the successor is not replacing the outside operator, they are the person who will hold the rhythm you built together. This conversation matters because general managers will accept a peer they have worked with as their new operating leader if they were told directly, and they will resist an announcement-by-email even if they know the person already.
Week minus four: dashboard and document handover
Every dashboard gets a named internal owner. Not a team. A person. That person is responsible for the data pipeline, the weekly refresh, and the escalation of any red line. This is written down and reviewed with the person, not implied.
The operating rhythm document is finalized. One page per recurring meeting: purpose, agenda, cadence, who runs it, what decisions get made, what escalation path exists. Same treatment for every standing report. The whole handoff package should be ten to fifteen pages. Anything longer will not get read.
Week minus two: the diagnostic memo gets shared
This one people forget. The successor needs the diagnostic memo from month one, the one that captured what the original problem looked like before anything was fixed. Without it they cannot recognize the early warning signs when parts of the old pattern start to reappear. That memo, plus a 12-month watchlist of things likely to slip, is what lets the successor lead defensively rather than reactively.
Week minus one: last standing meetings, outside operator silent
The successor runs the weekly and monthly cadences alone. The outside operator attends but does not speak. This is deliberately awkward. Everyone in the room knows you are about to leave, and the silence forces the group to solve the problems in front of them without leaning on you. If a general manager tries to address a question to you, redirect it to the successor. Every time. No exceptions.
Exit week: written handoff, dinner, goodbye
Deliver the final written handoff package. Have a working dinner with the internal leadership team, not a celebration. Talk about what you would watch in the next 90 days, what the successor is going to do first, what ownership needs to protect. Then leave. Cleanly. No lingering.
Fig. 2 · Eight weeks of exit ritual, mapped as milestones.
The post-exit check-ins
The 60-day and 90-day check-ins after exit are contractual. They are not a favor and they are not open-ended availability. They are two structured conversations, each about 90 minutes, with the internal successor and one representative from ownership.
The 60-day check-in has one purpose: audit whether the standing cadence is still running. Is the weekly P&L review happening on time? Are dashboards being updated? Are the general managers still naming their P&L levers? What has slipped? Not to fix any of it, but to name it, so the successor can fix it themselves inside the next month.
The 90-day check-in is the honest look at the numbers. Where has the P&L moved since exit? Which lines are drifting? Which parts of the rebuild are holding? This is also the conversation where you and the successor decide whether any further outside involvement is needed, or whether the internal team has fully absorbed the operating model.
If the answer at 90 days is that the rhythm is holding and the numbers are steady, the engagement is done. If the answer is that a specific piece is slipping, you can offer a narrow, defined re-engagement to shore up just that piece. That re-engagement should be a maximum of three weeks and should not become an open door.
What a good handoff feels like
You can feel a good handoff in the room, even before the numbers confirm it. The general managers stop looking at you when they answer a question. The successor makes decisions without prefacing them. The weekly meeting starts on time whether you are there or not. Small process problems get resolved between meetings, without your involvement, by the successor and the general managers together.
When those signals are present, the exit is the natural next step. The operation has already stopped needing you. Staying longer would create the dependency you spent months preventing.
When those signals are absent, the handoff is not ready and you have to be honest about it. Extending by a month to run one more shadow cycle is far cheaper than exiting on time and watching the operation slide.
The point
A turnaround is not measured in the month you deliver the results. It is measured in month twelve, when the operation is either still running on the rebuilt rhythm or has quietly slipped back to what it looked like when you walked in the door. The number the board celebrates in the exit meeting is only real if it is still real a year later.
Every engagement I take on now treats the exit as the deliverable, not the closing ceremony. The successor is named at contract signing. The shadow month is protected. The dashboards get named owners. The 60 and 90 day check-ins are booked before I leave. The final written handoff is short, specific, and read by the people who need to use it.
The best sign that you did the exit right is that the internal team stops mentioning your name in meetings within about six weeks. That is not sad. That is the goal. The machine is running on its own rhythm now. What you built is theirs. Cadence beats charisma, and the cadence is what stays.