Goal and success criteria
Write the project goal in one sentence and the two or three metrics that define success. Everyone in the room should be able to answer 'what does done look like?' without hesitation. If they can't, write until they can.
Free template
Free kickoff meeting template — start the project on a real whiteboard.
BoardSnap is an iOS app that reads whiteboard photos and produces clean summaries and action items in about ten seconds. This kickoff meeting template gives any project — product feature, client engagement, or marketing campaign — a structured start: goals, scope, team, timeline, and open questions on one board.
Download on the
App Store
Free to start. Pro from $9.99/mo or $69.99/yr.
When to run this
Use this at the very start of any project with more than two people or more than two weeks of runway. A kickoff meeting without a structure produces vague commitments and misaligned expectations — which are the root cause of most project failures.
Budget 60 minutes. Don't use the kickoff to do the planning — use it to align on the plan. The detailed planning happens before or after, not during.
The structure
Scope: in and out
Two columns. Left: what's in scope. Right: what's explicitly out of scope. The out-of-scope column is as important as the in-scope column — it prevents scope creep and saves weeks of misaligned work. If something's not written in either column, it's ambiguous and will become a problem.
Team and roles
Write every person on the project and their role. Not job titles — project roles. Who is the decision-maker (DRI)? Who is the technical lead? Who owns stakeholder communication? One DRI. If two people are the DRI, nobody is.
Key milestones
Four to six milestones from today to project close. Milestone names, dates, and owners. Not tasks — milestones. 'Design review complete' is a milestone. 'Create wireframes' is a task. Tasks go in the project tracker after the kickoff.
Open questions and risks
Write every unanswered question that could affect the project. Write every identified risk. For each: who's responsible for resolving it and by when? Open questions that aren't named in the kickoff don't get resolved — they come back as scope changes.
How to run it
- Send the goal before the meeting
Share a draft project goal 24 hours in advance. Attendees should arrive with a perspective on whether it's right. The kickoff starts at alignment, not at blank-slate brainstorming.
- Draw the board structure before anyone arrives
Five sections, labeled. Goal at the top. Scope columns in the center. Team and roles on the right. Milestones across the bottom. Open questions in the corner. The structure is visible when people walk in.
- Write the goal and get buy-in
Read the goal aloud. Ask: 'Does everyone understand what success looks like?' If anyone hesitates, rewrite the goal on the board until everyone can confirm it without hesitation. Don't move on until this is solid.
- Debate the scope, especially out-of-scope
The out-of-scope column generates the most useful debate. Someone will want something in scope that you've excluded — that conversation belongs in the kickoff, not in week four.
- Assign the DRI and one milestone owner
Before the kickoff ends: write one person as the DRI for the project. Then assign a name to every milestone. If any milestone is unowned, assign it before closing.
- Name open questions and risks
Ask: 'What are we most uncertain about?' Write the answers. Assign each a resolution owner and a date. Open questions that leave the room without an owner are open questions forever.
- Snap with BoardSnap
BoardSnap reads all five sections — goal, scope, team, milestones, open questions. The output is a project brief: milestones as action items, open questions as flagged risks, and the DRI named at the top.
Why kickoff meetings on a whiteboard + BoardSnap is better than digital
A kickoff in a slide deck covers the slides and skips the debate. A kickoff at a whiteboard surfaces the debate because you can't advance to the next slide — the board stays in view until everyone has said what they need to say.
BoardSnap captures the full board — including the things that got crossed out and rewritten — before everyone disperses. The project brief lands in the team's project tracker before the day is over.
Frequently asked
Who should be in a kickoff meeting?
Everyone who is accountable for a milestone or a decision on the project. Not everyone who might be involved — only people with a named role. Kickoffs with 15 people produce diffuse accountability. Kickoffs with five to seven decision-makers produce clear ownership.
Should the kickoff be before or after planning?
After the high-level plan exists, before the detailed work begins. The kickoff is alignment on the plan — it assumes someone has done the work of defining the goal and major milestones. If you don't have a draft plan, hold a planning session first and a kickoff second.
Can BoardSnap read a kickoff board with both text and diagrams?
Yes. BoardSnap AI reads all written text on the board, including text inside diagrams and callout boxes. Complex diagrams with minimal text may produce a summary focused on what's written rather than the diagram structure — label key diagram elements for better output.
Is BoardSnap free?
The free tier includes one project and 30 boards. Pro is $9.99/month or $69.99/year for unlimited boards and AI chat on each project.
Related templates
Discovery call template
The client-facing precursor to the kickoff — understand the need before aligning the team.
Requirements gathering template
Turn the kickoff goals into detailed requirements after the meeting.
Launch plan template
The execution layer that follows the kickoff — distribution and day-one operations.
Run your next kickoff meeting and BoardSnap will summarize it.
No exporting, no transcription. Snap the board, get the action plan.
Free · 1 project, 30 boards
Pro $9.99/mo · everything unlimited
Pro $69.99/yr · save 42%