The date moves. The budget grows. The team works harder. Yet the decisions that prevented the last go-live are still unresolved.
For the executives funding a stalled SAP implementation, that is an expensive cycle. The business may be paying to keep the legacy environment running while continuing to fund the SAP project. People are carrying the pressure of both. A revised schedule can organize the work, but it cannot, by itself, restore alignment or rebuild trust.
In my conversation with Kim Sorrelle, I described how I approach recovery: understand the business, see the solution, work backward through the steps, and address the human part that gets everyone communicating again. My De-Escalation Breakthrough Formula™ gives that work five pillars: Discover, Diagnose, Design, Deploy, and Deliver.
It is not a substitute for technical expertise. It is the organizational structure that helps the business and its implementation partner use that expertise to move the project forward.
Discover: surface what the status report cannot tell you.
Start with the gap between the reported position and the lived experience of the people delivering the project. Which concerns keep returning? Which decisions are being deferred? Where do executives, project leaders, and business-process owners describe success differently?
Discovery makes those differences visible before another commitment is built on assumptions. It also creates room for the warning signals people may have stopped raising because earlier concerns led nowhere.
Diagnose: distinguish the blocker from the argument about it.
A missed milestone is a symptom. The underlying issue might be a disputed process decision, an unresolved ownership question, a technical dependency, or priorities that change faster than the team can execute them.
Diagnosis separates those conditions from the pressure surrounding them. Customer frustration is real. Partner concerns may also be legitimate. Recovery needs a shared explanation of the risk, not a contest over whose account of the delay wins.
Design: build the recovery around this business.
A plan has to fit the organization that will execute it. In the interview, I spoke about businesses that still rely on a process created decades earlier. Those processes often hold valuable operational knowledge; they also need to be examined against what the transformation now requires.
Design connects the delivery work to the missing communication and accountability structure. That means clarity about who decides, which priorities hold, and how the team resolves a disagreement before it blocks the next dependency.
Deploy: make the agreements usable under pressure.
A recovery document is not an operating rhythm. Deployment puts sponsor conversations, escalation protocols, and peer accountability into practice so the next difficult issue has somewhere productive to go.
The objective is not to eliminate disagreement. It is to prevent disagreement from immobilizing the project or further damaging the implementation-partner relationship.
Deliver: measure what changed, not just what happened.
More meetings and a new schedule are activities. Delivery asks whether the blocking decision was made, whether the team can execute the agreed work, and whether the organization has credible evidence of readiness.
Closing the loop also matters after the immediate escalation settles. The relationship and accountability structures have to hold through the next phase, not disappear when the status report looks better.
The first question is not “What date can we promise?”
It is “What must become true for the next date to be credible?” That question shifts the conversation from reassurance to evidence. It gives executives a basis for recovery decisions and gives delivery teams a clearer path through the pressure.
The framework is structured; the recovery timetable is project-specific. An initial turnaround is not the same as completed testing, cutover, go-live, and stabilization.
If the project keeps receiving new dates without resolving the same old blockers, a private briefing is a confidential place to discuss what is preventing progress and whether independent recovery support is appropriate.
Adapted from Anita Anello’s conversation with Kim Sorrelle and her De-Escalation Breakthrough Formula™ partner overview.