---

title: "The kickoff meeting: the hour that shapes the whole project"

module: 6

module_title: "Meetings, Demos & Workshops"

order: 2

access: "paid"

summary: "Run the kickoff as a working meeting that produces clarity instead of a ceremony that produces excitement. Covers mapping who gives feedback and who decides, asking what success looks like in the client's words, surfacing past vendor history, agreeing on logistics, and closing with a concrete first two weeks."

related:

• "the-first-impression"
• "setting-vs-managing-expectations"
• "consistent-communication-cadence"
• "understanding-client-business-context"

---

The kickoff meeting: the hour that shapes the whole project

We once ran a kickoff that everyone agreed went great. Good energy, lots of nodding, the client said "this is exciting" at least three times. Six weeks later the project was a mess. Two stakeholders were giving us contradictory feedback, nobody could tell us who had final approval on designs, and the client's definition of "phase one" turned out to be about twice the size of ours.

Every one of those problems was answerable in the kickoff. We just didn't ask. We spent the hour building excitement when we should have spent it building clarity.

Why this meeting is different from every other meeting

The kickoff is the only meeting where you can ask basic questions without it being weird. "Who makes the final call on this?" is a completely normal question in week one. In week six, the same question means something has already gone wrong.

It's also the moment when the project is most flexible. Nothing has been built, no feedback has been given, no expectations have hardened. Every ambiguity you resolve in the kickoff is a conflict you never have to have. Every ambiguity you leave alone is sitting there waiting for you, and it will surface at the worst possible time, usually attached to a deadline.

And the client is paying closer attention in this meeting than they will in almost any other. They just signed a contract. They're watching for evidence that they made a good decision. How you run this hour tells them how you'll run the next six months.

How I think about this

The kickoff is a working meeting, not a ceremony. A lot of teams treat kickoff as a ribbon-cutting: introductions, a walkthrough of the SOW, some enthusiasm, done. That's a wasted hour. The goal is to leave with answers you didn't have walking in. If nothing surprising came up, you didn't dig enough.

Get the decision map before anything else. Who gives feedback, who approves, and who just needs to be informed? These are three different groups, and clients often haven't thought about the difference until you ask. The single most expensive thing to discover mid-project is that the person you've been pleasing isn't the person who decides.

Ask what success looks like in their words. The SOW says what you're building. It usually doesn't say why. "If this project goes perfectly, what's different for you six months from now?" gets you the real goal, and the real goal is what you'll need when you're making judgment calls later. Sometimes the answer surprises you. I've had a client answer that question with "honestly, I just need my CEO to stop asking about this," which told me more about how to run the project than the entire SOW did.

Surface the history. Ask what they've tried before and what happened. If a previous agency burned them, you want to know how, because you're inheriting that scar tissue whether they mention it or not. "Is there anything from past projects like this that you want us to do differently?" is a gentle way in, and the answers are almost always useful.

Agree on logistics like they matter, because they do. Update cadence, meeting rhythm, response-time expectations, where files live, how feedback gets delivered. This feels like the boring part of the meeting. It's also where most of the friction in a project actually comes from. Five minutes of explicit agreement here saves you months of low-grade annoyance.

End with the first two weeks, specifically. Excitement without a concrete next step decays fast. Before anyone leaves the meeting, everyone should know exactly what happens between now and the next time you talk.

What this looks like

Opening the meeting

After introductions:

"Here's how I'd like to use this hour. I have the SOW, so I don't want to spend our time re-reading it. What I'd rather do is make sure we understand your goals in your words, figure out how decisions will get made, and agree on how we'll work together day to day. Then we'll walk out of here with the first two weeks mapped. Sound good?"

Getting the decision map

"I want to make sure feedback flows smoothly, so let me ask a slightly blunt question. When we deliver the first designs, who reviews them? And of those people, who has final approval? I ask because on past projects we've had situations where we got great feedback from one person, made changes, and then someone new appeared in week five with different opinions. I'd love to avoid that here."

[Client pauses] "That's a good question. Sarah and I will review, but honestly our COO will want to see anything customer-facing."

"Perfect, that's exactly what I needed to know. Would it make sense to get the COO's eyes on the design direction early, before we've built too much on top of it?"

Asking about the past

"One more question before we get into logistics. Have you worked with an outside team on something like this before? Anything you'd want us to do differently?"

"Our last agency was fine, but we never knew what they were working on. We'd go two weeks without hearing anything."

"That's really useful. Then let's overcorrect: you'll get an update from me every Friday, even if the update is just 'everything's on track.' If a Friday ever passes without one, call me out on it."

Closing with the first two weeks

