do not reward the rescue you created.
some organizations celebrate emergencies because emergencies create visible heroes.
a deadline is ignored for weeks. ownership remains vague. risk is reported and dismissed. then one person works through the night, saves the launch, and receives public praise.
the applause teaches the wrong lesson.
heroics can be necessary. customers still need help when the system fails. but a rescue should trigger an investigation, not become the operating model.
ask what made the emergency predictable.
was the work started too late? did one person hold information everyone needed? did a leader avoid choosing between scope and time? were warnings punished until the problem became undeniable?
the rescuer may also be part of the pattern. people who gain status from emergencies can become reluctant to build systems that make their heroism unnecessary. knowledge stays private. delegation remains weak. every solution depends on the same person returning.
reward prevention.
recognize the operator who removed a recurring failure, documented a handoff, simplified a process, or raised a risk while the response was still inexpensive. those contributions are quieter, but they create capacity instead of stories.
after a crisis, separate gratitude from evaluation. thank the people who protected the result. then examine the decisions that required the sacrifice. do not let effort erase accountability.
a healthy company does not need exhaustion to prove commitment. it does not confuse chaos with speed or rescue with leadership.
after the applause, ask which ordinary discipline would have made the dramatic effort unnecessary. put that discipline into the next plan and give it an owner.
the best emergency is the one the customer never experiences.
build a culture where fewer heroes are required because more people can see, own, and prevent the problem.
