Delivering Across Time Zones Without Losing a Day

The default is a lost day

Without a plan, distributed work settles into a rhythm where every question costs a day. Someone asks in the evening, the answer arrives while they sleep, and the follow-up question starts the cycle again.

Two or three of those in a row and a two-hour task has taken a week.

What we changed

• Ask completely. A question goes out with the context, what was already tried, and the two options — so the answer can be a decision instead of a clarification.
• Write the decision down. Anything agreed in the overlap window gets three lines in the ticket before anyone logs off. Chat history is not a record.
• Protect the overlap. The hours everyone shares are for the things that genuinely need everyone. Status updates are not one of them.
• Hand off deliberately. End of day means a short note on state, blockers and what the next person can pick up — not an empty branch and good luck.

What we did not change

We did not ask anyone to work someone else's hours. A team quietly resentful at 11pm does not produce better software, and the arrangement never survives more than a quarter.

The result worth reporting

Review turnaround went from just under two days to under six hours, and almost none of that came from people being faster. It came from questions that no longer needed a second round trip.