Preparation 📋

Operational nuances that save the project from slowdowns.

You are the one loading the cannon. The Discovering problems worth solving 🔬 stage has named the problem, the kickoff date is in the calendar — and the temptation now is to exhale and wait for Monday. Don't. The next two weeks are when the Guardian (the manager who will own the transformation day-to-day, formally appointed at the Kick-off 🏈 stage) gets named and briefed, the Sponsor's commitment locks in (the budget-holder who must visibly back the change in public, not just sign), baseline data gets captured, paperwork seals, and the wider organisation hears about what's coming. Skip any one of them and your kickoff starts cold.

In this document

What happens during this stage

A two-week pre-kickoff timeline

The 10-question pre-kickoff brief

The Partnership Contract conversation

Where teams stall

What to prepare before this stage

1️⃣ What happens during this stage

This stage runs two parallel workstreams. Yours is the one that decides whether the project ships — a partner's (if you've hired one) only ever supports yours. Read this in that order.

If you're running this DIY, the consultant-side work doesn't disappear — it falls to you. You become the consultant of record. Walk into the kickoff already knowing your org dynamics, your prior failures, your people, your risks. The brief doesn't write itself.

🎯 On your side: four things have to be in place before the kickoff lands.

Paperwork sealed. Agreement signed, first payment cleared (or scheduled), procurement flagged green. We don't start delivery on a verbal yes — and neither should you.
Guardian named and briefed. Not just an org-chart designation. The Guardian must have read the Partnership Guidelines, understood the role, confirmed they have the time, and started showing up.
Baseline captured. The pre-transformation survey, the participant list, the org structure, the current-state metrics. If you can't measure where you started, you can't prove movement six months in.
Wider organization warned. A short note from the Sponsor to the broader team — what's coming, why, on whose authority. Without this, kickoff happens in a vacuum and the rest of the org learns from rumor.

2️⃣ A two-week pre-kickoff timeline

What happens before the kick-off

Roughly speaking, the 10-14 days between sign-off and kickoff break into three blocks.

Days 1-3 — Lock-down. Paperwork and payment closed off — if you've hired a partner, the first invoice is paid or scheduled; if you're running DIY, the budget is formally allocated and tracked. Sponsor confirms the kickoff date and clears their calendar for it. The Guardian is named in writing and accepts the role. Nothing else moves until this is done.

Days 4-7 — Brief and prep. Partnership Guidelines circulated to Sponsor and Guardian for reading. Project participant list compiled (names, emails, roles, team sizes). Org structure documented. Baseline survey drafted. Prior tool history written down — what was tried, why it failed.

Days 8-14 — Final ramp. Sponsor sends the all-hands "we're starting this" announcement. First-month meeting cadence booked into calendars (the speed rule: schedule four weeks ahead, not week-to-week). The "Why this platform" statement is drafted by the Sponsor and Guardian together. Kickoff agenda confirmed.

3️⃣ The 10-question pre-kickoff brief

If you can't answer each of these in two clean sentences before the kickoff opens, you're not ready. We use this exact question set internally as the sales-to-delivery handoff brief; it's the rigour required to walk into a kickoff that lands.

How many teams will take part in the project? How big is each one?
What is the Guardian's job position and real influence in the organization (not just title)?
What is the company's decision-making structure — who decides what, and what is the dynamic between leadership and middle management?
What is the Sponsor's actual posture toward this project — engaged, supportive, delegating, sceptical?
Has this organization tried to roll out a similar tool or methodology before? What happened to it?
Have they worked with external consultants or coaches in this domain before? With what result?
How many other teams exist in the organization beyond the one running this transformation? How big is the org overall?
Has Asana — or whichever work management platform you're standardizing on — been used here before, and to what depth?
What risks have you already noticed — political, technical, cultural?
Are there any non-standard arrangements: unusual KPIs, compressed timelines, custom scope? Write them down now, not in week six.

💬 Bringing this to your Sponsor: "Before kickoff, I want us to write down the answers to ten questions about our own organization. Not for the consultants — for us. If we can't answer them clearly, the project won't either."

