What a Startup Campaign Retro Reveals About the Stakeholders You Missed
On a startup campaign, the people who blocked your launch were rarely surprises in retrospect. A short retrospective practice for individual contributors — and the silent disagreement it surfaces.
The retro question that catches every silent stakeholder
Almost every startup campaign retro has the same buried sentence: 'we should have looped in X earlier.' The retro is where you turn that sentence into a habit.
Startup campaign retros are usually short and energetic — what worked, what didn't, what we'd change. The most useful five minutes you can add is one specific question: who saw this work for the first time at the moment they had to approve or react to it?
That single question surfaces the silent disagreement pattern more reliably than any stakeholder mapping exercise done at brief. People remember vividly when they were surprised. They will name names.
- Retro minute 1Ask the surprise question'Who saw this work for the first time when they had to act on it?' Capture every name surfaced.
- Retro minute 5Ask the second question'For each surprised stakeholder — what would they have said earlier that they didn't get to say?' Capture verbatim.
- Retro minute 10Convert to brief format changeTake the stakeholder names from minute 1 and turn them into a brief template field. The template — not your memory — is what catches them next time.
- Day after retroUpdate the brief templateAdd a line for the surfaced stakeholder class. Share with the team. Reference it in the next brief.
Common surprised-stakeholder classes on startup campaigns
Across startup campaign retros, the same classes of people get named:
- The technical co-founder, on anything touching product positioning
- The head of sales, on anything customer-facing
- The customer success lead, on anything that changes how customers will need to be supported
- A specific senior customer's account manager, when a campaign affects a flagship account
- An external partner or investor, on anything publicly visible
None of these are surprising in the abstract. They're surprising in the specific moment because the brief format didn't have a field for them. Adding the field is the entire intervention.
“Our retros surfaced the same name three campaigns running. We added a 'CTO has seen direction by' line to the brief template. The fourth campaign was the first one without a last-minute scramble.”
Retro output you actually use
0 / 4- A list of surprised stakeholders, with what they would have said
- One concrete change to the brief template — a new field, not a generic reminder
- A note pointing to this retro from the next brief
- A standing 'is anyone going to be surprised by this?' question in future brief reviews
The economy of this retro practice is its appeal: ten minutes added to a meeting that's already happening, one template change, no new process. The leverage is that it surfaces the specific people you missed, in their own words, while the project is fresh enough to remember accurately. For the preventive version on software work, see the startup software wizard; for the corrective version on bigger campaigns, see the seven mistakes article.