If you are an executive team, a COO, a sponsor or a program lead sitting in a reset session or a steering meeting trying to work out how to diagnose why a transformation has stalled, the honest answer is: not by guessing. In my Execution Intelligence™ work, I have sat in enough of these rooms to know the first move is almost always wrong. Someone proposes a relaunch. Someone proposes a new program director. Someone proposes a communications push. All three are prescriptions, not diagnoses. Before you spend money or credibility on a fix, you need a dated, factual picture of what happened to the program’s momentum, and when. That is what the Momentum Audit gives you, and it is the only thing I recommend running before anyone decides what to do next.
Why Prescribing Before Diagnosing Makes a Stall Worse
A stalled transformation attracts opinions faster than it attracts evidence. Every senior person in the room has a theory, usually shaped by whichever part of the program they touch most often. The sponsor thinks people have lost interest. The program lead thinks the business hasn’t freed up capacity. Someone on the leadership team blames communication and asks for a new set of slides. None of these theories are tested against anything; they’re proximity dressed up as insight. Act on the wrong one and you don’t just fail to fix the stall, you spend a second round of sponsor credibility on a cure for the wrong disease, which makes the next relaunch harder to fund.
In my wider work on initiative momentum I describe the Last Three Decisions Test as a fast way for a leadership team to check whether its decisions are actually changing anything inside the organisation. That test tells you whether a program is past what I call its Momentum Half-Life: how long an initiative can keep moving on its launch energy alone, before the signals that made it feel urgent fade and the organisation quietly concludes it no longer matters. It doesn’t tell you which part of the program’s momentum failed, or when. For that you need a diagnostic, not a screen, and it needs to run before anyone reaches for a fix.
Did It Ever Move? The First Question in Any Momentum Audit
Before I look at what has stalled, I ask the group a blunter question: did this program ever visibly move at all? Some programs described as “stalled” never had momentum to lose. They were announced, resourced and staffed, and then nothing observable happened for months before anyone admitted it. That is a different diagnosis, closer to a program that lost momentum before it ever went live than to the pattern this audit is built for, and the fix isn’t a relaunch of something that never really launched. If the honest answer is yes, people saw things change, then you have a genuine Momentum Audit to run, and the next step is finding out precisely when the moving stopped.
How to Audit the Four Launch Signals
Every program that gets off the ground runs on four signals in its early months: sponsor attention, novelty, early wins, and the launch clock itself. Each fades on its own schedule regardless of whether anything durable has replaced it. The audit’s job isn’t to relitigate how each signal works; it’s to find out, one by one, when each stopped producing anything visible and what, if anything, has taken its place.
The evidence standard I use is The First 48 Hours applied backwards. For each of the four signals, the leadership team looks for the most recent 48-hour window in which that signal produced something visible: a decision that changed a resource, a sponsor action people actually saw, a result the wider organisation noticed without being told about it. Then they write down the date. Not the date of the last update, the last meeting, or the last mention in a report. The date something last visibly moved because of that signal.
Do this honestly and the four dates almost always cluster together, and almost always land months before anyone in the room used the word “stalled”. That gap between when the fade actually began and when the organisation noticed is usually the most uncomfortable and most useful thing the audit produces.
What Counts as Evidence (and What Does Not)
This is where most attempts at diagnosis go wrong, because activity gets mistaken for evidence. A status report going out is not evidence, and neither is a steering meeting happening on schedule. What counts is a visible consequence: a decision that reallocated money or people, a practice that changed and stayed changed, a sponsor doing something in public the organisation noticed. If nobody outside the program team would have noticed it happening, it doesn’t count.
Here is a composite of a pattern I see often, which I think of as the four dates on the whiteboard. A leadership team was running a working-capital improvement program that delivered real early gains: collections tightened, a handful of practices changed, and the organisation could feel the difference for a few months. Then it flattened, and the debate in the room was whether people had simply lost interest. Instead of arguing about motivation, they put the four launch signals on a whiteboard and wrote the date beside each one, the last time it produced something visible within 48 hours. All four dates clustered around the end of the original launch push, months before anyone had used the word stalled. The audit also ruled two things out: the program had one clear owner throughout, and it had visibly moved early. What was left was a straightforward momentum problem with a known start date.
Is This a Momentum Problem or Something Else?
The audit is only useful if it’s willing to conclude that momentum isn’t the issue. Four outcomes tend to show up. The first, as above, is a genuine momentum problem: the launch signals expired and nothing durable replaced them. That’s the case this audit is built for, and it’s the one that routes to the question of how to revive a stalled initiative.
The second is that the program never moved before go-live, which I’ve already covered above and which points somewhere else entirely.
The third is that every task has an owner and the outcome has none, which is a separate diagnosis I call Ownership Fog, and it needs a different fix from anything in this audit.
The fourth outcome is the one leadership teams like least: the program is fine, but it’s one of too many things running at once, competing for the same attention and people as everything else on the agenda. That’s a portfolio question, and no momentum diagnosis will fix it, because the problem was never inside this program.
This kind of mid-program check has a close cousin before launch. Gary Klein’s “Performing a Project Premortem” (Harvard Business Review, September 2007) asks a team to imagine a future failure before a project starts, so they can catch its causes early. The Momentum Audit is its counterpart on the other side of launch: instead of imagining a failure that hasn’t happened, you’re dating one that already has.
What to Do with the Findings
Once the dates are on the wall and the diagnosis is clear, resist the urge to solve everything in the same session. The audit’s job ends at the diagnosis: a dated picture of which signal expired, when, and what, if anything, replaced it, plus a clear answer on whether this is a momentum problem at all. What the leadership team does with that finding, whether to revive the program, reset its sponsorship, or fold it into a broader portfolio decision, is a separate conversation. I’d rather a team leave with an accurate diagnosis and an unresolved decision than a decision built on the wrong diagnosis.
Running the Audit as a Working Session
I don’t think this audit works well as a document that circulates for comment. It works as a facilitated working session where the leadership team puts the dates on the wall together and sits with what they say before anyone is allowed to propose a fix. That’s usually where I come in: not to tell a team what happened to their program, but to hold the room to the discipline of finding the dates before reaching for the cure. If your transformation delivered a strong start and has since gone quiet, get in touch to run the Momentum Audit as a working session with your leadership team.
