Grace runs 2 kickoff meetings. The internal one creates alignment. The external one creates confidence. You own both, and the whole sequence around them.
Readiness is one sentence. If you can’t finish “This project succeeds when ______” in a way your client would agree with, the project is ready for one more conversation.
A kickoff is measured by what your client believes on the way out of the room. Every agenda item should trace back to one of the 3 beliefs.
The kickoff sequence. Most of the leadership work is finished before your client sits down. Prepare produces internal clarity, the internal kickoff produces one story, the external kickoff produces the 3 beliefs, and the close is what makes any of it survive the week.
What to do
Seven moves. These are the ones that decide whether the hour holds.
What to do
Write the success sentence before you book either meeting. Answer it from 3 angles, the client’s, Grace’s and the team’s, then write the client facing version in one line.
Send the draft agenda 3 business days out and ask one question. What needs to be added to this agenda for your discipline to leave ready to execute?
Write agenda lines that name a decision and an owner. Confirm what is included, what is excluded, and who owns the work at every boundary.
Build 2 attendee lists and hold every name to a test. One for the internal room, one for the external room. Leaving somebody off is a decision.
Design at least one Experience Point from a sentence your client said, and put it on the agenda before anything else goes on it.
Assign every external kickoff role before the internal meeting ends. Opener, topic leads, technical answers, note taker, closer. Name a role for yourself too.
Send the written recap within 24 hours. Decisions, actions, owners, due dates and unresolved items, to everyone who needs it, including the people who couldn’t attend.
What to watch out for
Seven signals. Each one is visible in the room, and each one costs you later.
What to watch out for
A deliverable owned by a discipline instead of a person. Disciplines don’t answer emails or make decisions.
An agenda line that names a topic and no decision. Rewrite it before you distribute it.
A subconsultant seeing their part of the story for the first time in front of the client.
A warm room, and a client who can’t state their own top priority afterward. Belief 2 didn’t land.
A team member who hesitates on an assumption. Find out what they’re seeing. It’s usually the risk everyone else missed.
The change conversation pushed to later because the meeting is running long. Later is when it costs money.
Decisions living in memory at the end of the day. The Decision Log gets updated today, while the room still remembers it the same way.
What to avoid
What to avoid
Opening with “here is what we need from you today.” It sounds indifferent to your client’s priorities.
Opening with “what would you like to talk about today?” It sounds unprepared.
Negotiating the communication cadence in the room. Module 6 set it. Bring it and confirm it.
Becoming the only person talking. If that happens, the meeting has already failed.
Speculating in front of the client. Commit to when you will answer instead.
Committing scope, schedule or fee before the impact is understood.
Calling a courtesy an Experience Point. If your client can’t explain why the moment mattered, it was hospitality.
Build the agenda on a clock
A complete agenda is never only your draft. Put a clock on the cycle and protect the order.
The 3, 2, 1 agenda clock. 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.
Draft. Solicit. Refine. Assign. Distribute.
A kickoff aligns 5 things. Success. Scope. Roles. Risks and assumptions. Communication rhythm. Write each one as a decision the room can make.
Instead of
Write
The test
Scope
Confirm what is included, what is excluded, and who owns the work at every boundary.
Is “extra” recognizable later?
Schedule
Confirm phase milestones, decision dates, and who owns each required input.
Does every date have a name on it?
Communication plan
Publish the one page communication plan and confirm the client decide by dates on it.
Did the client agree to the dates?
Change process
Confirm how a change gets raised, evaluated and resolved, before any work proceeds on it.
Did the client choose how options come to them?
Roles
Name who leads each discipline and who holds decision authority on each side.
Can both sides name the other’s decision maker?
Who belongs in each room
Not everyone assigned to the project belongs at either kickoff. Build both lists alongside the agenda.
Meeting
Invite the people who
Internal kickoff
Hold work, decisions, interfaces or assumptions that need to align before the client is in the room.
External kickoff
Establish the client relationship, explain a material part of the work, contribute to an important decision, or demonstrate the team’s capability.
Design your Experience Points
A designed moment that visibly serves something your client actually said. All 3 properties have to be true.
1 · It traces to a client sentence, in their own words, captured in Discovery.
2 · It sits on the agenda before the meeting begins, so it survives a meeting that runs long.
3 · It can be seen. Your client can describe it to somebody who wasn’t there.
Worked example. Karen Whitfield said she is never surprised in front of City Council. Three Experience Points come straight out of that one sentence.
Put the Council calendar on the plan
Every Grace update lands at least 5 working days before a Council date. She can see the runway.
Open the risk register in the room
Name the live risks out loud, so the first time she hears one is never in a public session.
Show the dispatch decision dates
Decide by and request by, both visible. It’s the one decision she has to defend publicly.
Then test it
Ask whether she could explain why the moment mattered. If not, you designed a courtesy.
What a kickoff leaves behind
Three beliefs, 3 moves. Belief is the deliverable of a kickoff, and each belief comes from one specific move. When a belief is missing, look at the move that produced it.
Ground rules, said out loud before the client arrives
The last thing the internal kickoff does. Say them, don’t assume them.
The ground rules
We speak from one agreed project position.
We do not speculate.
If we do not know, we commit to when we will answer.
We do not commit scope, schedule, or fee until the impact is understood.
Technical questions go to the person closest to the work.
Anything that could change the plan gets surfaced to me before anyone commits to it.
The 24 hour close
Kickoffs rarely fail in the room. They fail afterward, when everyone remembers the meeting slightly differently.
Today, before you leave
Update the project’s Decision Log with what the team decided, while the room still remembers it the same way.
Within 24 hours
Send a written recap. Decisions, actions, owners, due dates and unresolved items.
Who gets it
Everyone who needs it, including the people who couldn’t attend. They are the ones who drift first.
What’s primary
Decisions and commitments. Discussion summaries are secondary.
Prepare it. Staff it. Assign it. Lead it. Close it. Document it.
PM Excellence Academy