The handoff.
A 90-second pager exchange that said almost nothing — and didn't need to.
Lede
The handoff between oncall shifts used to take twenty minutes and a phone call. Last Tuesday it took ninety seconds and one Watch buzz. The system did the rest.
A clean handoff is not a meeting. It is the moment the night's events stop being someone's problem to remember.
What arrived
At 06:48 the outgoing oncall received a soft tap. It was not a page. It was a summary — three lines, machine-drafted from the night's events:
- Two acknowledged spikes, both auto-resolved
- One config diff queued for review
- Zero unresolved threads
What was said
The outgoing replied with a single message in the shared room: “Quiet night. Read the diff before you merge it.” That was the entire handoff.
A good handoff should fit in a sentence. A great one should not need to be said.
On what wasn't said
There was no list of things to watch. There was no thirty-minute walk-through of dashboards. There was no post-it on the laptop that read “remember to ack the third spike if it hits before noon.” None of it was needed because none of it had been left half-finished. The night had already been closed before the handoff began. The Watch buzz wasn't a transfer of obligation — it was a receipt.
What the incoming heard
The incoming oncall acknowledged at 06:50. By 07:05 they had read the diff, signed off, and were on a walk. At 09:00 the diff merged itself with their approval baked in.
The silence
The thing about a handoff like this is what it is not. It is not a Zoom call. It is not a forty-line email. It is not a ritual that someone has to perform in order to pretend the system is being looked after. It is one tap, one sentence, and trust that the rest is already written.