domains / business / change-management / change-management

change-management

Skill card

combined

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.

Repositories

Other copies

Combined skill

# Change Management

This skill covers two distinct change management procedures. Select the procedure that matches the task.

## Procedure A: Production Change Management (ITIL/SOC 2)

Use when managing production changes, CAB reviews, change windows, or rollback procedures.

1. Classify the change:
   - standard: Low risk, pre-approved, no lead time, within maintenance window.
   - normal_low: Low risk, peer review (1 approver), 2 business days lead time.
   - normal_medium: Medium risk, team lead + peer review (2 approvers), 5 business days lead time.
   - normal_high: High risk, CAB review required, 10 business days lead time.
   - emergency: Variable risk, Emergency CAB (minimum 2 approvers from on-call), immediate implementation, retroactive documentation within 48 hours.
2. Create a change request using the template:
   - metadata: id, title, requestor, date_submitted, target_date, change_type.
   - description: summary, detailed_description, business_justification, affected_systems, affected_services, affected_users.
   - risk_assessment: risk_level, impact_if_failed, likelihood_of_failure, risk_mitigation, dependencies.
   - implementation: change_window, implementation_steps.
   - testing: pre_change_testing, post_change_verification.
   - rollback: rollback_plan, rollback_trigger, rollback_estimated_time, rollback_steps, data_rollback.
   - communication: stakeholders_notified, notification_sent_date, status_page_update, customer_notification_required.
   - approvals: technical_reviewer, security_reviewer, cab_approval_date, cab_notes.
   - closure: implementation_date, implementation_result, post_implementation_review, lessons_learned, follow_up_actions.
3. Run the CAB workflow:
   - regular_cab: Weekly, Thursday 2:00 PM.
   - emergency_cab: On-demand, minimum 2 members required.
   - cab_members: permanent (Engineering Manager, Security Team Representative, Infrastructure/SRE Lead, Release Manager) and advisory (Business stakeholder, Database administrator, Network engineer).
   - agenda: Review emergency changes from prior week, review high-risk changes.

## Procedure B: Organizational Change Management (ADKAR)

Use when announcing a reorg, switching tools, pivoting strategy, killing a product, changing leadership, or managing resistance.

1. Awareness: Communicate the WHY before the WHAT. Explain the problem, why now, and who made the decision.
2. Desire: Address "What's in it for me?" for each stakeholder group. Run a concerns and questions session within 48 hours of announcement.
3. Knowledge: Provide step-by-step documentation, training, and clear answers to common scenarios. Use live training, documentation, video walkthroughs, shadowing, or office hours.
4. Ability: Provide time to practice, a safe environment to make mistakes, reduced load during transition, and access to help.
5. Reinforcement: Track adoption, recognize early adopters, model the new behavior, remove the old option, and apply consequences for non-adoption.

## Conflicts

- LeoYeAI/openclaw-master-skills uses the ADKAR model for organizational change, while BagelHole/DevOps-Security-Agent-Skills and sickn33/agentic-awesome-skills use ITIL/SOC 2 production change management with CAB reviews and rollback procedures.