Kickoff Meeting Checklist for Campaign Leads Worried About Late Feedback
When campaign teams don't get told the work is off-track until it's too late, the kickoff is where the feedback void begins. A heavy checklist for delivery managers running creative work.
The feedback that arrives in week eight should have been wired in week one
Most campaign feedback voids aren't created by silent stakeholders. They're created by kickoffs that didn't define when feedback was due.
Mid-size campaign teams routinely receive critical feedback at the worst possible time — usually a few days before launch, from a stakeholder who's been quiet for weeks. The feedback void pattern is most expensive on creative work, where late feedback usually means rework that costs days.
The kickoff meeting is where the feedback architecture is set, even when it isn't named. This checklist identifies what the kickoff needs to produce — concretely, in writing — to prevent the late-feedback failure mode. It's a heavy checklist because campaigns above a certain size genuinely require this level of structure. For lighter campaigns, see the lighter retrospective version.
Pre-kickoff preparation
0 / 5- Identify every reviewer who will see the work before launch — not just attendees of the kickoff
- For each reviewer, document what specifically they'll be reviewing (concept, draft, final cut, copy, legal)
- For each reviewer, document by when their feedback is due — in calendar dates, not project dates
- For each reviewer, document the consequence of late feedback (delay launch, ship without their input, loop them into next campaign)
- Pre-brief every reviewer who can't attend the kickoff itself, in 15-minute conversations
During the kickoff
0 / 5- Walk through the reviewer schedule explicitly. Make every reviewer's deadline visible.
- Ask each function lead: 'When do you need to see something to be useful?' Capture answers.
- Ask explicitly: 'Who reviews this work that isn't in this room? When are they getting it?'
- Establish the default escalation path for missed feedback windows. Document who decides 'ship without it' vs 'delay.'
- Confirm that one person owns chasing late feedback — not the whole team, one named person.
Post-kickoff
0 / 5- Send a recap email within 4 hours, with the full reviewer schedule
- Set calendar reminders for each reviewer 48 hours before their feedback is due
- Set up a single dashboard or doc tracking feedback status per reviewer
- Establish a weekly 5-minute review cadence: who's pending, who's blocking, who's late
- Document the protocol for what happens when feedback arrives outside the agreed window
- Week -1Reviewer pre-briefs15-minute conversations with each reviewer who can't attend the kickoff. Surface direction concerns at concept, not at final review.
- Week 0 (kickoff)Kickoff meetingWalk through the full reviewer schedule. Get acknowledgement from each function lead on the windows they're committing to.
- Week 0, post-meetingRecap and trackingRecap email, calendar reminders, dashboard. Done within 4 hours of meeting end.
- WeeklyFeedback status review5 minutes. Who's pending, who's blocking, who's late. Escalate if any reviewer hasn't responded by 24 hours after their window.
- Pre-launchFinal reviewer check48 hours before launch, confirm every reviewer has signed off. Anyone outstanding gets a final escalation; anyone non-responsive gets a documented 'shipping without feedback' note.
“The first time I ran kickoff with a calendar-date reviewer schedule, three reviewers pushed back saying their dates wouldn't work. Two years earlier, those same reviewers would have been silent at kickoff and surprised us at week eight. Pushback at kickoff is the goal, not the problem.”
Why this checklist is heavy
This is a heavy checklist because the feedback void pattern is one of the most common and most expensive failure modes on mid-size campaign work, and the underlying architecture genuinely requires this much structure. Lighter approaches — 'we'll keep stakeholders informed,' 'we'll loop people in as needed' — are exactly the absence of structure that produces the void.
The checklist appears bureaucratic. In practice, the meeting in which the kickoff happens is the same length whether you have this structure or not. The difference is what comes out of the meeting: a feedback architecture vs an unspecified expectation. The architecture takes the same hour to establish; it just produces different artifacts.
When to skip parts of this
The full checklist applies to campaigns with five or more named reviewers across two or more functions. For smaller campaigns — one or two reviewers, single function — a simpler version works: just the calendar-date schedule and the named owner of late-feedback chasing. The other elements add overhead that the smaller campaign doesn't need.
For the lighter retrospective version of this work, see the silent-disagreement retrospective; for the related corrective on priority collisions, see the priority-collision corrective.