Kickoff Is Where the Project Is Assigned

The kickoff and the two plans behind it

Module 5 built the seven step plan that bounds the work, prices it, sequences it, and staffs it. Module 6 built the six step communication plan that says when the project talks, to whom, and by when a decision has to be requested. Module 7 is the hour in which both plans are announced out loud and leadership of the project is assigned.

Almost nothing presented at a kickoff is invented in the room, since the scope boundary, the work breakdown, the labor budget, the schedule, the decide by dates, and the one page communication plan all exist before anyone sits down, in the form the two planning modules produced them. The work of this module is deciding what leaves the room with the client, in what order, and in whose voice.

The first three moves are made in private, and the fourth is made in front of the client.

What does a kickoff actually decide?

A kickoff is treated as the meeting where the project is explained. It is in fact the meeting where leadership of the project is assigned, and it gets assigned whether or not the project manager claims it. Somebody leaves that room as the person the project runs through, and the room settles that question early, on evidence, without ever taking a vote.

The assignment follows command of the work, and a project manager who presents information hands it somewhere else. It goes usually to the principal who led the pursuit, sometimes to the contractor, occasionally to nobody at all. Every later decision then routes around the project manager. Every later correction then costs a conversation that one well run hour would have made unnecessary.

Consider Oakhaven. Marcus Webb led the pursuit and is the name the City already trusts, and Dana Reyes, the project manager of record, has never met the client. If Dana opens the hour with a schedule that Marcus then explains, the City will route the next ninety days through Marcus, politely and permanently. Nobody will have decided that out loud.

A kickoff does not explain the project. It assigns the project.

Is the project ready to start?

Initiation is not a question of speed but a question of readiness. Most project pain traces not to a shortage of effort but to work that started before the expectations governing it were clear. The single best test of readiness is whether a project manager can write the project’s success in one sentence.

One sentence is a hard instrument, and it forces the client’s three success targets into a single ranked statement. It forces the tradeoff between them into the open, and it forces a project manager to write what the client would sign rather than what the team would prefer to deliver.

Consider Oakhaven. Karen Whitfield named three targets in discovery: the facility delivered as designed while emergency dispatch never goes dark, no surprise in front of City Council, and the $1.4M Grace fee delivered at the planned 20 percent profit. Those three compress into one sentence.

Readiness does not require every answer, only that the unknowns are named and that one person owns closing each of them. The Accountable Owner will spend a day at the readiness gate rather than a month unwinding a misunderstanding in the middle of Design Development.

How does a project manager present a plan rather than a project?

Presenting the project means describing what the building will be, who sits on the team, and roughly when the phases happen, and everybody in the room can do that. Presenting the plan means putting on the table the instrument that governs the next ninety days. It is built to a resolution nobody in the room has seen, and that resolution is the move that assigns leadership.

The material already exists, since the seven step plan built in Module 5 produced a scope boundary, a work breakdown, a labor budget, a schedule, a staffed plan, and an Earned Value Plan. The six step communication plan built in Module 6 produced coordination milestones, decide by dates, request by dates, and one page naming an owner and a written output for every scheduled conversation.

Consider what a project manager physically puts on the Oakhaven table. The work breakdown carries 9 deliverables and 14 work packages sorted down from 19 candidates, and it tells a client the boundary of Design Development was decided rather than assumed. The schedule, built at Step 5 of Module 5, carries the Week 13 submission as contractual and carries protected QAQC weeks the team has agreed not to spend, and it tells a client that quality on this phase is scheduled rather than hoped for. The one page communication plan, published at Step 6 of Module 6, carries the client decision calendar, and it tells a client exactly when the City will be asked to choose and how long the City will have to answer.

None of that is a report, since a project manager reading those three artifacts aloud is demonstrating command of work the room has never seen, and command is the evidence a room uses to assign leadership.

Present the project and the room learns what the building will be. Present the plan and the room learns who the project runs through.

How does a client come to feel heard?

The mechanism is not warmth, and warmth is easy to manufacture, easy to return, and easy to mistake for alignment. The People Pleaser’s blind spot is reading a pleasant room as proof that the substance landed. A client comes to feel heard when the team says the client’s own words back, in the client’s own language, and then shows the plan that was built around them.

The move runs in three plays, and the order of the plays is the method.

1. Play it back. State the client’s definition of success in the client’s words, attributed to the person who said them, before presenting anything the team produced.
2. Show the plan built on it. Point at the element of the plan that exists because of that sentence, and name the sentence.
3. Ask what is missing. Then stop talking, and write down whatever comes back.

The third play is the one that gets skipped, because the first two feel like a finish and because the room is warm by then. It is also skipped because a project manager who has just presented well is reluctant to invite a correction. It is the only one of the three that produces the belief, since a client who has been asked and answered can watch the answer change something.

