2 min lesson
Close the loop and write the narrative
Explain the order in "Close the loop and write the narrative", then say how you would verify the result.
Step 1 of 2
Close the loop and write the narrative
A fix is not done when it ships; it's done when the metric confirms the regression resolved. Verify in the same series you detected it, on the same segments and watch for the regression hiding in one slice while the global line recovers. Then write the postmortem-grade narrative so the next person inherits the lesson, not just the patch.
- 1Verify the fix. Confirm the metric returned to baseline in the affected segments, not just globally.
- 2Check for displacement. Make sure you fixed the regression rather than moving it to another slice.
- 3Quantify recovery. Restate blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition. post-fix so the win is measured, not assumed.
- 4Write it up. What broke, how it was detected, root cause and the prevention that stops a repeat.
- What broke
- The user-visible symptom and the metric that moved
- How detected
- Which detector fired and how fast, or why it didn't
- Root cause
- Model vs harness vs infra, named on the dimension you logged
- Prevention
- The canary, alert or schema change that catches it next time
The prevention line is the one that compounds, because it turns one incident into a permanent detector.
In the behavioral and hiring-manager rounds, tell a regression story end to end: how you detected it, how you quantified blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition. to justify the priority, how you drove the decision and how you verified the fix and prevented a repeat. The postings describe the team as truth-seeking, so show a story that ends in a decision. A story that ends at "I found it" reads as analysis; one that ends at "and here's the detector that now catches it" reads as ownership.
Don't over-escalate. Paging the team for every blip burns trust and the same alert fatigue you fight in detection. Calibrate to real user impact and reserve the incident path for fast, spreading, budget-burning regressions, and file the rest with their evidence and blast-radius estimate attached.
Learn more
Optional practice