Kick-off 🏈

You walk into this stage with a contract and a vague vision. You walk out with a project. Specifically: a Sponsor who has publicly committed, a Guardian who has accepted the role, a Change Leaders group that knows what's expected of them, a baseline survey filled in, and a meeting cadence locked into calendars four weeks ahead. You are the one who installs that change of state — by how you run the next two meetings.

---

In this document

What happens at this stage

Part 1 — With the Sponsor and Guardian

Part 2 — With the Change Leaders

How to actually run a kick-off — the facilitator's mindset

The seven elements every change management framework needs — or breaks without

Where teams stall

What to prepare before this stage

What you get with the full protocol

---

1️⃣ What happens at this stage

Kick-off is one stage with two distinct meetings, run roughly a week apart. They're not interchangeable, and the order is non-negotiable.

🎯 Meeting 1 — With the Sponsor and Guardian. Operational. Frames the project, locks in commitments, names risks, agrees on roles. This is where the Sponsor's "I'm in" goes from a verbal nod to a publicly visible posture, and where the Guardian's job description becomes specific enough that they can do it.

🎯 Meeting 2 — With the Change Leaders. A week later, with the team-leads and process-owners who'll carry the change into their teams. This meeting is run on top of the alignment from Meeting 1 — so if Meeting 1 was vague, Meeting 2 inherits the vagueness and amplifies it.

Note on naming (Sponsor, Guardian) — click to reveal

Sponsor and Guardian are roles formally appointed in the Reliability Protocol.

The Sponsor is the executive whose authority makes the project real — CEO in <40-person companies; a Department Director or HR exec above that.

The Guardian is the operator with enough authority, influence, and time to drive change across functions and resolve conflicts. Often the same person in smaller orgs, almost never in larger ones.

---

2️⃣ Part 1 — Meeting with the Sponsor and Guardian

This meeting is operational-focused: it sets the frames for how the project will run.

The non-negotiables to walk out with:

