Project Kickoff Meeting: A 60-Minute Agenda That Works

There is a particular kind of kickoff meeting that you have probably attended. Twelve people join a video call. The sponsor says a few warm words about how excited they are. Somebody shares a slide deck with 38 slides. The project manager reads slides 1 to 22 aloud, in a gentle monotone. At minute 51 someone asks, "Sorry, what is the deadline again?" and nobody knows. The meeting ends with the words "Great, let's circle back." Nobody circles back.

Three weeks later, two people discover that they have been building the same thing, one person discovers that the thing was never approved, and the sponsor discovers that the deadline she had in her head was a month earlier than the one in everyone else's.

A kickoff meeting is the cheapest hour you will spend on a project and the one that most often gets wasted. This guide gives you a 60-minute agenda that works, what to send beforehand, how to run it and what to do afterwards. There is a builder at the end that writes your invitation and agenda for you.

What a kickoff is for

A project kickoff meeting is the first time the people who will do, approve and use the work are in the same conversation about it. It has five jobs:

Share the why. What problem are we solving, for whom, and how will we know it worked?
Agree the scope. What is in, what is out and what does "done" mean?
Clarify roles. Who decides, who does the work, who must be consulted and who just needs to know?
Show the plan. The big milestones, the first 30 days and the dependencies.
Set the ways of working. How often we meet, where we talk, how problems are raised.

It is also the first impression. People decide in the first hour whether this project is organized or chaotic, and they will behave accordingly.

What a kickoff is not: a status meeting, a place to plan in detail, or a surprise party where people learn for the first time what the scope is. If anyone hears something important for the first time in the kickoff, you have not done your homework.

A note on timing. Project standards and textbooks, including the PMBOK Guide as commonly described, tie the kickoff to the point where planning ends and execution begins, with small projects often kicking off earlier, while the plan is still being shaped. In a small business, the practical rule is simple: hold it when the sponsor, the goal and the first steps are clear enough to say out loud, and before the team starts producing. Check the edition of the standard you follow if you need the exact wording.

Before the meeting: the 48-hour prep

Most of a kickoff's success is decided before anyone speaks. Do these things at least two days ahead.

Write the one-page charter. Goal, scope, success measures, constraints, sponsor, project manager. If you do not have one yet, the project charter guide and the first PMBOK step walk you through it in an hour.

Invite the right people. The sponsor, the core team, and the stakeholders who can block or bless the work. Use your stakeholder register so you do not forget the person who will be furious in month three. Keep it under about 10 to 12 people if you can. If more must hear the news, run a short briefing for them separately.

Make sure the sponsor will speak. The first ten minutes should come from the person who asked for the project, in their own words. A sponsor who does not show up tells the room the project is optional, so check the date with them first and see how to keep your executive sponsor engaged.

Send a pre-read, and keep it to two pages. The charter and a draft of the agenda. Ask people to read it, and to reply with one concern or question before the meeting. You will be amazed how many problems arrive by email in advance, where they are cheap.

Prepare the room. A real room with a screen or a whiteboard, or a video call with a shared document everyone can see. Test the link and the sound. Bring a timer, because the agenda has times and times need someone watching.

Decide who takes notes. It should not be the person running the meeting.

The 60-minute agenda

Here is the agenda, minute by minute. It fits a team of up to about a dozen people and a project that is small to medium. You can adapt it, but do not cut the sections, only the time.

0 to 5: Open (the project manager)

Welcome people, say the goal of the meeting in one sentence ("By the end of this hour we all agree on what we are building, who is doing what and what happens in the next 30 days") and set two ground rules: phones away, and questions are welcome at any time. Name the note-taker and the "parking lot," a visible list for topics that are important but belong elsewhere.

The sponsor says, in plain words, why this project exists, what changes if it works and what happens if it does not. They should include at least one number: the money, the time or the customers involved. Then the project manager restates the goal as a sentence everybody could repeat.

Test it: if someone could leave the room and tell a colleague what the project is for in one breath, you are on the right path.

15 to 25: Scope (the project manager)

Walk through three lists:

In scope: what we will deliver.
Out of scope: what we will not do. This is the most important list in the meeting. It prevents more arguments than any other.
Done means: how we will judge that the work is finished, and who accepts it.

