Salvaging an Enterprise Campaign Kickoff That Was Handed Off Mid-Stream

When the kickoff happened, but not with you

Enterprise campaigns sometimes change PM hands two or three times before launch. The original PM moved on, an agency lead transitioned out, an internal lead got pulled into another priority. The campaign continues, but the kickoff — the meeting where the campaign's specific commitments were established — happened before anyone currently running the project was there. The handoff pattern at this scale produces a campaign that's politely operating on a kickoff document that doesn't quite match what's been said in the rooms.

This playbook is a corrective for the delivery manager who's just inherited an enterprise campaign mid-stream and discovered the kickoff is no longer a reliable reference. The mechanics are not complicated; the politics are, and most of this guide is about the politics.

Why this isn't 're-kickoff'

The instinct is to call this a re-kickoff. Don't. The framing matters. A re-kickoff implies the original was wrong, which implicates everyone who attended it — including some people still on the project, and some people whose authority you're going to need. A 'realignment' implies that the original kickoff was correct for the project as it then stood, and that the project has evolved since.

The distinction is mostly cosmetic, but in enterprise contexts cosmetic distinctions matter. People will participate in a realignment that they would resist as a re-kickoff. The output is the same; the framing is what makes the meeting possible.

The gap document

The gap document is the most important artifact in this playbook. It's a one-page internal document — never circulated externally — that captures the specific differences between what the kickoff said and what current understanding is. The format is simple: three columns. What kickoff said. What current understanding is. What's unresolved.

The document serves three purposes. First, it forces you to be specific about gaps that would otherwise stay vague. Second, it gives you the structure for the sponsor reset conversation. Third, it serves as evidence later if anyone challenges the realignment artifact: 'we identified these specific gaps, here's how each was resolved.'

The gap document is not for distribution. The realignment artifact is. The two are different documents serving different audiences.

The sponsor reset

The 30-minute sponsor reset is the conversation that converts a stack of artifacts into a campaign you can actually run. The sponsor is the only person whose authority can supersede the original kickoff. Bring the gap document — but don't lead with it. Lead with a single question: 'If we were starting this campaign today, with what we now know, what would we be trying to accomplish?'

Write down the answer in their words. This is the seed of the realignment artifact. Resist the temptation to translate it into your language. The sponsor's words are what survives the realignment meeting and what other stakeholders will accept.

If the sponsor's answer is materially different from the original kickoff, you have your mandate to realign. If it's substantially the same, the realignment is more about re-broadcasting the original than rewriting it — which is faster and politically easier.

The realignment meeting

The realignment meeting itself runs 60 minutes. The agenda is short.

The first 15 minutes is a recap of the original kickoff, presented neutrally. 'Here's what the kickoff agreed to.' This grounds everyone in shared history.

The next 30 minutes walks through what's changed and what we now think the campaign is trying to accomplish. The sponsor's words — captured in the reset — appear here, attributed to the sponsor. This gives the conversation political legitimacy.

The last 15 minutes establishes the realignment artifact and how it will be used going forward. Single page, signed by the sponsor, circulated within 24 hours, referenced in every status going forward.

The meeting works because it provides a face-saving narrative arc: nobody is wrong, the project has evolved, here's the updated commitment. Stakeholders who would have been defensive about a re-kickoff are usually receptive to a realignment.

When this doesn't work

This playbook fails in two situations. First, when the sponsor isn't available or has moved on — without a sponsor reset, there's no way to legitimize the realignment, and you're trying to lead a meeting from a position you don't have. The corrective is to escalate up one level and find a sponsor's sponsor. Second, when the original kickoff was only weeks ago and the realignment is happening because of a serious problem — in that case, the political cover of 'the project has evolved' is too thin, and you may need to actually call it a re-kickoff and accept the friction.

What you've built

When this works, you've converted a campaign operating on a stale kickoff into a campaign operating on current commitments. The artifacts to keep going forward are the realignment document and the gap document. The gap document is internal and historical; the realignment document is the active reference.

For adjacent corrective work on the priority-collision pattern, see the priority-collision corrective; for the structural protections against this happening in the first place, see the kickoff continuity wizard.