Training 🧑🏫
Capability building that survives the first stressful month.
This stage is the first stage where the framework alone doesn't carry you. The first eight stages are decisions, mapping, alignment — work an experienced internal Operator can do with the toolkit and discipline.
This stage is different: ~10 hours of structured training, in front of a live team, on a platform you're using to install behaviour change. By reading this you've already done the harder cognitive work — now you have a real choice to make about who delivers the training.
In this document
Three ways teams run this stage
The License to Operate Quality Gate
What to prepare before this stage
Avoid this if you don't want your transformation to fail or delay
What you get with the full protocol
1️⃣ What happens at this stage
This stage is ~10 hours of practical training across three role-specific tracks, followed by a Quality Gate survey that certifies the team is ready to operate the system on Launch Day. Each track is hands-on — laptop open, clicking inside the workspace you built across Stage Implementation Plan 🗺️ – Work Conventions 🤝. The stage closes with a 30-minute Guardian debriefing that ties training outcomes to the Launch Day plan.
Training sessions are combined across teams wherever the audience overlaps — the same Basic content can serve 2–3 teams in one room, saving 40–60% of facilitator hours without weakening the experience. Manager track stays separate; the content is different and the audience is smaller.
2️⃣ Three ways teams run this stage
Across the teams we've watched arrive at this stage, three paths emerge. Ordered from most common to least, so you can self-select fast.
Path 1 — Bring in an experienced 3rd party (~80% of teams)
You contract an outside trainer with a track record of practical Asana workshops and implementations. They run the three tracks, read the Quality Gate signal, and hand the keys back to your Guardian on Launch Day. You stay accountable for the calendar and the room; they're accountable for delivery and diagnostic.
Why it's the 80% choice: 10 hours of hands-on workshop content is real work, the Quality Gate signal needs deployment-pattern recognition to read, and a neutral cross-industry voice lands "this is the new way" better than an internal voice the team is already familiar with. The trade-off is cost — usually less than the cost of a shaky Launch Day.
Path 2 — Internal champions lead the workshops (~10% of teams)
You already have one or two people in the organisation who've used Asana well at depth AND can teach. They lead the three tracks themselves, scaffolded by the Workshop Checklist — the most important workshop phases, in order — which you receive with the toolkit.
When this works: champion is a current daily user, has facilitated training before, has authority in the room. When it breaks: champion is only an enthusiast — knows the platform, can't teach it. If you can't name your champion in two sentences, you're not on Path 2.
Path 3 — Grow internal champions first via Train-the-Trainer (~10% of teams)
You don't have champions yet but want capability long-term — not a one-off implementation. We run a structured Train-the-Trainer programme with your candidates: they learn both the platform depth and the workshop facilitation craft. Then they run the workshops themselves on your timeline.
When this fits: you have time before the deadline, you're committing to the platform as a long-term operating system (not a pilot), and you'd rather build internal capability than rent it. Trade-off: longer end-to-end than Path 1, because two phases of training (us → them → them → team).
3️⃣ The three training tracks
Three tracks, three audiences, one outcome: everyone walks into Launch Day knowing how to operate the system at the level their role demands.
🧑🎓 Basic training
- Audience: All team members who will use the platform daily.
- Scope: ~4 hours, typically split into two 2-hour blocks.
- Outcome: Technical fluency in projects, tasks, custom fields, dependencies, Inbox and My Tasks, advanced search. Hands-on exercises throughout.
🎓 Intermediate training
- Audience: Anyone needing portfolios, advanced custom fields, automations, forms, integrations.
- Scope: ~4 hours.
- Outcome: Operational depth on the features that separate a power user from a casual one — automations, conditional logic, multi-project workflows, formulas.
👔 Manager training
- Audience: Every manager whose team will operate in the system.
- Scope: ~2 hours, separate from team training.
- Outcome: Delegation patterns, planning and replanning rhythms, multi-project oversight, productive meetings, the "no internal task emails" pledge.
4️⃣ The License to Operate Quality Gate
After each training track, every participant takes a short survey — what we call the License to Operate Quality Gate. It is not a test. It is a Kirkpatrick Level 2 (knowledge) + Level 3 (intent) measurement that does three things at once:
- Certifies readiness — confirms participants can operate the platform before they're handed the workspace keys on Launch Day.
- Surfaces commitments — asks for specific behavioural pledges ("I will archive my Inbox 2× per day," "I will not send internal task emails") that turn training into a psychological contract.
- Catches blockers — if a meaningful chunk of the team flags "Due Dates" or "My Tasks" as unclear, you intervene now , not on Launch Day morning.
Two forms run in parallel: a User form for everyone who attended Basic or Intermediate (skill confirmation + commitments), and a Leader form for managers (the "no email" pledge and the redirect-back-to-Asana confidence check).
🔴 Failure mode without the Gate: Launch Day reveals which competencies didn't land, and the first week of "real work" becomes the first week of remedial coaching. Adoption decays because the team learns to work around the gaps instead of through them.
Bringing this to your CFO: "We're committing the team's time to 10 hours of training. The Quality Gate is the diagnostic that proves it landed before we change how the company operates. It's the difference between a transformation and a training expense."
5️⃣ What to prepare before this stage
- Workspace finalised across Stage Implementation Plan 🗺️ – Work Conventions 🤝 — projects exist, conventions documented, mapped workflows live.
- Change Alliance named at the Change Alliance 👥 stage so Alliance members can co-facilitate from inside the room.
- Training calendar — three tracks scheduled, no further than two weeks apart, ideally finishing 7–10 days before Launch Day.
- Attendance enforced by the Sponsor — every team member confirmed; no "I'll catch the recording" exits for live participants.
- Laptops + working accounts — each participant has their own active account in the workspace, screen-sharing capable.
- Trainer briefed on conventions — whoever delivers the training knows your conventions, mapped workflows, and Change Alliance roles, so the training reinforces them rather than contradicting them.
- Quality Gate forms ready — survey links prepared, to be pasted into the meeting chat in the last 10 minutes of each session (not "sent later by email").
- Debriefing booked with the Guardian — 30-minute meeting after the last training, to close the stage and tee up Launch Day.
6️⃣ Avoid this if you don't want your transformation to fail or delay
‼️ Don't let people skip Basic to "save time." The skipped attendees are precisely the ones who'll derail the team's first week — they'll ask the questions that should have been answered in week zero, and the team will pause to help them every time.
‼️ Don't replace live training with recordings. Recordings serve as reinforcement; they don't replace the live exercise loop. Operators who try to "just send the videos" end Stage 9 with a team that has watched but not done — and Launch Day exposes the gap.
‼️ Don't send the Quality Gate survey "later by email." Response rate craters, the data goes cold, the diagnostic window closes. Paste the link in the meeting chat at the end of the call; reserve the last 10 minutes for completion. No exceptions.
‼️ Don't pretend the Manager track is optional. Managers shape every behaviour the team will copy. A manager who hasn't internalised the "no internal task emails" pledge will undo the pledge for the whole team within two weeks.
‼️ Don't half-DIY between the three paths. Pick one and commit. Champion-led with the Workshop Checklist, Train-the-Trainer, or partner-delivered — each has its own discipline. Blending them ("partner runs day 1, our champion runs day 2") produces none of them. A trainer reading slides is worse than no training; teams will spend Launch Day un-learning what they sat through.
‼️ Don't act on the Quality Gate signal silently. If the data flags a blocker, name it to the Sponsor and the affected team within 48 hours, with a concrete remediation step. Silent intervention reads as no intervention.
✅ What you get with the full protocol
The full Reliability Protocol is delivered as one weekly action by email. 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 that week. The artifacts you get for this stage:
- The Three-Track Workshop Agenda — minute-by-minute structure for Basic (~4h), Intermediate (~4h), and Manager (~2h) tracks, with exercises, icebreaker patterns, and the cue points to switch between explanation and live demonstration.
- The Workshop Checklist — the most important workshop phases in order, for Path 2 teams whose internal champion leads the training. Stand-alone scaffold; works whichever tracks you run.
- The License to Operate Survey Kit — both forms (User and Leader), positioning scripts ("Readiness Check," "Leadership Pact"), the timing pattern that protects response rate, and the thresholds that trigger intervention.
- The Pre- & Post-Training Email Templates — drop-in emails to send Change Leaders and the Guardian before training kicks off and after it closes, plus the "team questions" project structure to log open questions after the workshops.
- The Conventions Reinforcement Pack — daily rituals, typical-work-day patterns, Inbox & My Tasks usage, do's-and-don'ts in delegation — the resource library you hand participants as homework reinforcement.
- The After-Training Debriefing Guide — 30-minute agenda for the Guardian session that closes Stage 9 and bridges into Launch Day.
💬 Take this with you and your team can run this stage yourself. Hit a wall on curriculum, facilitator capacity, or how to read the Quality Gate signal — book the session below.
When to bring in a partner
If you're on Path 1 (the 80%) — the criteria below sharpen when a partner earns its keep. The package above is the framework, the agendas, and the diagnostics. Most operators run the first eight stages themselves. This stage is the one most operators bring us in for. Specifically:
- You don't have an internal trainer who can run 10 hours of hands-on workshop content and switch fluently between explanation and live operation inside the system.
- The Quality Gate signal is ambiguous and you need someone who has seen many deployments to read it — knowing what "intervention" means at a given score is pattern recognition, not protocol.
- The team is sceptical and a neutral trainer with cross-industry credibility lands the "this is the new way" message better than an internal voice the team is already familiar with.
💡 This is Stage 9 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.