Handing work between regions without losing it
Follow-the-sun promises continuous progress and usually delivers a daily re-orientation tax that nobody counted.
Work passed between regions each day should mean progress around the clock. In practice it frequently means each region spends its first hour working out what the last one did, and the piece of work moves more slowly than if one team had kept it. For broader context on planning work across time zones, Timeanddate Meeting Planner is a useful reference.
The difference is entirely in the handover.
The handover is a written artefact, not a status
A ticket updated to 'in progress' is not a handover. The receiving region needs the state of the work and the state of the thinking, and the second is what gets omitted.
- What was completed, specifically enough to verify.
- What is in progress and how far.
- What was tried and did not work — this is the item that saves the most time and is left out most often.
- The next intended step, and why.
- Anything blocked, and who was asked.
Without them the next region repeats the same failed approach. Across a week of handovers this can consume more time than the work itself.
Do not hand over mid-thought
Not every task should cross a handover boundary. A piece of work requiring sustained context is usually finished faster by one person over two days than by three people over one. For a practical software-side reference on handoffs and competing workstreams, this guide adds useful detail.
The practical rule is to keep exploratory or design work within a region and hand over work with a well-defined next step. Deciding this at planning time, rather than at the end of a day, is what makes follow-the-sun work at all.
Overlap the handover if you possibly can
Thirty minutes of live overlap at the boundary is worth a great deal — enough for the incoming region to ask the two questions the written handover did not anticipate.
Where the zones do not allow it, the substitute is a short recorded walkthrough. Less good, considerably better than text alone for anything with visual or structural complexity.
One place, one format
Handovers scattered across chat threads, tickets and email are handovers that get missed. One location, one template, always.
The template matters more than it seems: a fixed shape means the receiver knows where to look for the blocked item without reading the whole thing, and the writer does not have to decide what to include at the end of a tiring day.
Watch for the region that always receives the mess
Over time, one region often ends up consistently receiving half-finished work with poor handovers, and its own work suffers. This is rarely deliberate and it is corrosive.
Reviewing handover quality periodically — and treating a poor handover as a real defect rather than a minor discourtesy — is what keeps the arrangement equitable. Where one direction is consistently worse, it is a workload problem at the sending end, not an attitude problem at the receiving one.