# How to Run a Project Kickoff Meeting: What to Present and Say

A project kickoff should leave everyone able to say the same four things: why the project exists, what's in and out of scope, who does what, and when the key dates are. Present each in a few minutes with example lines rather than long slides, spend real time on risks and how you'll work together, and end by confirming decisions, owners and the next meeting out loud.

By the Speaking Coach team at Sodhera Intelligence. Updated 2026-10-22. Source: https://www.orecci.com/speaking-coach/presentations/project-kickoff/

## What a kickoff is for

A kickoff isn't a status meeting and it isn't a celebration. It's the meeting where a group of people who may not know each other agree what they're doing together. The test of a good one: a week later, ask anyone on the project why it exists and what's out of scope, and they give the same answer.

## A 60-minute agenda

| Time | Section | Who leads | What to cover |
| --- | --- | --- | --- |
| 0–5 | Welcome and introductions | Project lead | Names, roles, one line on what each person cares about |
| 5–12 | Why we're doing this | Sponsor or client | The problem, the goal, how success will be measured |
| 12–22 | Scope | Project lead | What's in, what's out, what's undecided |
| 22–30 | Roles | Project lead | Who decides, who does, who needs to be kept informed |
| 30–38 | Timeline and milestones | Project lead | Key dates and dependencies |
| 38–48 | Risks and assumptions | Everyone | What could go wrong; what we're assuming |
| 48–55 | How we'll work | Everyone | Meetings, tools, updates, how to raise problems |
| 55–60 | Recap and next steps | Project lead | Decisions, owners, the next meeting |

For an internal team, you can shorten scope and roles. For a client kickoff, keep them; that's where future disagreements start.

## What to say, section by section

These are made-up example lines for a website redesign. Adapt them.

### Introductions

Keep them short, and ask for something useful, not just a job title.

> "Let's go round quickly: your name, your role on this project, and one thing you'd like this project to fix for you."

That last part tells you more about stakeholders' real priorities than an hour of interviews.

### Why we're doing this

Ideally the sponsor says this, not the project manager. It carries more weight.

> "Our website was built six years ago. Half our enquiries now come from phones, and the site is hard to use on them. The goal is simple: more enquiries from mobile. We'll know it's worked if mobile enquiries are up by the end of next quarter."

### Scope

Be explicit about what's out. It's the line people forget and the one that causes trouble later.

> "In scope: the public website, all 40 pages, and the enquiry form. Out of scope: the customer login area, which is a separate project next year. Undecided: whether we translate the site. We'll decide that by the end of month one."

### Roles

> "Ana is the decision-maker on design. Raj approves anything touching the enquiry system. I run the plan day to day, so if you're not sure who to ask, ask me."

A simple table on screen helps:

| Area | Decides | Does the work | Kept informed |
| --- | --- | --- | --- |
| Design | Ana | Design agency | Marketing team |
| Content | Marketing lead | Content writer | Ana |
| Enquiry form | Raj | Developers | Sales team |

### Timeline

Give three to five milestones, not a 200-line plan.

> "Designs signed off by March 15. Build done by May 1. Two weeks of testing. Launch the week of May 20. The date most at risk is design sign-off, because it needs three people's approval."

### Risks

Ask the room. People will often name risks in a kickoff that they wouldn't raise later.

> "What worries you about this project? What could stop us hitting May 20?"

Write every answer down, agree the top three, and give each an owner.

### How we'll work

> "We'll meet every Tuesday for 30 minutes. Updates go in the shared channel, not email. If something's blocked for more than two days, tell me directly; don't wait for Tuesday."

### The recap

End by saying the decisions out loud, then put them in writing the same day.

> "So we've agreed: mobile enquiries are the goal, the login area is out, Ana decides design, and launch is the week of May 20. Our top three risks are sign-off speed, content delays and the form integration, with owners named. I'll send this summary today. First Tuesday meeting is next week."

## Slides: fewer than you think

A kickoff deck can be six slides: goal, scope, roles, timeline, risks, ways of working. Put the detail in a shared document. The meeting is for agreement, not reading.

## Delivery tips for leading the meeting

- **Talk less than half the time.** The meeting fails if only you speak.
- **Ask, then wait.** After "What worries you about this?", count to five in your head before filling the silence.
- **Name disagreements, don't smooth them over.** "It sounds like we see the deadline differently. Let's decide that before we leave."
- **Watch the clock aloud.** "We've got eight minutes for risks; let's get the big ones."

Practicing your opening and the risk discussion out loud helps if you're new to leading. Speaking Coach lets you describe the meeting and have a partner play a stakeholder who asks awkward questions, then shows you how you sounded. For the first minutes, see [how to introduce yourself in a meeting](/speaking-coach/guides/how-to-introduce-yourself/).

## Questions people ask

### What should be included in a project kickoff meeting?

The goal and why it matters, scope (in and out), roles, key dates, risks and assumptions, how the team will work together, and agreed next steps.

### How long should a kickoff meeting be?

Often 60–90 minutes for a client project, and 30–60 for a small internal one. Big projects sometimes split it into two sessions.

### Who should attend a project kickoff?

The sponsor, the project lead, the core team and the key stakeholders who'll make decisions. Not everyone who'll ever touch the project.

### Should I use an icebreaker in a kickoff?

A short one that's useful works best, such as asking each person what they want the project to fix. See [icebreakers](/speaking-coach/glossary/icebreaker/) for more.

### What do I send after the kickoff?

A short written summary the same day: the goal, scope, roles, milestones, top risks with owners, and the date of the next meeting.

---
Speaking Coach on the App Store: https://apps.apple.com/app/id6767124039
Speaking Coach on Google Play: https://play.google.com/store/apps/details?id=com.sodhera.speakingcoach