Change Alliance 👥

Without a formal handoff at this stage, every team in the company waits for you or your Guardian to enforce the conventions. By month three post-launch, the Guardian is exhausted, you have a different priority, and the conventions slowly become "the document we wrote that one time."

The Change Alliance is the antidote: a small group of named people — drawn from your existing Change Leaders cohort — who take on tool-scoped accountability for the rest of the company. Three roles, three scopes, one shared mission: keep the system alive without you having to be the one to do it. You are the one who installs that change of state — by which three people you put in which seat, in a 30-minute meeting, this week.

---

In this document

What happens at this stage

The three Change Alliance roles

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 one 30-minute meeting and one durable structural decision: three Change Alliance roles get filled, each with a named backup. The Guardian facilitates; the Sponsor signs off on the nominations; the Change Leaders cohort accepts or objects to each assignment. A short summary email — sent within 24 hours — locks the assignments on the record.

The meeting is short by design. The depth is in the prep, not the room.

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

Sponsor, Guardian, and Change Leaders were formally appointed at the

Kick-off 🏈 stage and keep those titles for the rest of the Protocol.

The three Change Alliance roles are new here — narrower, tool-scoped accountabilities laid on top of the broader Change Leader role.

---

2️⃣ The three Change Alliance roles

Three roles. Three scopes. One named primary and one named backup per role.

• ⚓ Convention Setter — scope: the whole organisation. 🔴 Failure mode: every team invents its own naming convention by month three. Re-converging costs more than the original convention work did.
• 🛡️ Workflow Guardian — scope: one workflow (each mapped workflow gets its own Guardian). 🔴 Failure mode: the workflow drifts, becomes harder to onboard new joiners into, dies of inconsistency.
• 📣 Awareness-builder — scope: one team (each team gets its own). 🔴 Failure mode: six weeks post-launch, no one in the team remembers why the company switched. "We used to use chat for this and it worked fine."

---

3️⃣ What to prepare before this stage

• Work Conventions document finalised and circulated (the artefact your Convention Setter will defend).
• List of mapped workflows with a candidate Workflow Guardian — and backup — for each.
• Change Leaders cohort with the Guardian's nominations per Alliance role.
• Sponsor briefed on the nominations, with a chance to veto before the meeting.
• 30-minute meeting booked within two weeks of finishing the Work Conventions 🤝 stage.
• Visual canvas (Miro / FigJam / whatever you've used since the Implementation Plan 🗺️ stage) with the three role slots ready to fill.

---

4️⃣ Avoid this if you don't want your transformation to fail or delay

‼️ Don't pick Workflow Guardians who don't use the workflow daily. Authority without daily usage is a guarantee of decay. The Guardian must be the doer, not the doer's manager.

‼️ Don't skip the Awareness-builder, thinking "the Sponsor covers it." The Sponsor sets initial direction; they don't live inside the team's daily talk. Without an Awareness-builder per team, the why goes silent within six weeks of launch.

‼️ Don't assign Alliance roles without backups. An Alliance role with no backup is one that goes dark the first time real life intervenes. Every role gets a named primary and a named backup on the same day.

‼️ Don't conflate Change Leader work with Alliance role work. Change Leader is a broad change-management role; Alliance roles are narrower and tool-scoped. An Alliance member who hasn't done the Change Leader work first will enforce conventions they haven't internalised.

‼️ Don't let the Convention Setter role float between people. "Whoever's around will handle it" is the death of the convention. One named primary, one named backup, full stop.

‼️ Don't accept "I'm too busy" from the right candidate without re-scoping. A weak Convention Setter is worse than a strong one with an explicit time commitment defended by the Sponsor. Renegotiate the workload; don't silently substitute the second-best candidate.

---

✅ 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 Change Alliance Role Brief — the three-role document with scopes, weekly behaviours, time commitments, and the "what failure looks like" pattern for each role.
• The Alliance Role Nomination Scorecard — the three role-fit tests (cross-functional / daily-user / daily-talk) in checklist form, used in the prep hour before the meeting.
• The 30-Minute Role-Assignment Meeting Agenda — the four-move structure with timing, facilitator notes, and the closing question that turns the meeting into the first Alliance backlog.
• The Alliance Summary Email Template — drop-in template for the Guardian to send within 24 hours of the meeting. Names primary + backup per role.
• The Backup-Per-Role Convention — the single-page rule for who steps in when, and how the handoff is communicated to the team.
• The Asana & Work Management Resources Project template — the educational project shared with each Alliance member, with resources, links, and onboarding steps they reference when educating their teams.

💬 Take this with you and your team can run the Change Alliance setup yourself. Hit a wall on which person fits which role 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:

• The nomination conversation has political pressure and you need neutral cover to push back on the wrong name without spending internal capital.
• You can't identify a daily-user Workflow Guardian for one or more mapped workflows — often a sign the workflow itself is mis-scoped.
• You're inheriting a half-built workspace from a previous transformation attempt, and the Change Leaders cohort needs re-forming before the Alliance can be named on top of it.

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