From project plan to kickoff presentation
How to turn a written project plan into a short kickoff deck that gets a new group aligned on goals, owners, timeline, risks and how the work will run.
A project plan is usually the most complete document a project will ever have. It has the goals, phases, owners, dates and risks. It’s also long, and most people joining the kickoff haven’t read it.
The kickoff deck has one job: get everyone in the room to the same understanding of the project in about half an hour. You don’t need to write anything new. You need to pick the right parts of the plan and put them in the order a newcomer needs.
What a kickoff actually needs to achieve
Before choosing slides, be clear about what should be true when the meeting ends. For most projects, that’s four things:
- Everyone can say why the project exists in a sentence.
- Everyone knows what they personally own and who to go to for the rest.
- Everyone has seen the timeline and the next milestone.
- Everyone knows how the team will work together: meetings, updates, where decisions are written down.
If a slide doesn’t help with one of those, it probably belongs in the plan, not the deck.
Map the plan to slides
Most project plans have similar sections. Here’s how they usually translate.
| In the plan | In the kickoff deck |
|---|---|
| Background and context | One slide: why this project, why now |
| Goals and success measures | One slide: what success looks like |
| Scope and non-goals | One slide, with non-goals clearly shown |
| Phases and milestones | One timeline slide |
| RACI or owner list | One slide of names against areas |
| Risks and dependencies | One slide, top three or four only |
| Communication plan | One slide: how we’ll stay in touch |
| Detailed task list | Stays in the plan |
That’s eight slides or so, plus a closing slide with first steps. For most kickoffs, that’s plenty.
Writing each slide
Why this project
Lead with the problem, not the solution. “Customers in smaller cities wait longer for deliveries than those in metros, and they’re telling support about it” (an illustrative example) gives the team a reason to care. Then one line on what the project will do about it.
What success looks like
Take the success measures from the plan and keep only the two or three that matter most. Write each as an outcome with a date: “New delivery route live in three pilot cities by the end of March.”
In and out of scope
This slide prevents more arguments than any other. Put what’s in scope on the left and what’s out on the right. Non-goals are often missing from kickoffs, and they’re what people most often assume wrongly.
The timeline
Turn the plan’s phases into one simple timeline: phase names, rough dates and the milestones that end each phase. Mark the next milestone clearly, because that’s what people need to act on this week. Leave the detailed Gantt chart in the plan.
Who owns what
A clear list of areas and owners, with one name per area. If two names sit against one area, that’s worth resolving before the kickoff, not during it. Include the person to ask when nobody seems to own something.
Risks and dependencies
Pick the top three or four risks from the plan, each with an owner and what’s being done. Dependencies on other teams deserve special attention here, especially if people from those teams are in the room.
How we’ll work
Meeting rhythm, where updates are posted, how decisions are recorded and how to raise a blocker. Easy to skip, costly to leave vague.
First steps
Close with what happens in the next week or two: specific actions, owners and dates. That’s what people leave the room with.
Make the plan kickoff-ready first
If the plan is written well, the deck is much faster to build. A few changes to the page help:
- Put a short summary at the top, covering the problem, the goal and the main dates.
- Give each section one heading, ideally written as a statement.
- Use a table for owners and dates rather than sentences.
- Move the task list under an appendix heading at the end, so it doesn’t crowd the story.
If people will join the project after kickoff, turning an onboarding guide into a welcome session uses the same approach for their first week.
Running the kickoff
A kickoff deck is presented, so keep each slide light and talk to it. A few things help on the day:
- Leave time for questions after scope. Disagreements surface here, and it’s better they surface now.
- Ask each owner to confirm their area out loud. It takes a minute and settles a lot.
- Share the plan link at the end, so anyone who wants detail knows where it lives.
After the meeting
Update the plan with anything decided in the room: changed scope, new owners, adjusted dates. The plan stays the source of truth, and the deck is a snapshot of it on kickoff day. If the plan is spread across several files rather than one page, you can build the kickoff deck with AI from a short summary of the project. If the project feeds the team’s goals for the quarter, the same page habits help when you present them, as covered in turning an OKR page into a quarterly goals deck.
Quick check before you present
- Can someone new say why the project exists after the first two slides?
- Are non-goals as visible as goals?
- Does every area have exactly one owner?
- Is the next milestone obvious on the timeline?
- Does the last slide list first steps with names and dates?
If the plan already lives in a well-structured page, Notion2Deck can draft these slides from it, so you can spend your time on the conversation rather than the layout.