Change management
Change-management model to reduce technical and operational risk in production.
explanation • updated 2026-03-15
Goal
Apply production changes with predictability, reversibility, and clear communication.
Change cycle
11) Classify change
Define low-risk, high-risk, or breaking, and list impacted teams.22) Prepare validation
Ensure tests, rollback criteria, and explicit execution owner.33) Execute in proper window
Avoid external risk windows and confirm on-call coverage.44) Verify post-release
Monitor core metrics and close only after sustained stability.
Decision matrix
| Type | Minimum approval | Rollback requirement |
|---|---|---|
| Low-risk | technical owner | recommended |
| High-risk | technical owner + operations owner | required |
| Breaking | technical owner + operations owner + external communication | required |
Relationship with changelog
Every production change should include changelog context with:
- release timestamp;
- expected impact;
- mitigation path if needed.