CM-201b · Module 2

Phase Architecture

4 min read

Three phases. Each has a purpose, a support model, and entry criteria based on the previous phase's results.

Phase One is the controlled pilot: one or two teams, high-touch support, intensive measurement. The goal is organizational conviction and a replicable playbook. The support model is hands-on — dedicated change manager, direct champion access, rapid problem escalation. The exit criterion is validated replication readiness.

Phase Two is the expanded rollout: additional teams, lighter support, validated playbook. The goal is scaling conviction across the organization and hardening the playbook against diverse team contexts. The support model shifts from individual to cohort — training sessions, champion network, shared FAQ, escalation path. The exit criterion is consistent adoption metrics across multiple team types.

Phase Three is broad adoption: organization-wide, self-service, embedded in workflow and onboarding. The support model is ambient — documentation, training library, peer champion network, periodic measurement. The exit criterion is transformation threshold: the new way of working is the default, and the organization without AI is the exception rather than the norm.

Each phase has a duration, a budget, and a support intensity. Most organizations underestimate Phase Two and try to jump directly to Phase Three. Phase Two is where the playbook meets organizational diversity — the teams with different cultures, different technical environments, different champion profiles. Phase Two is where the rollout either becomes robust or reveals its fragility.

Do This

  • Define explicit entry criteria for each phase before the pilot begins
  • Run Phase Two with multiple team types to stress-test the playbook
  • Reduce support intensity gradually — do not cut support abruptly between phases
  • Treat Phase Two results as the actual rollout readiness indicator, not Phase One

Avoid This

  • Skip Phase Two and go directly from pilot to org-wide deployment
  • Move to Phase Three before adoption metrics are consistent across Phase Two teams
  • Reduce the change management budget in Phase Three because "we are past the hard part"
  • Use Phase One champion as the sole Phase Two support — they cannot be everywhere