Goal of a kickoff
The goal is shared understanding of what the project is, who does what, what could go wrong, and what happens in the first two weeks.
Before the meeting
- Share a one-page project brief beforehand
- Confirm who the sponsor and project manager are
- Prepare a rough timeline and scope statement
Project kickoff agenda (2 hours)
- 0:00–0:20
Goals and success criteria
What does done look like? How do we measure it?
- 0:20–0:45
Scope and boundaries
What is in scope and explicitly out of scope.
- 0:45–1:05
Roles and decision rights
Who is responsible, accountable, consulted, informed.
- 1:05–1:15
Break
- 1:15–1:35
Risk scan
Top risks, dependencies and assumptions.
- 1:35–1:50
Milestones and communication
Key dates and how the team communicates.
- 1:50–2:00
First actions
Owners and deadlines for the next two weeks.
Common mistakes
- Turning the kickoff into a status update
- Leaving decision rights unclear
- No first actions assigned
- No communication agreement
After the meeting
Send a follow-up with the goals, scope, roles, risks, milestones and first actions. Schedule the first check-in before the kickoff ends.
Facilitator prompts for each block
- Goals: “Six months from now, what would make us say this project worked? How would we measure it?”
- Scope: “What will people assume we are doing that we are not doing?” Write the answers on an explicit out-of-scope list.
- Roles: “For each major decision on this project, who makes the call, and who needs to be asked first?”
- Risks: “Imagine it is month three and the project is in trouble. What went wrong?” This pre-mortem framing surfaces risks people are reluctant to raise directly.
- Communication: “Where do updates live, how often do we meet, and how do we escalate a blocker?”
- First actions: “What has to happen in the next two weeks, and who owns each item?” Do not accept an action without a name and a date.
Who should attend a project kickoff?
Invite the people who will do the work or make decisions about it: the sponsor, the project manager, the core team leads, and any stakeholder whose sign-off can block delivery. Keep observers out of the working session. If a wider group needs the context, run a short briefing afterward instead of letting a 20-person room slow down the decisions.
The sponsor matters most in the first 20 minutes. Their explanation of why the project exists and what success means carries more weight than the project manager repeating it. If the sponsor can only join for part of the meeting, schedule the goals block first.
Shorter version: a 60-minute kickoff
For a small team or a project under three months, compress the agenda: goals and success criteria (10 minutes), scope and out-of-scope (10), roles and decision rights (10), top five risks (15), first actions with owners (15). Drop the separate milestones block and put key dates into the follow-up document instead.
What you should not cut is the risk scan and the first actions. A kickoff that skips risks produces the “month-three surprise”, and one that skips first actions produces a week of people waiting for someone else to start.
Running a kickoff remotely or hybrid
- Send the one-page brief two days ahead and ask everyone to add one question to it before the call
- Use a shared document as the single record, filled in live, so remote participants see the same thing as the room
- Collect risks silently first (five minutes of individual writing), then discuss, so the loudest voices do not set the list
- Split a two-hour kickoff into two 60-minute calls on consecutive days if attention on video is a problem
What the kickoff follow-up should contain
- The goal statement and the measurable success criteria agreed in the room
- Scope and the explicit out-of-scope list
- A roles table (for example RACI: responsible, accountable, consulted, informed) for the main workstreams and decisions
- The risk list with an owner for each of the top risks
- Milestones, the meeting rhythm and where updates live
- First actions with owners and dates, plus the date of the first check-in
Key takeaway
A good kickoff ends with shared goals, clear roles, a risk list and first actions — not just introductions.
Frequently asked questions
How long should a project kickoff meeting be?+
Two hours covers goals, scope, roles, risks, milestones and first actions for most projects. Small or short projects can do it in 60 minutes by compressing each block; very large programmes sometimes run a half-day kickoff workshop.
What is the difference between an internal and a client kickoff?+
An internal kickoff can discuss risks, staffing and politics openly. A client kickoff focuses on shared goals, scope, contacts, approvals and communication. Many teams run a short internal kickoff first so the client meeting is well prepared.
What should be sent before a kickoff meeting?+
A one-page project brief with the goal, rough scope, timeline, known constraints and the agenda. Sending it at least a day ahead lets the meeting start with discussion instead of background.
Who runs the project kickoff meeting?+
Usually the project manager facilitates, while the sponsor opens by explaining why the project matters and what success looks like. On contentious projects a neutral facilitator can help.
What are the most important outputs of a kickoff?+
Agreed success criteria, an explicit out-of-scope list, clear decision rights, a risk list with owners, and first actions with names and dates. If any of these are missing, the kickoff was a presentation rather than a working session.