revops-change-management

What problem does it solve?

Revenue teams often run training sessions and roll out new processes—yet adoption fails because the rollout ignores human behavior, reinforcement, and transition realities.

Core Features & Use Cases

• Plan the Change: run impact analysis across people, process, systems, data, and financial risk; design stakeholder strategy and communication architecture using traffic-light classification; create a transition plan with cutover, rollback, and productivity-dip expectations.
• Make It Stick: design behavior change through enablement architecture (forgetting curve + spaced repetition, coaching using reverse salient, deep practice, creation tasks, and organizational energy infrastructure).
• AI-Specific Change Management: address FOBO (fear of becoming obsolete), prevent shadow AI issues via a governed adoption framework, and plan for EU works council consultation when deploying high-risk AI.

Quick Start

Use this skill to build an adoption-ready rollout plan by applying the one-variable rule, classifying the change as Green/Yellow/Red, and mapping a reinforcement cadence for the first 90 days.