Somewhere around month twelve of a multi-year program, someone on the leadership team says the quiet part out loud: this has lost the room. The steering pack still gets produced, the updates still go out, but nobody believes it’s actually going anywhere, and nobody wants to say so in front of the sponsor. That’s the moment a mid-program reset gets proposed, and it’s also the moment most organisations design the wrong response. I work with executive teams, COOs, and transformation sponsors at exactly this point, usually because someone senior has noticed the program needs more than a status update and less than a funeral. This piece is for whoever is designing that reset session: what it needs to contain, who belongs in the room, and why the instinct to make it louder is the instinct that finishes the program off.

The short version, from my Execution Intelligence™ work: a mid-program reset works by restart discipline, not restart enthusiasm. It is not a relaunch and not a bigger version of the original launch. It is a small number of visible decisions, said honestly, with evidence that lands within 48 hours. Everything else is decoration the program can’t afford at this point.

Why Relaunching a Stalled Program So Often Makes It Worse

Here’s a composite that will be familiar to anyone who has sat through one of these. An enterprise cost-to-serve program, fourteen months in, gets relaunched at a program-wide session as “[Program Name] 2.0”: a new name, a short video, a genuinely energised room. That afternoon, someone forwards the original launch email from more than a year earlier alongside the new one. The language is almost identical. Nobody says anything cynical. Nobody needs to.

That’s the trap built into every relaunch. The room’s energy is real, and there’s genuine research behind why: Hengchen Dai, Katherine Milkman, and Jason Riis found in their “Fresh Start Effect” research that temporal landmarks, such as the start of a new week, month or year, are followed by a measurable rise in aspirational behaviour. A relaunch tries to manufacture exactly that kind of fresh start. I’m not disputing that the effect exists. I’m arguing against relying on it here, because a fresh start creates enthusiasm, not discipline, and a relaunch spends the enthusiasm without producing the discipline the program needs. The organisation, watching from just outside the room, is asking a different question: what, concretely, is different this time. If the answer is a new name and a new deck, the relaunch confirms that the program runs on launch energy and nothing else.

What Is a Mid-Program Reset?

A mid-program reset is a working session, built for a far smaller group than the relaunch invite list, whose purpose is to announce a handful of decisions, already made, that visibly change what happens on the ground within two days. It has three ingredients, and none of them is a video.

• An honest account of what faded, without blame. Not “we lost momentum” as a vague apology, but a specific, non-punitive account of which signals expired, and when.
• The restart decisions, already made. Not workshopped live in front of the group. Decided beforehand, including at least one visible stop, then announced.
• Commitments with a 48-hour horizon. Specific enough that someone in the room could check, two days later, whether they happened.

A relaunch is built to persuade people the program still matters. A reset doesn’t try to persuade anyone of anything. It shows them.

The Second-Wind Moment You Only Get Once

A faded program doesn’t get unlimited attempts at a second-wind moment. I call the underlying pattern 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. Once a program is past it, a mid-program reset is its second hearing, and the organisation gives it exactly one: genuinely curious, cautiously willing to update its view. That’s the only one you get.

If nothing visibly stops, starts, or changes within 48 hours of the reset session, the second chance doesn’t just fail to land. It accelerates the fade, because it proves the “reset” was also launch energy, dressed differently. This is The First 48 Hours applied to a program’s second wind rather than its first launch: a decision is only believed once something visibly stops, starts, or changes within 48 hours of being announced. A reset that can’t produce that evidence has spent its one shot for nothing.

How to Design the Reset Session Backwards from Day Two

Don’t design the session by planning the session. Design it by deciding what will be visibly true on the morning after, and work backwards from there.

Start with the stop. Every reset needs at least one thing that costs something real, not a new report or working group, because starts are cheap and everyone knows it. A workstream limping along, a reporting cadence nobody reads, a governance layer that exists mainly for someone’s visibility: any of these can be the candidate. The stop is what makes the rest of the session credible, because it’s the one thing that can’t quietly be undone by Friday.

Then keep the invite list smaller than instinct suggests. A relaunch wants an all-hands, because its job is spectacle. A reset wants the sponsor, the program lead, and the team leads whose Monday changes because of what gets said. Everyone else can hear about it once there’s something to hear.

The restart decisions themselves are worth naming here, not re-teaching; I’ve covered the restart decisions a sponsor needs to work through elsewhere, and that work happens before you walk into the room, not during it. What the session adds is sequencing: say what faded, announce what’s already decided, commit to what will be visible in 48 hours, in that order, without opening any of it to re-litigation.

What Leaders Must Say Out Loud About Why It Faded

The honesty is where most reset sessions quietly fail, because it’s uncomfortable and there’s a strong pull to skip to the good news. Don’t. People already know the program faded; the open question is whether leadership will say so, without pinning it on the delivery team for conditions leadership itself set.

The Momentum Half-Life framing gives leaders language that is neither apology nor excuse. You can say, plainly, that the program launched on sponsor attention, novelty, early wins and the launch clock, none of which was ever built to last, and all four had expired by the time it stalled. That lands very differently from “we didn’t execute well enough” or “priorities shifted,” phrases people have heard before and don’t believe. Naming the mechanism, rather than assigning fault, is what lets the room move to the decisions instead of relitigating the last twelve months.

Why Re-Energising the Team Is the By-Product, Not the Goal

Once leaders accept a relaunch is the wrong shape, the common next mistake is to redesign the session to be more sincere and more carefully worded, while still aiming it at getting people re-energised. That’s the same wrong target, pursued more gently. A second-wind moment is real, and I’m not asking anyone to ignore how people feel leaving the room. But energy that isn’t backed by a visible decision is the same trap as the relaunch, just quieter. Aim the session at how people feel, and you’ll unconsciously soften the stop and load in reassurance instead of decision; the room feels better for a week and reverts once nothing changes, because feeling energised was never what was missing. What was missing was proof that a decision had teeth. Design for the decision and the visible consequence, and the energy turns up as a by-product; chase it directly and you get a room that claps once and reverts by Thursday.

Bringing Outside Perspective into the Reset

Most of what a reset needs, a sponsor and program lead can build themselves: the honest account, the stop, the 48-hour commitments. Where I get brought in is usually one of two moments: opening the session itself, because a faded program often needs someone outside the internal chain of command to say the honest version of events without it reading as a delivery team covering itself, or stress-testing the reset beforehand, so the stop is real and the commitments are specific enough to be checked. Either way, it sits inside the broader work I speak and consult on as a speaker for a program relaunch or reset.

If your program is at this point, the conversation worth having isn’t about the relaunch deck. It’s about which stop you’re willing to make, and whether you can prove it within 48 hours. If you want to talk that through before you schedule the session, get in touch here.