A project in which someone asks "So what are we building again?" two months after launch has usually failed to share its purpose and roles at the kickoff. A project that sets off with a broken shared understanding of purpose and roles is hard to rebuild later, and the first 90 minutes become the leverage point that decides its direction for the following months.

Patterns in which kickoffs fail

Many kickoffs are treated only as a ritual for starting a project. That has little effect. The failure patterns share a common structure.

A slide-reading session: The PM reads the materials aloud one-sidedly while participants stay passive. Almost no questions come up

A vague purpose: The definition of success is not shared, so each person starts with a different picture of the finished product

Unclear roles: It is unclear who decides what and who holds approval authority. Decision-making stalls later

Participation in form only: Everyone was invited, but only a few actually speak and no agreement is formed

A 5-element framework for kickoffs

An effective kickoff handles the following 5 elements thoroughly over a 90-minute timeline. If any one is missing, problems tend to appear in later stages.

110 min

The project's purpose and background

Share why this project is being done and what it means for the organization

215 min

Definition of success and KPIs

Make concrete what will count as "done" and "successful"

320 min

Scope and assumptions

State what is in and out of scope. Share assumptions and constraints with everyone

420 min

Roles and responsibilities (RACI)

Chart who decides, who executes, and who reports to whom

525 min

Risks and milestones

Identify expected risks and agree on the key dates

Choosing participants - neither too many nor too few

A kickoff is not an information session. It is a place for decisions and agreement. Choose participants badly, and the discussion scatters and nothing gets decided. Following Bezos's two-pizza rule, keep it to 8-10 people as a rule. If more people need the information, hold a separate large-group kickoff briefing after the kickoff.

Role	Required / optional	Weight of the role
Project owner	Required	Someone who can articulate the definition of success. Holds approval authority
Project manager	Required	The main person in charge of progress. Also writes the agenda
Technical lead	Required	Judges technical feasibility
Design lead	Case by case	Required when UI/UX is involved
Key stakeholders	Required	Representatives of affected departments such as sales and marketing
Team members	1-2 representatives	At least 1 to reflect the voice of those who will build it
Facilitator	Required	The PM can double as facilitator, but separating the roles is preferable

Scheduling in practice - the wall of mandatory attendance

Because a kickoff includes the project owner and decision-makers, finding a slot when every required attendee is free is hard. With a normal coordination flow it tends to land 2-3 weeks out, and the project does not start in the meantime. There are practical techniques to prevent this.

Reserve kickoff slots at the start of the month

Anticipating new projects, tentatively hold 2 slots a month on everyone's calendars as "kickoff reserve slots"

Effect: A wait of several weeks shrinks to a few days

Build around the owner's free slots

First extract free time from the calendars of people whose schedules tend to be packed (executives, department heads), and have other members fit around them

Effect: The number of coordination round trips drops sharply

A rule that allows substitutes

Allow deputies to attend in place of anyone other than the team leads. Only key members attend in person

Effect: Slots that work for everyone become far easier to find

Design it on the assumption of being online

Hold it online instead of insisting on in person. This removes the constraint of securing a meeting room

Effect: The effort of booking a meeting room disappears

Preparing advance materials - getting the most out of the kickoff

If discussion starts from zero on the day of the kickoff, there is not enough time to reach agreement. An effective approach, like the "six-pager" Amazon uses, is to share advance materials at least 24 hours before so that every participant enters the meeting having read them.

Elements to include in the advance materials

The project's purpose and place in the organization (1 page)
Definition of success and measurable KPIs (1 page)
The scope and the reasons for it (1 page)
Key assumptions and constraints (1 page)
An initial draft roadmap (1 page)
3-5 issues to discuss on the day (1 page)

Actions within 24 hours after the kickoff

A kickoff is not complete just because it is over. Only when the minutes of the decisions and the agenda are shared within 24 hours and participants' understanding has been aligned does the kickoff truly end.

Things to finish by the day after the kickoff

Share the decisions as a bulleted list (5-10 items at most)
List open issues with their owners and deadlines
Set the date of the next meeting and send invitations
Open a communication channel for the project
Distribute the final version of the RACI chart
Share the initial version of the risk register

Split the kickoff into 2 stages

Many projects think of the kickoff as a single event, but splitting it into 2 stages tends to work better. The first is a "strategy kickoff" where only decision-makers and the PM set the direction, and the second is an "execution kickoff" with all the members who will carry out the work.

Without this split, the strategy discussion happens in front of the execution members, and it tends to stay superficial. When decision-makers show that they are still thinking things over, execution members cannot move. Settling strategy first and designing execution separately raises the quality of both.

Kickoff design is also an application of event planning timelines. Having a separate facilitator so that the PM can concentrate on the content raises the productivity of the discussion. Schedule control is secured by managing deadlines explicitly.

When launching a new project, if the PM writes out the agenda using the 5-element framework, items they have not yet decided themselves come to the surface. Those are the real issues to discuss at the kickoff.

Scheduling and running a project kickoff