null route queen / network lab / operations notes

Write It for the Future You

Operational ticket notes should function like packet captures for human events: what happened, when it happened, who participated, what changed, and what happened next.

The lesson

During after-hours incidents, document what actually happened — not what you later assume happened.

A missed call is not a conversation.
A voicemail is not confirmation.
A message sent is not acknowledgement.
A conversation on the 11th is not a conversation on the 8th.

Capture these explicitly

Example

Bad:

Contacted Andrew.

Better:

09/08 03:14 — Called Andrew; no answer. Voicemail left requesting callback.

Then later:

09/11 10:22 — Spoke with Andrew. Reviewed incident and confirmed follow-up action.

Why this matters

Weeks later, the ticket should tell the story without requiring reconstruction from Teams, Zoom, phone history, email, or memory.

Treat operational notes like a packet capture:what happened, when it happened, who participated, what changed, and what happened next.

Future You should be able to replay the incident from the notes.

← Back to Operations Notes