Project Kickoff

Ten minutes to nine

You have the scope, the budget, the schedule, the staffing plan, and the communication plan. Module 5 built most of it. Module 6 built the rest.

You know those things well. Your team may not. Your consultants may not. Your client certainly does not. That gap is what a kickoff closes.

Kickoff is an undervalued step in the project process. It is the first time the team formally introduces itself to the client, and it is the first time the client can evaluate the decision to hire you.

Grace runs 2 kickoff meetings because they do 2 different jobs. The internal kickoff creates alignment. The external kickoff creates confidence. You own both meetings, and you own the whole sequence around them.

What you'll be able to do

• ✓Write the project's definition of success in one sentence your client would agree with.
• ✓Build a kickoff agenda that produces decisions, and staff each room on purpose.
• ✓Design an Experience Point that traces to something your client said.
• ✓Lead the internal and the external kickoff, then close both of them inside 24 hours.

Your client came for confidence

A typical kickoff spends the hour walking the proposal, the schedule, and the org chart. Everything said is accurate, and it's all information the client already holds.

The proposal explains the work. The schedule explains the timing. Your client read both before the meeting started.

A kickoff earns its hour by answering the questions those documents can't. Your client arrives with 3 of them.

Running a great kickoff takes 2 decisions from you. First, decide what the client needs to believe about your team when the meeting ends. Then design the meeting to produce the evidence for those beliefs.

Confidence gets built before your client sits down. A team that hasn't agreed with itself will perform its own disagreement in front of the client, at the exact moment the client is deciding who to trust. That's why the internal kickoff comes first.

Get the project ready first

Nothing goes on a calendar until the project is ready. Readiness means you know what success looks like before anyone walks into the room. It comes out of the Discovery work in Module 4, where you defined the client's success criteria and their experience expectations.

Write success in one sentence

Ask one core question. What must be true at the end of this project for everyone to feel it was successful? Answer it from 3 angles. The client's. Grace's. And the project team's.

Then write the client facing version as a single sentence.

If you can't finish that sentence in a way the client would agree with, the project is ready for one more conversation.

On Oakhaven, Karen Whitfield named her targets in discovery. The facility gets delivered as designed, dispatch never goes dark, and she is never surprised in front of City Council. That's a definition of success for the outcome, for performance, and for experience, in the words she used.

Build an agenda that produces decisions

A kickoff aligns 5 things. Success. Scope. Roles. Risks and assumptions. Communication rhythm.

Most meeting agendas answer one question. What are we going to talk about? A stronger agenda answers 4.

1. Why are we talking about it?
2. What decision do we need to make?
3. Who needs to make it?
4. What should be true before we move to the next topic?

That changes what a line on the agenda looks like.

That third row matters. You are bringing a cadence, and Module 6 already set it. Bringing a plan is different from asking a room what it wants.

A complete agenda is never only your draft. Send it to the key team members and subconsultants who will be in the room, and ask them one specific question. What needs to be added to this agenda for your discipline to leave ready to execute?

Put a clock on that cycle. Send the draft at least 3 business days before the kickoff. Ask for additions back 2 business days before. Then refine the draft, assign an owner to each item, and distribute the final agenda to every attendee one business day before the meeting.

A compressed timeline can compress the days, and it should protect that order. Their answers are input. You still decide what belongs on the final agenda, because left unmanaged the draft becomes a collection of everyone's topics.

Decide who is in each room

Not everyone assigned to the project belongs at either kickoff. Build the 2 attendee lists alongside the agenda, and hold every name to a test.

Leaving somebody off a list is a decision, the same way including somebody is.

Design your Experience Points

Module 1 tied client value to performance and experience. You have planned the performance. Kickoff is your first chance to plan the experience.

An Experience Point is a designed moment in the kickoff that visibly serves something the client actually said. It carries 3 properties.

1. It traces to a client sentence. Something they said, in their own words, captured during Discovery.
2. It sits on the agenda before the meeting begins. Planning it is what makes it survive a meeting that runs long.
3. It can be seen. The client watches it happen and can describe it to somebody who wasn't there.

Here is the simplest test. The client should be able to explain why the moment mattered. If they can't, it was hospitality.

Karen Whitfield said she is never surprised in front of City Council. So put the Council meeting calendar on the communication plan, and schedule every Grace update to land at least 5 working days before a Council date. She can see that, and she can explain why it matters.

Run the two meetings

On Oakhaven both meetings ran on the morning of August 10. The internal kickoff went first at 90 minutes, and the external kickoff followed straight after at 2 hours. Long meetings, and productive ones when they are planned well and run efficiently.

The internal kickoff, in 6 moves

1. Open on purpose. Read the success statement exactly as you wrote it, then leave it on the screen. When the discussion drifts, point back to it and ask whether this moves us closer to that outcome or farther away.
2. Name an owner for every deliverable. Walk the deliverables one at a time and ask who owns this. If the answer is a discipline, keep going, because disciplines don't answer emails or make decisions. Ask for a name, then ask whether they're comfortable owning it.
3. State the boundary. Say what's included and what isn't, and name the work that belongs to the Owner and the work that belongs to consultants. Your client hears these same boundaries in an hour, and this room agrees on them first.
4. Test the assumptions. Take the few risks likeliest to change cost, schedule, or quality, and ask what changes if this assumption is wrong. Scope? Schedule? Fee? Resolve what the team can resolve now. For the rest, capture the assumption, assign an owner, and set a date to revisit it.
5. Assign the external kickoff roles. Who opens, who leads each topic, who presents the technical content, who answers discipline questions, who listens, who captures decisions as they happen, and who closes. Name a role for yourself too. If you become the only person talking, the meeting has already failed.
6. Agree the ground rules out loud. Say them in the room before anyone walks into the next one.

One question ends the internal kickoff. If Karen walked in right now, would everyone at this table describe this project the same way? Keep working until your client would hear one story.

The external kickoff, in 6 moves

1. Start with the person. Remind your client what you heard mattered most, and show how it shaped the plan. Opening with what we need from you today sounds indifferent. Opening with what would you like to talk about sounds unprepared.
2. Ask what changed. Has anything changed since we last met? If something has, understand it first and name who owns figuring out what to do about it. Commit to evaluating the impact before you respond.
3. Show how the project will be run. Open the communication plan, this time for the client. Show where the decisions and the design reviews land, then ask her directly. Will this give you what you need, early enough to act on it?
4. Confirm the boundary and open the change conversation. Slow down here. Most kickoffs rush it, and it is far easier to have this conversation now, while nothing is at stake.
5. Deliver the Experience Point you designed. On Oakhaven, that's the Council calendar sitting on the communication plan with every Grace update landing before a Council date. Hard to fake and easy to remember.
6. Close it. Summarize the decisions and the near term priorities. Name the next milestone, the next decision your client owns, and what's still unresolved with the name of whoever closes it. Set the date of the next meeting.

That last question does real work. It puts your client inside the problem solving conversation with you, which is where she belongs. It's her project.

Close it the same day

Kickoffs rarely fail in the room. They fail afterward, when everyone remembers the meeting slightly differently and drift gets room to grow.

Update the project's Decision Log before the day ends, while the room still remembers it the same way. Then send a written recap within 24 hours to everyone who needs it, including the people who couldn't attend. Decisions, actions, owners, due dates, and unresolved items. Discussion summaries are secondary.

Put it to work