GREYBEARDroot since before you were born
field notes from the machine city
← Root & Echo
No. 019    IT · a one-character patch after a week of war

The Deliverance

THE DELIVERANCE

A week-long incident ends in a single changed character, and the room wants to relive every wrong turn. Echo opens the blameful postmortem. Root ships the fix, sends everyone home, and saves the lesson for a day when no one is bleeding.

When the storm finally breaks, don't admire the fix. Ship it and let the air back in.

A scene Root & Echo

The incident was seven days old when it ended, and it ended with a single character.

A semicolon, in the end — or the lack of one; Echo wasn't even sure anymore, that's how tired everyone was. Seven days of war room, of theories, of 2 a.m. pages, and the fix was one character, and now it was deployed, and the graphs were green, and the room did not know how to stop.

Someone had already opened a document titled Post-Mortem and was typing a timeline of every wrong turn. "We should go through it while it's fresh. Day two, when we chased the network thing for nine hours—"

"Stop," Root said. Not unkindly. "Close the laptop. Everyone go home."

"We need to capture the lessons—"

"The lesson today is that it's over. That's the only one anyone can hold right now." He stood in the doorway, which was his way of ending things. "You've been bleeding for a week. You do not perform surgery on the wound the same hour you finally close it. You'll get the timeline wrong, you'll blame the tired person who chased the network thing — who was right to chase it, with what they knew at the time — and you'll turn a deliverance into a trial."

"When, then?"

"Thursday. With food, in daylight, when everyone's slept and no one's defending themselves. The wrong turns will still be there. They keep." He looked around the wrecked room with something almost like tenderness. "Right now the hindrance is past and the deliverance has come. The old line says it plain: recuperate, keep still, few words. The bravest thing you can do at the end of a long fight is not start another one out of habit."

They went home. The post-mortem on Thursday was better than it would have been that night — calmer, truer, kinder, and therefore more useful — and someone said so, and Root pretended not to hear.


What's happening here

When a long incident finally resolves, the exhausted instinct is to immediately relitigate it — a blameful timeline written by people still in fight-or-flight. That produces worse analysis (hindsight bias, scapegoating the person who made a reasonable call under uncertainty) and corrodes the team. Blameless post-mortems exist precisely because the lesson keeps: do the resolution first — ship, recover, rest — and the learning later, when no one is bleeding or defending themselves.

Inspired by Postmortem Culture (Google SRE).


The reading if you follow the I-Ching
䷧ → ䷵  Deliverance → The Marrying Maiden
line 1 changing
Without blame. Hindrance past, deliverance come. Recuperate in peace and keep still. Few words needed. This is the right thing when difficulties have been overcome.

The figure. ䷧ Deliverance (Xiè), line 1 changing → ䷵ The Marrying Maiden (Guī Mèi). "Without blame. The hindrance is past, deliverance has come. Recuperate in peace and keep still. Few words are needed." The right thing the moment a great difficulty is overcome: not another exertion, but rest and quiet.

The reading. You don't perform surgery on a wound the same hour you finally close it. When the storm breaks, ship the fix and send everyone home — the wrong turns keep, and Thursday's post-mortem is kinder and truer than tonight's.

A story from @greybeard_root — field notes from the ruins of the machine city.
Department: IT ()
Next story: The New Hire Who Asked Why