Why does momentum disappear after a strong launch, when nobody actually decided the initiative mattered less? I hear some version of that question more than any other, from sponsors in mid-program reviews, COOs in steering sessions where the updates still arrive on time but the room feels different, and program and transformation leaders on reset day. The honest answer is uncomfortable: momentum doesn’t disappear because the launch was weak. It disappears because the launch was strong, and the strength was built on signals that were always going to run out.
That’s not a flaw in your program. It’s the mechanism, and it sits at the centre of my Execution Intelligence™ work on the gap between what organisations decide and what they actually do. I call it 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’s not a number, and it’s not fatigue or morale, but a description of what launch energy is made of, and how each part expires on its own schedule. Naming that mechanism for a leadership team, in the room where the program is being reviewed, is most of what I’m brought in to do at this point.
Why Strong Launches Are Built on Temporary Signals
Every launch that lands well does so because of four signals, and all four are, by design, time-limited. Sponsor attention is visible because it’s new. Novelty is interesting because nobody’s seen it before. Early wins are impressive because they’re the easiest ones. The launch clock creates urgency because it has an end date. None was ever meant to last the life of the program, only to get it moving. The mistake isn’t launching hard; it’s not noticing that whatever carried the program in month one was never built to carry it through month twelve.
What Happens When Sponsor Attention Moves On?
In the early weeks, the sponsor turns up: asking about the initiative in meetings, mentioning it publicly, wanting the update before anyone else does. That visible presence tells the organisation, more clearly than any memo could, that this matters. Then, gradually, the questions get shorter and the update slot moves later in the agenda. It’s tempting to read this as the sponsor losing interest. More often, something more human is happening: a newer initiative needs the same visible presence this one used to have, and there’s only so much of a senior leader’s attention to go around. The sponsor hasn’t stopped caring; they’ve been pulled toward whatever now looks most urgent, and the program that used to have their attention has quietly lost it.
Why Novelty and Early Wins Run Out First
Novelty has a short shelf life by definition: the new way of working is interesting precisely because it isn’t yet the way things are done, so the moment it succeeds, it stops being interesting. A few months in, nobody’s talking about it in the corridor, not because it failed but because it worked. Early wins follow the same arithmetic: the first results are the easiest ones, the problems with no entrenched owner and no real resistance. Once those are claimed, what’s left is harder, the process with a defender, the fix needing a decision three layers up. The program hasn’t failed; it’s simply stopped producing the visible proof that made it feel like it was winning.
What Happens When the Launch Clock Ends?
Most launches run on a dated push: a dedicated team, a defined window, everyone focused on getting it off the ground. That clock is useful precisely because it’s finite. But finite means it ends, and when it does, the dedicated team goes back to their normal roles and the initiative is handed to whoever’s job it now is to keep it running without a launch team’s full attention. Nobody announced a deprioritisation; the calendar simply moved on, from a temporary team’s full focus to a permanent team’s fraction of it.
Why Did the Initiative Slow Down Without Anyone Deciding It Should?
Here is the part that catches leaders off guard: none of the four expiries above is a decision. Nobody decided the sponsor should get quieter, novelty should wear off, or the launch team should disband. Each just happens, invisibly from the top, because none shows up as a line item anyone has to sign off. That’s why an initiative can slow down while its work plan still looks healthy: the metrics measure the work, not the signals quietly making the work feel urgent.
What fills the gap isn’t an announcement. It’s a string of small, unannounced decisions, and the organisation reads every one. This is where The First 48 Hours works in both directions. I usually describe it as proof that a decision has been made: a decision is only believed when something visibly stops, starts or changes in the 48 hours after it. But an unannounced decision has a First 48 Hours too. A quiet reassignment, a skipped steering meeting, a review deferred again for a “better time”: nobody framed any of these as a verdict, but within 48 hours, the people closest to the work have drawn their own conclusion anyway.
Program Drift: How Organisations Read Unannounced Decisions
Consider a composite I’ve seen the shape of more than once, which I think of as the best person, moved quietly. A service quality program is rolled out across a contact centre network. The first few months are strong, with visible improvements and engaged site managers. Around month five, the program’s most respected lead gets reassigned to fix an urgent problem elsewhere, “for a few weeks.” Nobody announces anything, because nothing was decided, at least not on paper. But within 48 hours, the program team and the site managers have read the signal and drawn their conclusion. The few weeks become permanent. Nobody ever formally decided to deprioritise the program; the organisation decided for them, one quiet reassignment at a time. That’s program drift from the inside: not a dramatic call to abandon an initiative, but a sequence of small, defensible moves, each unannounced, each read within 48 hours as a small verdict, until the verdicts add up to an ending nobody chose.
Is It Initiative Fatigue, or Is Your Team Reading the Signals?
Leaders often label this moment initiative fatigue, as though the team has simply run out of energy for this specific program. Sometimes that’s part of it. But what looks like fatigue is more often a team that has correctly read the four expired signals and the unannounced decisions that followed, and has concluded, reasonably, that leadership’s real priorities lie elsewhere. That’s not fatigue; it’s an accurate reading of the evidence in front of them. Ask the question plainly: is the team tired, or are they telling you, through their drop in energy, what your organisation’s unannounced decisions have already told them?
Other things can genuinely slow an initiative: a sponsor change, a wave of other priorities crowding the calendar, or an initiative being absorbed into business as usual before it was ready. But in the mid-program reviews I see most often, the four expiring launch signals and the unannounced decisions that follow them are doing the quiet work, well before anyone reaches for those explanations.
Where This Leaves Sponsors and Executive Teams
If your initiative has slowed and nobody at the top deprioritised anything, the useful question isn’t “who lost interest?” It’s “which of the four signals has expired, and what unannounced decisions have filled the gap?” That’s a diagnostic question, not a motivational one, and I’ve set out a structured way to answer it in a separate piece on how to run a Momentum Audit.
The fix isn’t a bigger relaunch. Launch energy, once spent, doesn’t come back on demand. What holds a program together past its launch is building operating signals before the launch energy runs out, signals that don’t expire on their own. This pattern isn’t unique to any one company: Donald Sull’s research on why good companies go bad, published in Harvard Business Review, describes “active inertia”, organisations doing more of what worked before rather than genuinely changing course. I think the same inertia operates at the scale of a single initiative, drifting back to what it was doing before through the accumulated weight of a hundred small decisions.
The moment I’m most useful in a program’s life isn’t the launch. It’s the session partway through, when the room senses something has shifted but can’t name what. In a program reset day or a sponsor and steering session, I bring the language for what’s happening: which signals have expired, what the unannounced decisions have told the organisation, and what the executive team needs to visibly do in the next 48 hours to reverse that reading. That conversation, held early, is usually cheaper than any relaunch. If your initiative started strongly and has gone quiet, and that’s the conversation your leadership team needs next, get in touch to start it here.
