Ask a leadership team why a program has stalled and they will give you a confident answer. Ask the people three levels down doing the actual work and you will get a different answer entirely. Most operators treat this as noise, a normal amount of organizational fog to be expected in any company past a certain size. It is not noise. It is the single most valuable diagnostic signal available, and almost no one is set up to read it.
The instinct in operations leadership is to trust the account that comes from the top of the org chart, because it arrives with the most authority and the least friction to act on. That instinct is backwards. Leadership's account of a stalled program is a hypothesis, not a finding, and treating it as settled fact is the first and most expensive mistake in any turnaround. The real diagnostic work starts by refusing to take that account at face value and instead laying every account, from the top down to the people closest to the work, side by side.
This is the first stage of the Gap Diagnostic: Listen. Not a survey, not a town hall with a predetermined conclusion, a genuine listening tour that treats every conversation, at every level, as equally weighted data. The wide variance between what leadership believes is happening and what the working team experiences is not a communication problem to smooth over. It is the finding itself.
The second stage, Map the Gap, is where most consulting engagements quietly fail before they begin. It is tempting to average the accounts into something diplomatic, a synthesis everyone can nod along to. That instinct produces a report nobody disagrees with and nobody acts on, because it has sanded off the one detail that actually mattered: where the accounts diverge the most. The widest gap in that spectrum, between what leadership sees, what middle management protects, and what the working team lives, is where the real system failure is hiding. Middle management's account deserves particular scrutiny here, not because the people in it are dishonest, but because their account is structurally built to protect the org chart above and below them. It is the least reliable data point in the room precisely because it has the most incentive to sound resolved.
Once the gap is named accurately, the third stage, Rebuild the System, becomes possible. This is where the difference between an operator and an advisor shows up in the work itself, not just the résumé. Rebuilding process and accountability at the exact point of failure, with the people who do the work rather than for them, requires the kind of credibility that comes only from having actually run engineering, operations, or a P&L. A team can tell the difference between someone redesigning their workflow from a framework and someone redesigning it from having carried the same kind of accountability themselves. The fix has to be built at the gap, not applied around it as a patch, or it will not hold once real pressure returns.
The fourth stage is the one that separates a real fix from a consulting engagement that quietly reverts once the operator leaves: Hand Back the Machine. No process stays correct on its own. Systems drift, priorities shift, and a structure that was airtight at handoff degrades unless someone has been shown how to keep it current. The goal of this stage is not a document or a template, artifacts nobody opens twice. It is a cadence, a way of operating, installed in the organization itself, so the system keeps healing when the operator is no longer in the room. An organization that has been handed a self-healing structure behaves differently under pressure than one that was handed a report.
The pattern underneath all four stages is the same: the reflex to diagnose a stalled operation as a people problem, a team that is too slow, or does not care, is almost always wrong, and it is wrong in the same direction every time. It points blame downward, at exactly the people who have the least power to fix a structural gap and the most accurate read on where it actually is. The fix is not more management pressure on the team. It is a leadership team willing to hear an account of their own operation that contradicts their first instinct, and an operator willing to name that gap plainly instead of managing around it.
That willingness, more than any framework, is what makes a turnaround hold.