Onboarding 👋
The system becomes standard for current & future members.
This stage looks small from the outside: one project template, small daily reps, three short moments with the team. The smallness is intentional — adoption is a function of repetition under low friction, not of effort. The Operator's job here is not to teach (training did that) and not to announce (Launch did that). It's to install a daily rep, defend the cadence it lives in, and make sure nobody stalls without anyone noticing.
The Training 🧑🏫 stage gave the team the skills. The Launch Day 🚀 stage drew the line. This stage installs the daily repetition. The Consolidation of changes 🌳 stage checks the new rhythm holds.
In this document
The four-week onboarding project that drives Asana adoption
Why repetition is the whole point
The three meetings that frame onboarding
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
Stage 11 runs in parallel with the first weeks of normal work after Launch. Every participant — every person who'll use the platform daily — gets their own personal onboarding project, duplicated from a single template, with deadlines automated across four weekly bundles. The project is structured so the participant practices the technical features and the cooperation habits in the system itself, on real work, not in a sandbox.
The Guardian duplicates the template once per participant, monitors progress across the cohort via a portfolio dashboard, and intervenes the moment a project stalls. The whole stage is delivered as a live introduction at the last ten minutes of the final training session — not a "watch the video and figure it out" handoff. By the time that training session ends, every project has been opened, every participant knows where to find their tasks, and the cadence has started.
Note on naming (Sponsor, Guardian, Change Leaders, Change Alliance) — click to reveal
Sponsor, Guardian, and Change Leaders were formally appointed at the
Kick-off 🏈 stage.
The Change Alliance was named at the Change Alliance 👥 stage.
By this stage every role is in place — your job is to keep them executing, not to introduce anyone new.
2️⃣ The four-week onboarding project that drives Asana adoption
One template. One project per participant. Four weeks of work the participant does on real tasks, not on a tutorial.
A few non-negotiables baked into the template:
- Tasks are short. Each task takes a few minutes — no task in the project should feel like "I need to block half an hour for this." Small enough to slip between other tasks. Small enough that finishing one releases the next.
- Tasks describe an action the participant performs, not content to read. "Create your first task in My Tasks and assign yourself a due date" — not "Read about My Tasks." The task name is the instruction.
- Due dates are automated. When the participant starts the project, a rule sets the dates across all four weeks. They don't pick the schedule; they meet it.
- The Guardian sees everything in one place. All onboarding projects sit in one portfolio. One glance = the health of the whole cohort.
3️⃣ Why repetition is the whole point
Training taught the team how to use the platform. Launch made the platform the only valid place to work. Neither built a habit. Habits are what your team does on autopilot at 9:14 on a Tuesday morning — and autopilot is built from repetition, not from understanding.
The Reliability Protocol's Adoption phase reduces to a single equation that every Operator at this stage internalises:
4️⃣ The three meetings that frame onboarding
Three meetings. The first introduces the project, the second catches drift, the third closes the loop and hands ownership to the Guardian and the Change Alliance for the long term.
- 🏁 Start — the last 10 minutes of the final training session (the Training 🧑🏫 stage). The project is introduced for the first time. The Guardian walks the team through how to open it, how the four weekly sections are arranged, how the automated deadlines work, and what to do if a task runs long. By the time the meeting ends, every project has been opened at least once.
- 🔄 Check-up — held during the Consolidation of changes 🌳 stage, once the cohort is two to three weeks in. ~20 minutes. The Guardian asks three questions: Was it easy to follow through? What was the hardest task? What was your aha moment? The point isn't completion data (the portfolio shows that already) — it's the texture underneath: where the friction is, where the desire is, where the next intervention lives.
- 🎯 Summary — runs as part of the project sum-up meeting with leaders (the responsibility-transfer meeting). The Guardian shows portfolio progress, hands the day-to-day monitoring of each workflow's onboarding cohort forward to the Workflow Guardians named in the Change Alliance at the Change Alliance 👥 stage, and frames the completed projects as the org's permanent onboarding template for every future hire.
5️⃣ What to prepare before this stage
- The onboarding project template is loaded into your Asana workspace — a single template, four weekly sections, chunked tasks, automations live.
- The participant list is final — everyone who will use the platform daily has a name and an email, ready to be assigned a project on the day the stage starts.
- The start moment is locked in as the last 10 minutes of the final training session (the Training 🧑🏫 stage). Don't try to schedule a standalone introduction a week later — the audience disperses fast.
- The portfolio is set up so all onboarding projects land in one place and the Guardian can see cohort health at a glance.
- The check-up meeting is on the calendar for ~2–3 weeks into onboarding, before the summary meeting.
- The Guardian has 10–15 minutes a day for the next 4 weeks — to scan the portfolio, spot red dates, and message the participant whose project hasn't moved.
6️⃣ Avoid this if you don't want your transformation to fail or delay
‼️ Don't separate the start from the last training session. The 4-week project does not launch itself by email. The end-of-training moment is where each project gets opened, walked through, and committed to in the room. Without it, week one becomes "I'll get to it tomorrow" — and then week two does too.
‼️ Don't let red dates accumulate. The moment a participant has three overdue tasks, the project has mentally collapsed and the habit is dead. The Guardian's job is to replan with the participant the same day — not to wait until the check-up meeting to notice.
‼️ Don't run the project as a sandbox. Onboarding is not "practice space." The participant has to log their actual work in the project from day one. Sandboxing teaches the team to use Asana for tutorials, not for work — and the second the tutorial ends, they revert.
‼️ Don't measure completion as success. A participant who closed every task but hasn't opened the platform in five days has not adopted. One who's still posting comments in their project in week six has. Measure repetition, not check-off.
‼️ Don't ship the videos cold. The "send a video and hope they run it themselves" version of this stage fails most of the time because nobody opens the project on day one. If you're going to do Stage 11 at all, do the live introduction at the end of training. The repetition can't form a habit that never started.
✅ 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 Asana Onboarding Project Template — the 4-week structure (one section per week, chunked tasks each a few minutes long, due-date automations baked in, portfolio configuration pre-set) plus the Guardian setup guide for duplicating it per participant and assigning it live at the end of training.
- The Three-Meeting Agenda Pack — start agenda (the last 10 minutes of training, where each project is introduced and opened in the room), midway check-up agenda (the three questions, what to listen for, how to spot drift), and the summary meeting agenda (responsibility transfer to the Workflow Guardians from the Change Alliance 👥 stage, and the framing that turns the template into the org's permanent onboarding asset).
💬 Take this with you and your team can run Onboarding yourself. Hit a wall and want a partner — book the session below.
When to bring in a partner
The package above covers the framework. Most operators run it themselves. Bring in a partner when:
- You don't have spare cycles for regular portfolio monitoring. Adoption is lost in 48-hour windows — partner-side co-monitoring catches red dates before they pile up.
- Replanning conversations feel political. Telling a team member "your project hasn't moved in six days" is a calm operational conversation in theory and a charged one in practice. A neutral partner can hold that line in the first four weeks while your authority is still being recalibrated post-Launch.
- The start moment slipped. If you missed the "last 10 minutes of training" window and now need a standalone introduction a week later, the audience is already drifting — a partner running that introduction buys back the energy you would have lost.
💡 This is Stage 11 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.