Timezone Coordination is whether you plan around other people's working hours rather than your own by default. It is the quietest of the four habits — nobody notices it going well, and when it goes badly, the resulting missed handoff usually gets blamed on one of the other three instead.
The Habit That Hides Behind the Other Three
A missed handoff caused by bad timezone planning tends to get diagnosed as a different problem — poor async handover, because the question arrived too late to answer in writing; or slow escalation, because the response took a full day. The actual cause, a request sent without accounting for when the recipient's day starts, often goes unexamined.
That misattribution is part of why this habit is easy to underinvest in relative to its actual cost — the damage shows up wearing another habit's name.
What Weak Timezone Coordination Looks Like
It rarely looks like carelessness. More often it looks like planning that defaults to the sender's own clock — a meeting proposed at a convenient time without checking what that means for a colleague eight hours away, a same-day request sent as that colleague's working day is ending rather than starting.
None of it looks deliberate. It looks like someone simply not having built the habit of checking a clock other than their own before sending.
Coordination Isn't the Same as Personal Sacrifice
A common misread treats this habit as personally absorbing the coordination cost — working unusual hours to match a colleague's schedule. That is one possible response, but the habit itself is really about planning and message timing: sending a request early enough that a same-day answer is actually possible, or explicitly flagging when a reply can wait.
The skill is accounting for the gap, not eliminating it by personal sacrifice.
Reading a Timezone Coordination Score in Context
Timezone Coordination pairs most usefully with Escalation Speed, since both concern the cost of delay across working-hour gaps — one from the perspective of asking in time, the other of planning in time. A low score on both points at the same underlying pattern: not tracking when someone else's working day actually is.
The Distributed Work Habits test scores Timezone Coordination out of twelve chances, one of four independently reported facets with no combined total — a low result here is a specific, addressable habit, not a verdict on someone's overall fit for remote work.