How to Run a Project Kickoff

Key Takeaways

• Four outputs matter: the decider, the definition of done, the exclusions, and the hidden constraints. Everything else is optional.
• Ask who signs off, out loud, in the room. It is the single most valuable sentence in the meeting and the one most often skipped.
• Get the exclusions agreed while everyone is still friendly. Nobody wants to discuss what is not included in week six.
• Hidden constraints are legal review, brand rules, a fixed launch date, an internal politics problem, and a stakeholder who is on holiday. Ask directly; none of them appear on their own.
• Send the summary within a day. An unwritten kickoff decision has a shelf life of about a week.
• The kickoff is where you buy the right to say no later, politely and with a reference.

The Four Outputs

Most kickoff templates run to twenty sections. Four of them carry the value.

Who decides. Not who attends, not who is interested, not who is the client contact. Who has the authority to approve the work as done. Ask it plainly: when this is finished, who signs it off? If the answer is a committee, ask who resolves disagreements inside the committee, and if the answer is nobody, you have found the project's biggest risk on day one, which is exactly when you want to find it.

What done looks like. Not the deliverable list, the outcome. "A ninety second film" is a deliverable. "Something the sales team can open a conversation with, that our CEO is comfortable putting on the homepage" is a definition of done, and it tells you things the deliverable never would.

What is out. Every project has an assumed halo of extra work that lives in the client's head and not in yours. Naming exclusions in the kickoff is a friendly act, done at the only moment when it costs nothing.

The constraints nobody mentioned. Legal review, brand guidelines, an immovable date tied to something you have not been told about, a stakeholder who will be away for two of your six weeks, a previous agency whose work everyone is quietly reacting against. None of these arrive unprompted.

If a kickoff produced those four and nothing else, it was a good kickoff. If it produced a warm feeling and a shared vocabulary but not the name of the approver, it was a meeting.

Ask Who Signs Off, Out Loud

This is the highest-value sentence in the whole meeting and people skip it because it feels blunt.

It is not blunt. It is a normal professional question and clients answer it easily when asked directly. What creates awkwardness is asking it in week five, when the reason you are asking is that two people have given you contradictory notes.

Phrasing that works: "So I route things correctly, who is the final approver on this, and is there anyone else who needs to see it before that point?"

The second clause is the valuable one. It catches the legal reviewer, the brand guardian, the regional lead and the founder who wants a look. Each of them is a week of delay if they appear late and a scheduled step if they appear now.

Write the answer down and put it in the summary email. Not as a gotcha, as logistics. Once "Priya is the approver" is in writing, notes from elsewhere route through Priya without you having to be the one who says so.

If they cannot answer, that is the finding. Say it gently and concretely: without a single approver, contradictory feedback has nowhere to be resolved, and the usual cost is an extra round. Ask them to nominate someone before the first review.

Get the Exclusions Agreed Early

Scope conversations are easy in week one and unpleasant in week six, and the content is identical.

Bring the exclusions to the kickoff already drafted. Not as a contract clause, as a slide or a paragraph: here is what this includes, here is what it does not, and here is what those extra things would cost if you want them.

Clients almost always respond well, because it converts a vague worry about being nickel-and-dimed into a menu they can plan against. Sometimes they buy the extras on the spot, which is a better outcome for everyone than discovering the need in week six.

Your exclusions list is written by your own history. Whatever has previously arrived late and unpaid on a similar project goes on it. That list is short and stable.

Include the round count and what a round is while you are there: two rounds means two consolidated sets of notes from one named approver. Undefined, "two rounds" and "unlimited small changes" mean the same thing.

Ask For the Constraints Directly

Constraints do not volunteer themselves, because the people who know them do not know they are unusual.

Ask a small set of direct questions. Is there a date this cannot move past, and what is tied to it? Does anything here go through legal or compliance, and how long does that usually take? Are there brand rules or a style guide I should have? Is there anything that has been tried before that did not work? Is anyone key away in the next two months?

The "tried before" question is the one that pays. It surfaces the previous attempt everyone is quietly reacting to, which explains preferences that would otherwise seem arbitrary and saves you from proposing the exact thing that failed last year.

Ask about the real audience, not the stated one. Sometimes a piece is nominally for customers and actually for an internal audience: a board, a sales team, a founder's ego. Knowing that changes the work substantially and nobody will tell you unprompted, though most people confirm it when asked whether there is an internal audience too.

The Agenda That Fits in an Hour

An hour is enough if you protect it, and most kickoffs waste the first twenty minutes on introductions that could have been an email.

Five minutes: why we are here and what this meeting is for. Say the four outputs out loud so people know what you are fishing for.

Ten minutes: the client describes the problem, uninterrupted. Not the brief, the problem. The gap between the two is usually the most useful information in the meeting.

Ten minutes: what does done look like. Push past deliverables into outcomes. "How will you know this worked?" is the question that unlocks it.

Ten minutes: scope, exclusions, rounds. The drafted list, quickly, with the extras priced.

Ten minutes: constraints. The direct questions above.

Ten minutes: approvals, timeline and next steps. Who signs off, who else sees it, and what the first milestone is.

Five minutes: anything we have not asked about. This slot produces something surprisingly often, because someone has been sitting on a concern that did not fit any earlier question.

Send the Summary Within a Day

The kickoff's output is not the meeting. It is the document that follows it, and the value decays fast.

Send it within one working day, while everyone still remembers agreeing. A week later, memories have diverged and the summary reads as your interpretation rather than the shared record.

Keep it to one page with five headings: goal and definition of done, scope and exclusions, approver and reviewers, timeline and dependencies, open questions.

The open questions section matters most and gets left off. Anything unresolved in the meeting goes there with a name and a date attached. Unowned open questions become the thing that delays week four.

Invite corrections explicitly. "Reply if anything here does not match your understanding." Silence then becomes agreement you can point at, gently, later.

What This Buys You Later

Every part of a kickoff is an investment in a specific future conversation.

The approver's name prevents the round where two stakeholders disagree and you are the referee. The definition of done prevents the review where someone evaluates the work against a goal you never heard. The exclusions prevent the awkward pricing conversation in week six. The constraints prevent the legal review that appears three days before launch.

Most of the value is the right to say no politely, with a reference. Not "that is out of scope" as an assertion, but "we scoped the 16x9 master and left the vertical cuts out, which I have priced here" as a fact both of you agreed to. That sentence is only available if the kickoff produced it.

Storyflow is our product and it should be described honestly here. It has no meeting agenda templates, no minutes function, no action-item tracking and no calendar integration, so the meeting itself belongs in whatever you already use, and the summary belongs in email or your project tool. The adjacent job is holding the kickoff's outputs where they stay visible: the goal, the exclusions, the constraints and the references on one canvas, so week six can be checked against week one. Paid-only during early access, with the Free plan landing before the end of 2026, and anyone a paid member invites to a board joins free now.

The Bottom Line

A kickoff is a fact-finding exercise disguised as a relationship meeting, and the facts have a short window in which they are cheap to get.

Leave with four things: the decider, the definition of done, the exclusions, and the constraints. If you have those, the meeting worked, whatever else happened.

Ask who signs off, out loud, and ask who else needs to see it first. One sentence, and it removes the risk that causes most overruns.

Bring the exclusions already drafted, because agreeing them in week one is friendly and agreeing them in week six is not.

Ask the direct constraint questions, especially what has been tried before, because nobody offers that information unprompted.

Then write it down within a day and invite corrections. The meeting is not the output; the page is.

A kickoff is not the start of the work. It is the last cheap moment to find out what the work actually is.