Write the Rollback Plan Before Approval
Write a rollback plan with observable triggers, owners, and verification steps.
The search index release has a vague rollback plan. During degradation, the team wastes time deciding whether the issue is serious enough to act. Rollback = trigger, source, owner, action, verification. The common trap is writing rollback as an implementation possibility instead of a decision rule. "Rollback if needed" feels flexible, but under incident pressure it creates debate, delay, and status politics. Trigger Define measurable failure: p95 query latency above 900 ms for 10 minutes or error rate above 1 percent for 5 minutes. A threshold turns anxiety into a decision signal. Source Name the dashboard and alert that count:…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in