Consider the Oakhaven opening, and the order in which the room hears things. A project manager does not open by walking the room through an agenda. A project manager opens by reading Karen Whitfield’s three targets back to Karen Whitfield, attributed to the conversation in which she set them, then turns to the protected QAQC weeks and says plainly that those weeks exist because dispatch cannot go dark. Then comes the third play.

What is an Experience Point?

Module 1 locked the value equation, and the equation multiplies rather than adds, so a project delivered flawlessly and experienced badly does not return a partial result. Module 4 discovered the client’s own definition of both halves, and Module 5 planned against Performance and Financial. Nothing in the course so far has told a project manager how to deliver Experience on purpose, in the room, in a single hour.

An Experience Point is a designed moment in the kickoff that visibly serves the client’s stated Experience criterion, a specific planned observable move the client could point to afterwards. It is not a courtesy, it is not a tone, and it is not a well run meeting.

Consider Karen Whitfield’s Experience criterion on Oakhaven, that she is never surprised in front of City Council. Three Experience Points follow directly from that one sentence, and each of them traces back to it.

• 1The communication plan is presented with the Council meeting calendar already on it, and every Grace update is scheduled to land at least five working days before a Council date.
• 2The risk register is opened in the room rather than held back, with the three live risks named out loud, so the first time Karen hears a risk is never in a public session.
• 3The dispatch system selection, the one decision Karen will have to defend publicly, is scheduled with its decide by date and its request by date visible, so she can see the runway she has.

Every one of the three traces to a sentence Karen said, and that traceability is the test. A team that cannot name the sentence behind a moment has designed a courtesy.

Performance is delivered over months. Experience is delivered in moments, and the first moments are at kickoff.

What must a kickoff align, and what must it leave behind?

A kickoff aligns five things out loud, in the room, with everybody present who will be held to them. The job is to make the implicit explicit while it is still cheap, because every one of the five costs a conversation now and costs a change order later.

• 1Success. Confirm the purpose and how success will be judged. What outcome matters most? What wins if priorities collide?
• 2Scope. State the boundary of what the team will deliver and what it will not, so “extra” is recognizable later.
• 3Roles. Name who does what, who leads each discipline, and who holds decision authority on each side.
• 4Risks and assumptions. Put the early risks and the assumptions behind the fee on the table, when they are still cheap to manage.
• 5Communication rhythm. Set the cadence of meetings and updates, and how decisions will be recorded and confirmed.

The five are what a kickoff aligns, and they are not what it leaves behind. A kickoff is not measured by whether the meeting felt good, and it is not measured by attendance. It is measured by what the client and the team believe on the way out of the room. Belief is the deliverable.

Three beliefs stated as a checklist are three things to hope for. The mapping below turns them into a method, because each belief is produced by one specific move, and none of the three is produced by warmth.

How does alignment survive the meeting?

A kickoff runs in three stages, and each stage produces something the next stage requires. Prepare produces internal clarity. Execute produces shared alignment. Follow through produces execution, the only one of the three a project is actually paid for.

The most common failure is skipping the first stage, and a team that has not aligned internally cannot align a client. What such a team does instead is perform its own disagreement in front of the client, at the exact moment the client is deciding whom to trust. The Kickoff Brief is the artifact that proves preparation happened, and preparation is what makes that performance impossible.

Thirteen things get confirmed before anyone walks into the room, and they answer two questions rather than thirteen.

Follow through is the shortest stage and the one that decides whether the hour holds. Decisions and open items are documented and sent inside 24 hours, the communication rhythm is scheduled rather than promised, and the assumptions named in the room are written where the team can still find them in week nine. A kickoff that is never sent is remembered differently by every person who attended it.

There is one output of a kickoff that does not fit anywhere on a checklist. The best kickoffs leave a team that wants to do the work together rather than a team that merely knows its tasks. Camaraderie is the reserve a project spends in the weeks Module 8 and everything after it will bring.

Summary

This lesson followed one hour on the Oakhaven Public Safety Campus, from a room filling at ten minutes to nine to the documented decisions that left it inside a day. Inside it came the readiness sentence, the plan a project manager put on the table, and three Experience Points designed from three sentences Karen Whitfield said. The same hour runs on every project Grace delivers, and the artifacts on the table change with the client and the phase.

The Module 7 Quick Reference documents the three stages, the five alignments, and the three beliefs. The Kickoff Readiness Board lets a project manager test a kickoff before running it, item by item, against what the plan can support, and then rehearse the first ninety seconds of it out loud on a live project.

In Module 8 the work starts, and the alignment reached inside this hour becomes the baseline execution is measured against.

On your next kickoff

1. Write the one sentence success statement for your next kickoff, then test whether your client would sign it without editing a word.
2. List the artifacts you will physically put on the table, and remove every item that describes the project rather than governing it.
3. Design two Experience Points from something your client actually said, and put both on the agenda before anything else goes on it.
4. Book the 24 hour send in your own calendar now, and name the person who writes it.

The Kickoff Readiness Board tests a kickoff before it is run, and the Quick Reference carries the three stages, the five alignments, and the three beliefs.