• Goals and metrics agreed. The "Why this platform" statement from discovery, sanity-checked against the Sponsor's current view. If they hesitate on it now, hesitation in week 8 is guaranteed.
• Timeline visualised. Not a Gantt — a single picture showing the four phases (Alignment → Foundation → Adoption → Momentum) and where Sponsor decisions are required.
• Roles assigned. Sponsor, Guardian, Admin IT — and a placeholder for the Change Leaders group that gets filled in over the next week.
• Tools agreed. Where do the project board, files, and communication live? Decide once, here. Re-deciding in week 4 wastes a week.
• Risk and change-management approach. Walk through one realistic scenario together: what if a Change Leader leaves, what if priorities shift, what if the launch slips? Don't theorise — test the joint response.
• The Partnership Contract, made explicit. Speed (3-day feedback turnaround), disclosure (a week's heads-up on hires, restructures, product launches, leadership changes), survey discipline (Guardian chases completion above 80%), meeting cadence (booked four weeks out), Sponsor presence (at kickoff, implementation plan, launch, post-transformation review). This conversation is the one most teams skip — and the one they re-have, over and over, in the middle of every operational disagreement for the next six months.

The hostage moment

Toward the end of Meeting 1 — after roles are assigned, after the Partnership Contract is on the table — comes the single most useful tactical move of the entire stage. We call it the hostage moment, and it sounds like this:

💬 "Before we finish this meeting, we need a baseline. Go to this link: [paste survey link in chat]. It takes 4 minutes. We don't finish the meeting until we see two responses."

It works for one reason: this is the only moment in the project where you have the Sponsor and Guardian's undivided attention, with social pressure on. After this meeting, the Sponsor will return to their day, and the survey link will sit in their inbox for two weeks before someone gives up chasing.

The hostage moment is how you go from "we'll send a baseline survey" to "we have a baseline survey." Without baseline data captured during this meeting, you cannot prove ROI six months in. When the CFO asks "was this worth it?" you need numbers from before and after. The hostage moment is what makes the "before" exist.

How meetings get scheduled — and why this matters more than it looks

You have 4 real options for how the project's recurring meetings get booked.

Each one trades off differently against your organisation's culture:

1. Guardian books via a self-serve booking system (Calendly, Microsoft Bookings, Asana scheduling, or whatever's already in use internally) with a hard rule that all meetings are scheduled one month in advance, with a deadline on when the booking is done.
2. Coach (or PM) blocks placeholders in everyone's calendars first; the Guardian confirms.
3. Recurring meetings on a fixed day-of-week and time, for the duration of the project.
4. Synchronously, during this kick-off meeting, while the Guardian is in the room.

There's no universally right answer. Self-serve booking suits self-organising teams; placeholders suit organisations where calendars fill fast and the Guardian is too senior to chase; recurring suits stable teams; synchronous suits everyone-too-busy-to-do-it-later. Pick wrong and the speed of the project is permanently capped.

Bringing this to your Sponsor.

💬 "The biggest risk to the project's timeline is not the work — it's our meeting cadence. We need to lock the next month of meetings in the next 48 hours, or we will be setting the slowest pace this project can possibly run at."

---

3️⃣ Part 2 — Meeting with the Change Leaders

A week later, with the team leads and process owners who'll do the operational work of the transformation. This is the first contact most of them will have with the project.

Your goal in this meeting is clarity on three things: their role in this project, the rough timeline of what's coming, and why the change is happening now. By the end, each one of them should know — without being told — that they are personally responsible for permanent adoption inside their team, and that the consultants (or you, if running DIY) are there to enable that, not replace it.

💡 What the meeting needs to do:

• Re-present the "Why this platform" statement — but check first: do they recognise the rationale? If they don't, the Sponsor and Guardian have a communication gap to close before the Audit 🔍 stage.
• Walk the timeline at the right altitude. Goals and deliverables per phase, not meeting-by-meeting detail. Overload them now and they'll disengage from week 1.
• Prime them for the role evolution. They start as "Change Leaders." Later — at the Change Alliance 👥 stage — those roles get formally split into the Convention Setter (who sets organisation-wide rules), the Workflow Guardian (per workflow, keeps it current), and the Awareness-builder (per team, keeps the "why" alive). Don't explain all three roles now. Plant the vocabulary.
• Walk the team through how change feels. Most adoption failures are emotional, not technical. We use the Bridges Transition Model — endings, neutral zone, new beginnings — to give Change Leaders a frame for the resistance they'll feel from their teams in weeks 4-8. When you can predict the dip, you don't panic during it.
• Prime for "fast over perfect." The teams that finish transformation are the ones that ship rough drafts of workflows and refine them, not the ones that wait until the workflow is "ready."
• Run the hostage moment again — same script, same baseline survey, peer pressure between Change Leaders this time instead of between Sponsor and Guardian.

---

4️⃣ How to actually run a kick-off — the facilitator's mindset

The agendas above tell you what to cover. The harder question is how — what posture you walk in with, and how each section of the meeting feeds into the next.

The frame we use internally is the rally driver's test lap: the day before the race, the driver and co-pilot walk every corner of the track. On race day, they already know where the hard turns are and how to take them. A good kick-off does the same thing for a transformation. By the end of the meeting, the Sponsor and Guardian should feel as if they've already run the project once and now just have to follow their own footprints in the snow.

That feeling doesn't come from a deck. It comes from the order in which you walk them through the meeting:

1. Introductions — not for the information; for the cadence. The more someone speaks early, the more comfortable they are speaking when something goes wrong later.
2. Project goal — the only part of the project the client owns before the meeting. Anchor here, and the rest of the project becomes "their plan with us inside it" instead of "our plan they nod along to."
3. Plan, from orbit down — wide first ("the whole transformation is three months in two halves"), then a single zoom into the rhythm (weekly meetings, equally spaced), then the key moments (kick-off, mapping, launch, review). Don't drown them in detail in the first pass.
4. Risks — risks make roles necessary. Walked in this order, "what could go wrong" naturally hands off into "who's accountable for preventing it."
5. Roles — assigned to specific people in the room, with two or three concrete behaviours each. Sponsor → carrying urgency. Guardian → pace of execution. Change Leaders → translating the change into their team's language.
6. Next action — one specific thing each person does before the next meeting. The kick-off only succeeds if it ends in motion.

Each step depends on the one before it. Skip introductions and the goal conversation goes shallow. Skip the goal and they'll nod through the plan without engaging with it. Skip the risks and the roles feel arbitrary. The order is the method.

The deeper layer of this — the specific phrasing, the failure modes inside each step, the ways to recover when one of the steps goes sideways — is in the full Kick-Off Facilitator's Playbook, gated below.

---

5️⃣The seven elements every change management framework needs — or breaks without

No transformation survives on enthusiasm alone — it needs a set of structural conditions in place at once, and each one that's missing produces its own predictable failure: no shared vision breeds confusion, missing skills breed anxiety, absent incentives breed resistance, too few resources breed frustration, and no action plan breeds false starts. The seven elements below are that checklist — Kick-off is where the first five get locked in, and the later stages of the Protocol install or reinforce the rest.

---

6️⃣ Where teams stall

‼️ The Sponsor signs and disappears. "Change starts at the top, day one" is one of the few non-negotiables in this work. A Sponsor who approves the budget and then delegates the project until launch is not actually sponsoring it — they're funding it. The wider organisation watches the Sponsor for signal, and the signal in this case reads "this isn't really a priority." Sponsorship that doesn't show up at the kick-off rarely shows up at launch either.

‼️ The hostage moment skipped, baseline never captured. "We'll send the survey out after the meeting" is the politest way to never have baseline data. Two weeks later, completion is at 31%, and you can't prove change because you can't prove the starting point. In our experience, the surveys that capture useful baselines are the ones filled in during the kick-off, in the 4 minutes between role assignment and meeting close.

‼️ Change Leaders chosen for enthusiasm, not influence. It's tempting to nominate the most excited person in each team. Excitement isn't the criterion — influence in their team is. A Change Leader who can't shift behaviour in a single team meeting will not be able to drive adoption when the transformation gets uncomfortable. The Guardian's job at the end of Meeting 1 is to nominate Change Leaders by influence, not by volunteering.

‼️ The Partnership Contract conversation skipped. Sponsor, Guardian, and Operator never explicitly agree on speed, disclosure, survey discipline, and meeting cadence. When week three hits and the Guardian misses two feedback deadlines, there's no shared expectation to anchor the conversation against. Everything becomes a personality conflict instead of a process gap.

‼️ Meetings booked week-to-week instead of four weeks out. The most expensive failure mode of all, because it's invisible. Each individual meeting still happens. The project just runs at half speed, the Sponsor's calendar fills with higher-priority things, and by month three the team has lost momentum without anyone being able to point to why.

---

7️⃣ What to prepare before this stage

• Sponsor and Guardian named, briefed, calendars cleared for both kick-off meetings (see the Preparation 📋 stage if this isn't done)
• A "Why this platform" draft by Sponsor and Guardian together — one sentence on the frustrating problem being removed, one on the goal date
• Project goals and success metrics in a single visible artefact (we use a Miro board; a slide deck or a doc works)
• Baseline survey ready to deploy in both meetings — link in hand, not "we'll figure it out"
• Meeting cadence proposal — which scheduling model fits your culture, with the booking link or calendar block ready to use during the meeting
• List of candidate Change Leaders — by influence, not enthusiasm; team-by-team, with the Guardian's reasoning written down
• The Partnership Contract talking points — speed, disclosure, survey discipline, cadence, Sponsor presence — ready to be discussed, not improvised

---

✅ What you get with the full protocol

The full Reliability Protocol is delivered as a sequence of weekly emails. You don't read 15 stages in one sitting — you receive one stage at a time, with one implementable artifact, and one clear next step you (or your Guardian) can act on at the pace your organisation can sustain. The artifacts you get for this stage:

• The Kick-Off Facilitator's Playbook — the step-by-step facilitation guide for both kick-off meetings, with phrasing, recovery moves, and the timing of the hostage moment.
• The Sponsor & Guardian briefing pack — a 3-page brief you send before Meeting 1 so neither walks in cold.
• The Change Leader nomination scorecard — the rubric for picking by influence, not enthusiasm.
• The Partnership Contract template — the explicit speed/disclosure/cadence/Sponsor-presence agreement, ready to walk through in Meeting 1.
• The baseline survey — the same 4-minute survey we run in the hostage moment, with the questions we found capture the sharpest "before" picture.
• The kick-off agenda template — both meetings, sequenced in the order that makes them land.

💬 Take this with you and your team can run kick-off itself. Hit a wall in either meeting and want a partner — book the session below.

When to bring in a partner

The package above is what we use to run kick-offs ourselves. Most operators can run it themselves once. Bring in a partner when:

• You need the hostage moment to land cold. A neutral facilitator carries social weight you don't — especially if your Sponsor reports above you.
• The Sponsor is sceptical or distant. A partner reframes the meeting from "internal kick-off" to "external diagnostic" and changes who feels accountable in the room.
• You're running kick-off across more than 2-3 teams at once. The complexity of Part 2 (Change Leaders) compounds with team count, and parallel facilitation pays for itself fast.

If any of those land, the diagnostic below is the lightest possible engagement — 60 minutes, no commitment beyond the session.

💡 This is Stage 3 of the Reliability Protocol — Remote Sensei's 15-stage system for permanent organisational transformation, and the global standard for Asana implementation: making Asana and AI stick in mid-size and enterprise teams so work ships on time without anyone chasing it.

➡️ How it works · ➡️ Client results