18 Jan 2026

Timezone collapse in a 14-person squad

Fourteen people, three offsets, one “send now” button. The person who clicks is usually the one who is still in the office in BST. The recipient may be eating dinner in Eastern Time or still in yesterday in Auckland. Collapse is not a metaphor. It is a queue that used the wrong civil clock.

Our drill is unkind on purpose. We take a real onboarding sequence, freeze the copy, and only allow changes to hold rules. Learners must name the recipient offset, not the Slack channel’s offset. If they cannot, the send is delayed until they can — including in the exercise, which makes ambitious people restless. Restlessness is useful data.

A pattern that keeps appearing: Scottish customers of a US-founded product receiving 23:00 mail because California thought 15:00 was polite. The fix is not “add a delay of eight hours.” The fix is a hold until the recipient’s next desk band, with incident traffic exempted on a written list.

We do not pretend a four-week Cross-Timezone Cadence programme finishes an exception form. Several Edinburgh teams booked a Pulse Audit afterwards. That is a better outcome than a certificate that implies the clocks are done.

If your squad is smaller than fourteen, the drill still holds. Two people in mixed offsets can ruin a morning. Notification Timing Optimization is the name we put on refusing that ruin as a default.