Hi everyone,
For the next 15 weeks I’m publishing the Reliability Protocol here, one stage a week.
It’s the implementation framework we use at Remote Sensei to roll out Asana in mid-size and larger companies. It doesn’t stop at setup and training. It runs from the first “what’s actually broken?” conversation to the review a year later, when you find out whether the change stuck. Most of it is about habits and handoffs, because software doesn’t change how people work. Habits do.
One thing is new. AI agents are now part of the processes we implement and optimise: AI Teammates in Asana, AI Studio rules, agents built in Claude. So every stage covers where agents fit, and where they don’t yet.
How the series works:
- every stage gets its own topic, with the core of the stage in the post and the diagrams as images
- when a new stage goes live, I reply here with the link. You can mark this topic with
to get notified.
Alignment
- Stage 1: Discovering problems worth solving
- Stage 2: Preparation
- Stage 3: Kick-off
- Stage 4: Audit
- Stage 5: Implementation Plan
Foundation
- Stage 6: Mapping & Implementing Workflows
- Stage 7: Work Conventions
- Stage 8: Change Alliance
Adoption
- Stage 9: Training
- Stage 10: Launch Day
- Stage 11: Onboarding
- Stage 12: Consolidation of changes
Momentum
- Stage 13: Operational handover
- Stage 14: Business Impact Review
- Stage 15: After Transformation
Questions and pushback are welcome in any stage topic, and so are your own rollout stories. I’ll answer there.