You can build the structure behind this with the work breakdown structure, and the habits in how to stop scope creep start here.

25 to 35: Roles and decisions (the project manager, with the team)

Put up the names. For each major piece of work, who is responsible, who approves, who must be consulted and who is kept informed? A RACI chart does this on one page. Then ask the most useful question in project management: who makes the final call when we disagree? Write down the name. Ten minutes spent here saves weeks.

35 to 45: The plan and the first 30 days (the project manager)

Show the milestones, not every task. Three to seven dates the sponsor cares about, then zoom into the next 30 days: what happens first, who owns it and what the first visible result will be. If you have dependencies (for example, nothing can start until the permit arrives), show them. A simple Gantt chart works, and the critical path tells you which delay would hurt most.

45 to 52: Risks and assumptions (everyone)

Ask two questions and give them time:

"What could make this project fail?"
"What are we assuming that we have not checked?"

Go around the table so everyone answers. Write the answers on a visible list. These are the beginning of your risk register; the guide on risk management in plain English shows how to turn them into actions.

52 to 57: How we work together (the project manager)

Agree the rhythm: how often we meet (a weekly 30-minute check-in is a good default), where we talk (one channel, not five), how status is shared, how a problem gets raised and how fast a question should be answered. The communication plan guide has the template, and the status report guide shows what a useful weekly update looks like.

57 to 60: Close (the project manager)

Read back the decisions, the open questions and the actions, each with an owner and a date. Ask for a final "Anyone who cannot commit to this, speak now." Thank people, and end on time. Ending on time is the one thing that proves you take their hours seriously.

A small team of four in a short meeting around a small table with one laptop and notebooks — A charter, an agenda and a plan for the first 30 days: a small table and a short meeting are enough.

How to run the hour

An agenda is a map. These habits are how you actually drive.

Talk less than half the time. If the project manager speaks for more than 25 or 30 minutes of the 60, it is a lecture. Ask more than you tell.

Ask for one concern from each person. Near the end of the risks section, go around the table: "What is one concern you have, and what is one thing you need from the rest of us?" Quiet people are often the ones who know where the bodies are buried.

Treat silence with suspicion. A room of nodding heads is not agreement. Try "What would make you say no to this plan?" or "Who sees a problem I haven't mentioned?"

Use the parking lot. When someone starts a long technical discussion, say, "That matters. Let's put it in the parking lot and schedule time with the right people." Then actually do it.

Keep the sponsor in the room. If the sponsor and a team member disagree about the goal, you want to find out in the kickoff and not in month three.

Write on something everyone can see. Decisions, owners and dates should appear on screen as they are agreed.

Variations for real life

A 30-minute version for a very small project. Merge the sections: goal and scope (10 minutes), roles and plan (10), risks and ways of working (7), close (3). Send the pre-read.

Remote and hybrid teams. Cameras help but are not required. Use a shared document that everyone edits during the meeting, ask people to speak in a set order so that nobody is lost, and keep breaks. Remote meetings drift faster than in-person ones, so be strict about time.

Large projects. Hold two kickoffs: a short one with the sponsor and leaders to agree the goal, scope and decision rights, and a second with the wider team. Do not try to hold a 40-person meeting with a 12-person agenda.

Customer-facing projects. Run an internal kickoff first, so that your team agrees before the customer joins. Then hold a customer kickoff that covers the same ground, with extra time for their definition of success and their availability.

Projects with a lot at stake. Add a pre-meeting with the sponsor to rehearse the "why" so they say it crisply, and a short session afterwards to make sure that what you heard is what they meant.

After the meeting: the first 24 hours and the first week

The kickoff does not end when the call does.

Within 24 hours, send the notes: the decisions, the actions with owners and dates, the open questions, the risks and the parking lot. One page. People who were not there will rely on it.
Update your documents. Fold the new risks into the risk register, the roles into the RACI and any scope clarification into the charter. Ask the sponsor to confirm any change in writing.
Book the next meetings while everyone is still engaged: the weekly check-in and the first review.
Deliver a small first win in the first week. A draft, a decision, a booked appointment, a first cleared obstacle. People judge momentum fast, and a visible early result makes the kickoff look like a promise that is being kept.
Start the scoreboard. Choose two or three numbers you will report every week, as described in your first scoreboard.

