Vizually
ArticleProject Lifecycle3 min read

Fixing a Kickoff Meeting That Surfaced Two Different Campaigns

When a kickoff meeting reveals two stakeholders pointing at different versions of the campaign, individual contributors at enterprises need a fast corrective. A short playbook.

Vizually Team·
Initiation & Chartering

When kickoff reveals two campaigns inside the same brief

A kickoff meeting where two stakeholders describe different campaigns is doing its job. The next 24 hours decide whether you keep the value.
Vizually editorial

Most kickoff meetings end with a polite consensus that turns out to be fictional. A useful kickoff meeting ends with a recognized priority collision — two stakeholders describing what they think the campaign is, in language that doesn't quite line up. The IC running the kickoff has 24 hours to convert that recognition into a written resolution before each stakeholder returns to their team and starts executing against their own version.

This is a corrective playbook for that specific moment. It's not how to run a better kickoff in the future — it's what to do tomorrow morning, with two stakeholders, two implicit campaigns, and a team that's already starting to act.

  1. Hour 0 (in the meeting)
    Name the divergence
    When you spot the divergence, name it. 'I'm hearing two slightly different versions of the campaign — let me play them back.' This is uncomfortable. It's also the only point at which both stakeholders are still in the room.
  2. Hour 1
    Write both versions down
    Send a one-page memo to both stakeholders within an hour of the meeting. 'Here are the two versions of the campaign as I understood them.' Frame it neutrally — both as legitimate, not one as wrong.
  3. Hour 4
    Schedule the resolution meeting
    30 minutes, both stakeholders, the next business day. Not a debate — a single decision: which version of the campaign are we running?
  4. Hour 24
    Document the decision
    After the resolution meeting, send a one-paragraph confirmation to both stakeholders. 'You agreed on X. We will execute against X. Y is explicitly out of scope for this campaign.' Both reply-confirm.

Why naming it in the meeting matters

The single highest-leverage action is naming the divergence while both stakeholders are still in the room. After the meeting, you'll be having two separate conversations, and each stakeholder will have refined their version of the campaign in private. Bringing them together later to reconcile is an order of magnitude harder than naming the divergence when you first see it.

The phrasing matters. 'I'm hearing two slightly different versions' is neutral. 'You two seem to disagree' is adversarial. 'Let me make sure I have this right' is too soft to land. The neutral framing keeps both stakeholders willing to participate in resolution.

What to do if the resolution meeting fails

Sometimes the 30-minute resolution meeting doesn't produce a decision. Both stakeholders hold their position, and neither has the authority over the other to resolve it. This is not a kickoff failure — it's a sponsorship gap, and the corrective is to escalate to whoever sponsors the program above both stakeholders.

Frame the escalation as a request, not a complaint. 'Two stakeholders have valid but different visions for this campaign. We need a single direction by [date] to keep the project on track. Who decides?' Most program-level sponsors are willing to make this call quickly when the question is framed cleanly. The escalation feels political; in practice, it's the most expedient path forward.

For the lighter retrospective version of this work, see the lighter retrospective version; for the heavy handoff version, see the heavy handoff corrective.

More in
CategoryProject Lifecycle

Related reading

Articlethe lighter retrospective versionArticlethe heavy handoff correctiveArticlethe executive kickoff template