domains / families / business / change-management

change-management

combined

Implement change management processes. Configure CAB reviews, change windows, and rollback procedures. Use when managing production changes. Framework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership, or when user mentions change management, change rollout, managing resistance, org change, reorg, or pivot communication.

When to use

• Establishing change management processes for production environments
• Implementing change advisory board (CAB) workflows
• Defining change classification and approval requirements
• Configuring automated change tracking in CI/CD pipelines
• Handling emergency changes with proper controls and documentation

When not to use

• Guidance and checklists only; not legal advice and not a substitute for a qualified auditor.
• Docs-only import: upstream templates and scripts not bundled.

Skill page

Conflict

The three copies define two different procedures for the same skill name. BagelHole and sickn33 describe ITIL/SOC 2 production change management (CAB, change classification, rollback, and change request templates). LeoYeAI describes organizational change management using the ADKAR model (awareness, desire, knowledge, ability, reinforcement) for reorgs, pivots, and tool migrations. Because the copies overlap in name but each contains material steps the others lack, crowning one would hide a real alternative.