Context
Skilled people repeatedly prevent visible failure through memory, urgency, personal access, and informal coordination.
Problem
Heroic recovery creates genuine value while masking structural fragility. Because the incident ends successfully, the organization rewards the intervention and underinvests in the conditions that would make it unnecessary.
Forces
- Emergencies require judgment and speed.
- Formalizing every edge case can create bureaucracy.
- Experts gain identity and leverage from indispensable knowledge.
- System improvement competes with immediate delivery.
Pattern
Treat repeated rescue work as evidence about missing ownership, interfaces, defaults, automation, observability, or authority. Preserve expert judgment for novel conditions while turning recurring conditions into tested, transferable system behavior.
Apply it
After intervention, record what signal was noticed, what access or knowledge was unique, which boundary failed, and what earlier action would have prevented urgency. Prioritize changes that reduce recurrence and shorten safe recovery without requiring the same person.
Failure modes
- The person is documented as the escalation path instead of transferring capability.
- Automation reproduces an undocumented workaround.
- Runbooks exist but cannot be exercised safely.
- “No heroics” becomes criticism of appropriate incident leadership.
Evidence needed
Trends in repeated incidents, after-hours intervention, single-person dependencies, recovery time, runbook success, and the percentage of routine recovery executed safely by the wider team.