What a Mid-Size Campaign Kickoff Retro Reveals About Silent Disagreement
On mid-size campaign projects, the kickoff often gets polite agreement that hides real disagreement. A short retrospective practice for delivery managers — and the question that surfaces it.
Polite kickoff agreement is the most common form of silent disagreement
If your kickoff meeting ends with everyone nodding, you don't have agreement. You have a tax bill due in week six.
Mid-size campaign kickoff meetings tend to end the same way: polite agreement, brisk handshake, calendar invitations for the next steering meeting. Six weeks later, the project is dragging because each function has been quietly executing against its own version of the brief. The silent disagreement pattern didn't happen during execution — it happened at kickoff, and nobody named it.
The retrospective intervention is short. Add five minutes to the post-launch retro. Ask one question. The answer surfaces what kickoff didn't.
“We added the question to our retros. The first retro after we did, four people described four different campaigns from the kickoff. None of them were wrong, exactly — but none of them matched, either. Now our kickoff template forces an explicit choice.”
- Retro minute 5Ask the surprise question'When you left the kickoff, what did you think this campaign was?' Each function lead answers in their own words.
- Retro minute 10Compare the answersLay them next to each other. Differences are the silent disagreement that was present at kickoff.
- Retro minute 15Translate to template changeWhat field, in your kickoff template, would have forced the silent disagreement to surface? Add it.
Common kickoff template additions that this retro produces
0 / 4- An explicit primary outcome statement that each attendee acknowledges
- A 'one-line summary in your own words' field that each function lead fills in at the meeting
- An out-of-scope list that's read aloud and acknowledged before the meeting closes
- A recap email sent within 4 hours of kickoff with the meeting's key decisions, requiring reply-confirm
The point of the retrospective question is not to fix the campaign that's already shipped — it's to make the next kickoff structurally less prone to silent agreement. The fastest way to do that is to identify the specific disagreements that went unnamed last time, and add fields to the kickoff template that force those classes of disagreement to be made explicit.
For the corrective version of this work, see the corrective version on enterprise campaigns; for the heavy version focused on the feedback-void pattern, see the feedback-void checklist.