4️⃣ The Partnership Contract conversation

This is the conversation that almost never happens DIY — and it is the single most underrated act of this stage.

Before the kickoff, the Sponsor, the Guardian, and the operator running the project need to sit in a room (or a 45-minute call) and explicitly agree on the terms of how they will cooperate during the engagement. Not the terms of what they're buying — the terms of how they'll show up to it.

The conversation covers, at minimum:

Speed. "We will turn around feedback on any deliverable within 3 working days. If we can't, we say so by day 1."
Disclosure. "We will tell each other a week in advance about anything that could affect the project — new hires, restructuring, product launches, leadership changes."
Survey discipline. "When a survey goes out, the Guardian reminds, monitors, and chases. Completion under 80% is a project risk, not an admin issue."
Meeting cadence. "Meetings are booked four weeks ahead, not week-to-week. This is what speed looks like in practice."
Sponsor presence. "The Sponsor shows up to kickoff, to the implementation plan review, to launch, and to the post-transformation review. Not just signs."

5️⃣ Where teams stall

‼️ Guardian named on paper, not empowered. This is the most expensive mistake at this stage, and the one nobody catches at the time. The role gets assigned to someone enthusiastic but without the authority, influence, or time to drive change across functions. The damage doesn't show up until Stage Work Conventions 🤝 – Training 🧑‍🏫, when the Guardian needs to force a hard switch — the moment the entire organization moves to the new platform on the same day — and finds they don't have the political weight to call it. By then it's too late to swap roles without losing months.

‼️ 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 organization 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 kickoff rarely shows up at launch either.

‼️ The wider team learns from rumor. No pre-kickoff communication from the Sponsor means the project's existence reaches people through gossip — "I heard we're switching tools again" — before it reaches them through leadership. By the time the official kickoff happens, resistance is already organised. A two-paragraph note from the Sponsor a week before kickoff prevents this almost entirely. Skipping it costs months of trust.

‼️ The Partnership Contract conversation skipped. The Sponsor and Guardian never explicitly agree on speed, disclosure, survey discipline, or 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. In our experience, teams that skip this conversation re-have it in the middle of every operational disagreement for the next six months.

6️⃣ What to prepare before this stage

Before you walk into a kickoff — internal or with us — have ready:

Signed agreement and first payment cleared or scheduled
Guardian named in writing, with the Partnership Guidelines read and the role formally accepted
Sponsor commitment locked: kickoff date confirmed, attendance non-negotiable, first all-hands announcement drafted
Pre-kickoff brief filled in — the 10 questions above, written down, not in someone's head
Participant list compiled — names, emails, roles, team membership for everyone who'll touch the transformation
"Why this platform" draft by Sponsor and Guardian together — one sentence on what removing the current frustrating problem looks like, one sentence on the goal date

✅ 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, once appointed) can act on at the pace your organisation can sustain. The artifacts you get for this stage:

The Pre-Kickoff Checklist — every operational item from this page, in a single working document.
The 10-question pre-kickoff brief — the exact handoff format we use internally between sales and delivery, ready to fill in for your own org.
The Partnership Guidelines — the document that forces the speed/disclosure/cadence/Sponsor-presence agreement before kickoff.
The Sponsor announcement script — the all-hands "we're starting this" note, with two variations (formal and personal).
The Guardian Role Brief — what the role actually involves, written so the person you're appointing can read it once and decide.

💬 Take this with you, and you can run preparation yourself. Hit a wall and want a partner — book your Reliability Diagnostic below.

When to bring in a partner

The package above covers the framework. Most managers run preparation themselves. Bring in a partner when:

The Guardian appointment is contentious. You can see the right person, but they don't have the political authority — and reshuffling needs an outside voice.
The Sponsor agreed at the Discovering problems worth solving 🔬 stage and has gone quiet since. You need someone external to re-anchor commitment before kickoff lands cold.
The org has burned a previous platform rollout and trust in transformation projects is low. The Partnership Contract conversation goes further with a third party in the room.

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

💡 This is Stage 2 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