Beacon

Change management

View as Markdown

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

  1. 11) Classify change

    Define low-risk, high-risk, or breaking, and list impacted teams.
  2. 22) Prepare validation

    Ensure tests, rollback criteria, and explicit execution owner.
  3. 33) Execute in proper window

    Avoid external risk windows and confirm on-call coverage.
  4. 44) Verify post-release

    Monitor core metrics and close only after sustained stability.

Decision matrix

TypeMinimum approvalRollback requirement
Low-risktechnical ownerrecommended
High-risktechnical owner + operations ownerrequired
Breakingtechnical owner + operations owner + external communicationrequired

Relationship with changelog

Every production change should include changelog context with:

  • release timestamp;
  • expected impact;
  • mitigation path if needed.