You do not rise to the level of your aspirations. You fall to the level of your training.
Hospitals do not wait for emergencies to practice. They run drills. Codes are called over the intercom, teams mobilize, and the entire choreography is rehearsed — not because they need the exercise, but because muscle memory saves lives when the real thing hits.
Tech teams rarely do this. We wait for production to break and call it “learning by doing.” That is like a hospital saying their trauma training is the next car accident that rolls through the door.
The idea is simple: simulate a real incident in a controlled environment and let the team respond as if it were real.
You do not need chaos engineering tools for this, although they help. A well-structured tabletop exercise where someone narrates the scenario and the team talks through their response is already better than nothing.
In hospitals, residents rotate through departments — surgery, internal medicine, ER, pediatrics — specifically so they are not useless outside their specialty when a crisis crosses domains.
In tech, this maps to on-call rotations that span teams, paired debugging sessions across services, and shadow shifts where junior engineers observe how a different team handles their stack. The goal is not to make everyone an expert in everything. It is to make sure nobody freezes when they see an alert from an unfamiliar service.
Emergency rooms do not improvise their communication. There is a protocol for who gets called, in what order, through which channel, with what information. The reason is not bureaucracy — it is that confusion during a crisis kills people.
In tech, it kills uptime.
Decide these things now, while things are calm:
Having a fill-in-the-blank template for incident updates removes the cognitive overhead of composing messages under stress:
[SEV Level] - [Service/System]
Status: [Investigating / Identified / Monitoring / Resolved]
Impact: [Who/what is affected]
Current action: [What is being done right now]
Next update: [Time]
Nobody writes poetry during a crisis. Make the format boring and consistent.
This is the part nobody wants to talk about.
Hospital staff are trained for the emotional weight of emergencies. They have peer support, structured debriefs, and an institutional acknowledgment that the work takes a toll. Nobody expects a surgeon to be emotionally unaffected after losing a patient.
In tech, we pretend that a 3 AM page followed by four hours of debugging followed by a morning standup is just part of the job. It is part of the job. But pretending it costs nothing is how you burn people out.