Interactive Checklist
Check items as you complete them. Progress is saved locally.
0%
1 Phase 1: Impact Assessment
Document the proposed change in a decision card with scope, rationale, and alternatives considered
Identify all systems and services affected — list each in card notes
Estimate the blast radius: number of users, services, and data stores impacted
Assess rollback complexity (trivial / moderate / difficult / impossible)
Check the change calendar for conflicts with other planned deployments or freezes
Tag the change priority level: P1 (emergency), P2 (planned), P3 (improvement)
2 Phase 2: Stakeholder Alignment
Notify all affected team leads — add them as watchers on the change card
Schedule a change review if blast radius exceeds 2 teams or 1,000 users
Get written approval from the service owner (comment on the card)
Create a communication plan card: who needs to know, when, and through what channel
Document the customer-facing impact (if any) and draft external communications
3 Phase 3: Execution Preparation
Write a detailed runbook as a checklist card linked to the change card
Build and test the rollback procedure — verify it actually works in staging
Set up monitoring dashboards for key metrics (error rate, latency, throughput)
Define success criteria: what metrics confirm the change is working correctly
Schedule the change window and notify on-call engineers
Create a Vizually.AI canvas snapshot before the change for baseline comparison
Pre-populate an incident card (in case rollback is needed) with contacts and escalation paths
4 Phase 4: Execution & Monitoring
Execute the runbook steps in order, checking off each in the canvas
Monitor dashboards for 15–30 minutes post-change (longer for database migrations)
Verify success criteria are met — update the change card status to "Deployed"
If metrics degrade beyond thresholds, execute rollback immediately — do not debug in production
Notify stakeholders of completion (or rollback) via the communication plan
5 Phase 5: Post-Change Review
Update the change card with actual vs. planned timeline and any issues encountered
Run AI Health Check on the project canvas to confirm no downstream tasks were disrupted
If rollback was needed, schedule a blameless review within 48 hours
Document lessons learned in the card notes for future reference
Archive the change card to Done with a completion timestamp