How to run a project kickoff meeting
The short answer
A kickoff aligns everyone before work starts. Cover why the project exists, its goals and scope, who does what, the timeline and milestones, known risks and how the team will communicate. End with first actions and owners, and share the notes the same day.
Step by step
- 1
Explain the why
The problem the project solves and what success looks like.
- 2
Agree scope
What's in, what's out and what's still open.
- 3
Clarify roles
Who decides, who does the work and who needs to be kept informed.
- 4
Walk through the plan
Milestones, dates and dependencies.
- 5
Name risks and ways of working
Known risks, meeting rhythm and where updates go.
- 6
Assign first actions
Clear owners and dates for the first week.
Common mistakes
- Leaving scope vague.
- Skipping roles, so decisions stall later.
- Not sharing notes afterwards.
Acta's decisions and RACI template records who owns what from the kickoff itself.
Try Acta free for 15 daysQuestions
Who should attend a project kickoff?
The sponsor, project manager, core team and key stakeholders.
What is a RACI?
A chart showing who is Responsible, Accountable, Consulted and Informed for each piece of work.