It takes approximately four minutes to double-check a timezone.
You read the message. You are not quite sure which CST is meant, or whether the person is accounting for the current DST offset, or whether "next Thursday" means the coming Thursday or the one after. You open a browser tab. You search. You compare the result against your calendar. You go back to the message, confirm it makes sense, and move on.
Four minutes. It does not feel like a problem.
But a distributed team of twenty people, each encountering two or three ambiguous time references per day, is spending somewhere between one hundred and sixty and two hundred and forty minutes per day on this task — collectively. Over a working year, that is between five hundred and seven hundred hours of combined productive time spent on a problem that is, at its root, a communication formatting issue.
This is before accounting for the cases where the check fails — where someone misreads the abbreviation, puts the wrong time in their calendar, and the error is only discovered when someone does not show up. The recovery cost for a missed meeting, a delayed deployment, or a misrouted support ticket is typically much higher than the cost of the original double-check.
Timezone anxiety is the low-grade cognitive background noise of distributed work. It is not dramatic enough to appear in productivity reports. It does not produce incidents with clear timestamps. It does not trigger postmortems. It accumulates invisibly in the small pauses between reading a message and acting on it.
The solution is not to ask people to be more precise — they are already trying. The solution is tooling that makes precision the default output of normal communication. When a time reference can be shared as a verified, unambiguous link rather than a raw abbreviation, the four-minute check becomes unnecessary.
Four minutes is not a large number. Multiplied across a distributed workforce, it is.