A small team in a short stand-up meeting in a bright office, one person speaking and the others listening — One voice at a time, then everyone leaves knowing what happens next. End on time, with owners and dates.

A worked example (illustrative)

Suppose a 12-person accounting office, which I will call Lakeview Tax & Books, is moving its client billing to a new system. All of this is invented.

Why (the owner, 5 minutes): invoices go out an average of 11 days after the work is done, and late invoices cost the office roughly a week of cash flow each month. Goal: invoices out within 3 business days of finishing the work, starting with the January billing cycle.
Scope: in, the migration of current client records and the new invoice template; out, changes to the payroll service and the client portal; done means three consecutive weeks of invoices sent within 3 days.
Roles: the office manager is responsible for the migration, the owner approves the template, two accountants are consulted on the exceptions, and everyone else is informed. The owner makes the final call if the office manager and the accountants disagree.
Plan: first 30 days are data cleanup, a pilot with 10 clients and a training session. A hard date: the old system's subscription ends on January 31.
Risks: client records with missing tax IDs, two accountants who have never used the new system, and the January rush.
Ways of working: a 20-minute check-in every Tuesday at 8:30, one chat channel, a one-page status every Friday.

Total time: 60 minutes, with a pre-read of two pages. Within a day, everyone had notes. A week later the pilot had started. That is the entire miracle: nothing fancy, just being clear before the work begins.

The hall of fame of kickoff mistakes

The 38-slide reading. If you are reading your slides aloud, you could have emailed them.
The absent sponsor. The project's most important person on "a quick call at minute 40."
The surprise scope. A major requirement appears for the first time in the meeting, and the room goes quiet in a bad way.
The unrecorded decision. A great discussion and no notes, so everyone remembers a different outcome.
The eternal "TBD." Roles, dates and owners all "to be decided." The meeting is not a kickoff. It is a rumor.
The 25-person meeting. Many people, few opinions heard.
The overrun. A 60-minute meeting that takes 105, killing goodwill in the first hour.
The "we'll sort out roles later." The sentence that has launched a thousand turf wars.
The cake. Do bring cake if you like, but not instead of a plan.

Try the tool: build your kickoff invitation

The builder below writes a kickoff invitation with a timed 60-minute agenda. The sample is the invented accounting office; replace each answer with your own project. It also warns you when something that usually hurts a kickoff is missing: no measurable goal, no out-of-scope list, no decision-maker, no dates or no first-30-days plan. Nothing you type leaves your browser.

What to do this week

Write the one-page charter, or dust off the one you have.
Choose the date and check it with the sponsor before sending any invitation.
List the people to invite from your stakeholder register, and cut the list to the ones who truly need to be in the room.
Send the pre-read and ask for one concern from each person.
Book the first weekly check-in at the same time as the kickoff.

If you are about to launch a project and want a second pair of eyes on the plan, the charter or the first 30 days, get in touch or look at how I work in Project Focus consulting. The toolkit has free templates for the charter, the RACI chart and the weekly status report.

This is general guidance. The example is invented. Adapt the agenda to the size and risk of your own project.

Frequently asked questions

How long should a project kickoff meeting be?

For most small and medium projects, 60 minutes is enough if people have read a short pre-read. A very small project can use 30 minutes. Large projects usually need two sessions: a short one with leaders and a longer one with the full team.

Who should attend a kickoff meeting?

The sponsor, the project manager, the core team doing the work and the stakeholders who can approve, block or use the result. Keep it to about 10 or 12 people if you can, and brief everyone else separately.

What is the difference between a kickoff and a planning meeting?

A kickoff aligns everyone on the goal, scope, roles, first steps and ways of working. Planning meetings go deeper into schedules, budgets and tasks and can take days. For a small project the kickoff may include light planning, but it should not turn into a detailed planning session.

What if the sponsor cannot attend?

Move the meeting if you can. If you cannot, ask the sponsor to record a short message with the goal and why it matters, and to confirm the scope and decision rights in writing beforehand. A project without a visible sponsor usually drifts.

The Project Kickoff Meeting: A 60-Minute Agenda That Works

What a kickoff is for

Before the meeting: the 48-hour prep