Engagement Kickoff Checklist

The argument in week six is almost never about what was in scope. Read the thread afterward and it is usually about time: the work took longer, the date did not move, and nobody can agree on why.

Week zero is where you make that argument unnecessary, and most of what does the work there has nothing to do with scope.

Why this exists

The thing that quietly eats an engagement is latency. You wait eleven days for a network account. You wait a week for the data extract because the person who pulls it is on leave. You wait four days for a decision that takes ten minutes to make. None of that is anybody’s fault, and all of it comes out of your delivery time unless you agreed in advance that it would not.

So the most valuable line in a kickoff is not a scope statement. It is the slip rule, written down before anyone needs it: each business day blocked on access, data or a decision moves the end date by one business day, and blocked days get logged on the day they happen rather than reconstructed later from memory. Agreed in week zero, that sentence is administrative. Raised in week six, the same sentence is a complaint.

The second line that earns its place is a question no standard kickoff agenda contains: who is worse off if this succeeds? Every process change has someone whose work becomes visible, whose judgment gets encoded into a rule, or whose Thursday afternoon task disappears. If nobody in the room can name that person, you do not yet understand the process well enough to change it — and they will arrive later, described as unexpected resistance.

How to use it

Submit every access request in week zero, including the ones you will not need for two weeks. Access queues run on their own clock, not yours. The request that costs you an afternoon of attention can cost three weeks of somebody else’s process, and a properly scoped engagement finishes late because of this more often than because of anything technical. Record a ticket number for every one, so that “we asked” is a fact rather than a memory.

Write the table of contents of the final deliverable during the kickoff, and send it the same day. One page, numbered sections, no prose. You want the argument about it now, when changing it costs an email, rather than in the final week when it costs the final week. The reaction also tells you something a scope discussion will not: the section they ask about first is the one they actually care about, whatever the statement of work says.

Book the last meeting in week zero, on real calendars. Meetings that are not booked become emails, and an engagement that ends in an email tends not to end at all. It fades out, with a tail of small requests nobody priced.

Then hold the gate. No billable work starts until the decider is named and has agreed to a response time, the slip rule is written down, every access request carries a ticket number, and the last meeting exists on a calendar.

Where it goes wrong

This is too much ceremony for short work. Under about three weeks, run the people section and the time section, throw the rest away, and accept the exposure — the overhead would otherwise be a visible share of the engagement, and the client is paying for it.

It also cannot rescue a vague proposal. If you find yourself discovering scope during the kickoff, if the conversation keeps turning into design, stop the meeting. The honest move is to convert the next two weeks into a priced discovery and rewrite the engagement around what you find, rather than running a checklist over a hole.

And none of it substitutes for a sponsor. A checklist makes a well-sponsored engagement run cleanly. It cannot manufacture authority that does not exist, and the signs that it does not exist are all visible in week zero to anybody willing to read them.