Execution discipline for long programs is not the same problem as execution discipline for a six-week rollout. A short initiative can survive on launch energy because it finishes before that energy runs out. A multi-year program cannot: it will outlive its launch signals as a matter of arithmetic, and the discipline that matters is what you build to replace them, not how hard you launch. I raise this most often with sponsors and COOs in program reset days, mid-program reviews, and steering sessions where the paper still looks fine but the room senses the program is coasting on fumes nobody’s replaced.

The concept I use here, from my Execution Intelligence™ work on the gap between what organisations decide and what they actually do, is 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. On a program measured in years, its Momentum Half-Life will be reached, usually well before the program’s actual finish line. The question worth asking early isn’t whether that happens. It’s what you’ve built to take over when it does.

Why Long Programs Outlive Their Launch Energy

Every program launches on the same four signals: sponsor attention, novelty, early wins, and the launch clock. I’ve written elsewhere about how each launch signal expires, so I won’t repeat the mechanics, but the short version matters here. Sponsor attention is finite because something newer always competes for it. Novelty is finite by definition; the moment a new way of working succeeds, it stops being new. Early wins are finite because the easiest problems get solved first, and the launch clock is finite because it has an end date, after which dedicated teams get reabsorbed into their normal jobs.

On a program that runs for years, all four run out long before the program does. That’s not evidence of a badly run program; it’s what happens to every program, well-run or not, once enough time passes. Sustaining momentum on multi-year programs isn’t about keeping these four signals alive past their natural life, which is like trying to keep a match burning for three years by wanting it hard enough. The actual discipline is building something else to carry the load those signals were carrying.

What Are Operating Signals, and Why Do Long Programs Need Them Early?

I call the replacement operating signals: durable evidence built into how the organisation decides, funds and measures. There are four I look for on any long program from the start, because long before the program finishes, the launch signals covering for their absence will have gone quiet.

• A standing decision slot, not a report slot, in the executive rhythm: a fixed place used to decide something, not receive an update.
• Resources that visibly move toward the program at defined points: people, budget or time that shift on a schedule everyone can see, not on someone remembering to advocate for it.
• A named measure in a senior leader’s own scorecard: the program is something a specific executive is personally measured on, not a line in a report nobody outside the program reads.
• A visible consequence when the program is deprioritised: something else must visibly change as a result, so deprioritising it becomes a decision someone has to make out loud.

None of these four requires enthusiasm. That’s the point. They keep working on the months when nobody in the room feels energised about the program, which, on a multi-year timeline, is most months.

How to Turn Governance into Decisions, Not Reports

The standing decision slot is the operating signal I see mishandled most often, because the failure is quiet. Take a composite I think of as “Taken as Read”: a multi-year network reliability program in an asset-heavy business. At launch, it’s given a standing slot at the top of the monthly executive meeting, and the sponsor opens with it personally. Eighteen months in, the slot is still there, technically, but it has slid, item by item, to the last position on the agenda, and by the time the meeting reaches it, the paper is “taken as read”: nobody has time left to discuss it, so the update is accepted without a word said. Nobody decided to demote the program; the agenda did it, gradually. But the effect is the same as if someone had decided it out loud: the room now reads the program as less important than it used to be.

The fix isn’t a memo. It’s a structural change to what that slot is for: move it back to the top, and change what happens in it from a report to a decision. Each month, the executive team makes one decision about the program that will be visible within 48 hours, whether that’s releasing a resource or changing a target, or the team formally re-decides whether the program should continue at its current level of investment. This is the First 48 Hours principle applied to governance itself: every recurring governance moment on a long program should end with at least one decision visible within 48 hours. A steering item that only receives reports isn’t neutral. It’s a decay signal, broadcast every month the pattern continues.

Sustaining Momentum on Multi-Year Programs Without Relying on Enthusiasm

The most useful reframe for sponsors is this: sustaining momentum on multi-year programs is not primarily a communications exercise, and it isn’t a matter of keeping belief in the program high across years nobody can picture at the start. It’s a governance design question. The program keeps moving not because people feel motivated about it, but because the organisation keeps being required to decide about it, fund it at defined points, measure someone against it, and notice out loud when it stops being a priority. That’s what should change in year one: instead of planning relaunches to keep the change alive as the years pass, a sponsor should design the four operating signals into how the program is governed from the outset. A program that depends on its launch team’s enthusiasm to survive year three was never going to survive year three.

Where a Speaker on Sustaining Execution After the Initial Launch Fits

I get asked into long programs at a specific moment, and it’s rarely the launch. The launch team doesn’t need convincing; they’re already energised, which is exactly the problem this article is about. I’m more useful later: when a sponsor senses the launch energy thinning and wants the executive team to build operating signals before the gap is visible, or later still, when those signals were never built and the room needs a clear-eyed diagnosis of why the program feels stuck despite still being funded.

As a keynote speaker on execution discipline for long programs, I bring the language and framework for that conversation into a program reset day, a sponsor and steering session, or an executive gathering where a multi-year initiative’s future is genuinely on the table. As a speaker on sustaining execution after the initial launch, the session I run isn’t about restoring enthusiasm; it’s about walking the executive team through which operating signals already exist, which don’t, and what it takes, structurally rather than emotionally, to close the gap before the program reaches its Momentum Half-Life. If your organisation is weighing a keynote speaker for initiative momentum against a live multi-year program, this is the conversation worth having early, not late.

Why This Matters More on Longer Programs

It’s worth being honest about scale. A twelve-month program faces a real but bounded version of this problem; a program running three, five or more years faces a structurally different one. Bent Flyvbjerg’s research on megaprojects, published in the Project Management Journal, argues that large, long-duration undertakings carry a different category of risk than shorter projects: more time for original sponsors to move on and for the case that justified them to stop matching the world they now operate in. I don’t think that applies only to capital projects. A multi-year internal program carries the same exposure, and the longer the timeline, the more it needs structures that don’t rely on anyone’s memory or enthusiasm to stay intact.

Building the Discipline Before You Need It

The practical takeaway is this: don’t wait for the mid-program review to notice the launch signals have faded. By then, the agenda slot has usually already slid, the resourcing has usually already thinned, and the scorecard has usually already stopped mentioning the program by name. Build the four operating signals while the launch signals are still doing their job, so the handover between them is invisible to the rest of the organisation: not heroics in year three, but governance decisions made in year one that nobody notices because nothing ever visibly breaks.

If your program is heading into its second or third year and you want the executive team clear on which operating signals are missing before the launch energy fades, get in touch to start that conversation.