"Here's what happens next. By Wednesday you'll have a project brief summarizing everything from today, so you can check whether we heard you right. Next week we start discovery interviews, and I'll need about 45 minutes each from Sarah and two people on the support team. Can you help me get those scheduled? Then we're back together two weeks from today to review what we've learned."

What goes wrong in kickoffs

The SOW read-along. Someone shares their screen and walks through a document everyone has already read. Twenty minutes disappear and nobody has learned anything.

Only asking questions you know the answers to. If every question in your kickoff is a softball, you're performing curiosity instead of practicing it. The valuable questions are the ones where the answer might be inconvenient.

Letting enthusiasm stand in for alignment. "Everyone seemed excited" is not a kickoff outcome. Excitement and shared understanding feel identical in the room and behave completely differently afterward.

Skipping the awkward questions because the mood is good. Asking about decision authority or budget approval can feel like breaking the honeymoon vibe. But these questions are never easier than they are right now. Awkward in week one beats painful in week six.

No written follow-up. If the kickoff produces decisions and nobody writes them down, you didn't produce decisions. You produced memories, and memories diverge.

Getting better at this

Build a kickoff question bank. Keep a running list of the questions that would have saved you pain on past projects. Mine includes "who has final approval," "what's been tried before," "what does your boss care about here," and "what would make this a failure even if we deliver everything in the SOW." That last one gets interesting answers.

Send the agenda a day ahead. Not a formal document, just a short email: "Here's what I want to cover tomorrow, let me know if there's anything you'd add." Clients often reply with the thing they were nervous to bring up live.

Write the recap within 24 hours. Everything decided, everything open, and who owes what by when. This document becomes the reference point when memories diverge later, and they will.

Audit your last kickoff against your last project problem. Take the most painful surprise from a recent project and ask: could a kickoff question have caught this? Usually the answer is yes. Add the question to the bank.

How this connects

The kickoff is where first impressions become project habits. It's where you set expectations instead of managing them later, where communication cadence gets established, and where you learn enough about the client's world to speak to their business context for the rest of the engagement. Run it well and every other conversation in this collection gets easier.

Things to try

• Before your next kickoff, write down the three most expensive surprises from your last project. Design one question for each.
• Ask "who has final approval?" in your next kickoff and don't move on until you get a name.
• End your next kickoff by scheduling the next meeting before anyone leaves the room.
• Send a kickoff recap within 24 hours that separates decisions made from questions still open.
• Ask a new client what their last vendor should have done differently. Then do that thing, visibly.

The best compliment I've gotten after a kickoff wasn't "great meeting." It was a client who said, "You asked us things we hadn't thought about yet." That's the job. Anyone can host a pleasant hour. The kickoff is your one chance to find the problems while they're still cheap.

Template: Kickoff Working-Meeting Agenda

Use this when: you're running a project kickoff and want it to produce clarity and decisions instead of just good feelings.

Channel: Meeting agenda

```template

Kickoff: [CLIENT / PROJECT]

Length: 60 minutes

Goal: leave with the decision map, a shared definition of success, agreed logistics, and the first two weeks mapped.

1. Intros and how we'll use the hour (0:00-0:05)

"I've read the SOW, so I don't want to re-read it. I'd rather understand your goals in your words, figure out how decisions get made, and agree on how we'll work day to day."

1. Success in their words (0:05-0:20)

• If this goes perfectly, what's different for you six months from now?
• What would make this a failure even if we delivered everything in the SOW?

1. The decision map (0:20-0:35)

• When we deliver the first work, who reviews it? Of those, who has final approval?
• Who just needs to be kept informed?

1. History (0:35-0:45)

• Have you done something like this with an outside team before? Anything you'd want us to do differently?

1. Logistics (0:45-0:55)

• Update cadence, meeting rhythm, response-time expectations, where files live, how feedback gets delivered.

1. The first two weeks (0:55-1:00)

• Concrete deliverable, concrete date, what we need from you, and the next meeting on the calendar before anyone leaves.

Follow-up: written recap within 24 hours separating decisions made from questions still open.

```

Template: Kickoff Decision-Map Question

Use this when: you're live in a kickoff and need to find out who actually approves the work without it feeling like an interrogation.

Channel: Call script

```template

"I want to make sure feedback flows smoothly, so let me ask a slightly blunt question. When we deliver the first [DESIGNS / DRAFTS / BUILD], who reviews it? And of those people, who has final approval?

I ask because on past projects we've had situations where we got great feedback from one person, made changes, and then someone new appeared in week five with different opinions. I'd love to avoid that here."

(Pause — let them work it out. The answer is often "I hadn't thought about that.")

[If a new decision-maker surfaces:]

"Perfect, that's exactly what I needed to know. Would it make sense to get [THAT PERSON]'s eyes on the direction early, before we've built too much on top of it?"

```