Project Kickoff Continuity Wizard for Mid-Size Implementation Teams
A short branching wizard that helps individual contributors at mid-size companies design a kickoff meeting that survives any one person leaving — without making it a heavyweight ceremony.
If the kickoff lives in one person's head, it didn't happen
The test of a kickoff meeting isn't whether everyone enjoyed it. It's whether the project would survive the kickoff facilitator going on vacation tomorrow.
Mid-size implementation projects often pivot on the institutional memory of one person — usually the PM who ran the kickoff meeting. When that person leaves, gets reassigned, or goes on extended leave, the project loses its origin story. Decisions made at kickoff get re-litigated. Trade-offs get re-debated. The single point of failure pattern lives in the kickoff facilitator's memory.
This wizard is a 10-minute exercise to design a kickoff that survives any one person leaving. It's not a kickoff template — it's a set of branching choices about what artifacts the kickoff produces, and how they get distributed.
Step 1: What's the kickoff producing?
0 / 3- Is there a written deliverable that captures the agreed-on scope, timeline, and constraints? (Yes/no)
- Is the deliverable signed by the sponsor and at least one function lead? (Yes/no)
- Is the deliverable in a shared location accessible to anyone joining the project? (Yes/no)
Step 2: Who knows the unwritten context?
0 / 3- Is there a 'context' section that captures political dynamics, sponsor sensitivities, and partner relationships? (Yes/no)
- Has at least one other person been briefed on the unwritten context? (Yes/no)
- Could a new PM, brought in tomorrow, find this context within an hour? (Yes/no)
Step 3: What survives if the facilitator leaves?
0 / 3- If the kickoff facilitator left tomorrow, would the project know which decisions were made and why?
- Would the project know what was discussed but explicitly deferred?
- Would the project know what wasn't discussed and represents a known gap?
Wizard outcomes
Outcome A — All yes. Your kickoff is continuity-resilient. Continue with current practice.
Outcome B — Step 1 has gaps. The basic written record isn't there. Fix this first; everything else depends on it. The kickoff template needs a written output, signed, in a shared location. Each of these is one small change with a large protective effect.
Outcome C — Step 2 has gaps. The written record exists but the unwritten context doesn't. This is the most common gap, because it requires deliberately writing things down that feel awkward to write — political dynamics, sponsor sensitivities, what the actual decision-making looks like vs the formal one. Add a 'context the artifacts don't carry' paragraph to the kickoff document. Brief one backup person on the context.
Outcome D — Step 3 has gaps. The biggest, hardest gap. The kickoff produced documents and even unwritten context, but a new arrival can't figure out what wasn't said. This usually requires a different kind of artifact — a brief journal entry by the facilitator capturing 'things we talked around but didn't resolve.' Three sentences is enough. The journal entry is the most overlooked artifact in mid-size project work.
The wizard's purpose is preventive: design the kickoff once, in a way that doesn't require the facilitator to be present forever. Mid-size companies, with their higher turnover and looser documentation discipline, are the environment where this matters most. For the executive-facing template that builds on these principles, see the executive kickoff template; for the silent-disagreement view of kickoff problems, see the retrospective version.