The short version
- Follow the sun means work passes between teams in different time zones so it continues through a 24 hour cycle without anyone working nights.
- It depends entirely on the handoff. Every shift change is a point where context can be lost, and the losses compound.
- It works well for bounded, interruptible work such as support tickets. It works badly for work needing continuous judgement.
- Teams of five to fifty usually cannot afford the redundancy it needs. Partial follow the sun, for one workstream, is often the right size.
The definition
Follow the sun is an arrangement where work moves between teams in different time zones so that it progresses continuously without anyone working outside their normal hours. A team in Europe finishes and hands to a team in the Americas, who hand to Asia Pacific, who hand back to Europe the next morning.
The promise is a full day of progress on something, every day, on ordinary shifts. The cost is one handoff per shift change, and the handoff is where the whole model lives or dies.
It originated in large support and service organisations, where it fits naturally: tickets are discrete, self describing, and interruptible by design. Most of the trouble comes from applying it to work that is none of those things.
Where it works and where it does not
| Work type | Fit | Why |
|---|---|---|
| Support tickets | Good | Discrete, documented, designed to be picked up by anyone |
| Incident response | Good | Genuinely needs 24 hour cover, and the alternative is paging people at night |
| Alert triage queues | Good | Bounded decisions against written criteria |
| Feature development | Poor | Needs continuous judgement. Each shift re reads the other's work. |
| Design and research | Poor | Output is a shifting understanding, which does not transfer in a note |
The pattern is clear. Follow the sun suits work where the state can be fully written down. Where the state is partly in someone's head, every handoff loses some of it, and three handoffs a day loses a lot. See where follow the sun loses context.
What a handoff has to carry
A follow the sun handoff is not a summary of the shift. It has to let someone continue without asking, which is a much higher bar. Four fields.
- Where it stands. The current state, not what was done. "Auth is failing on refresh only, reproduced, cause not yet found."
- What has been ruled out. The field that saves the most time and is most often missing. Without it, the next shift repeats the last shift's investigation.
- Open questions with names. What is unresolved and who could answer it, so the next shift knows what they may decide themselves.
- Next action. One specific thing, so the next shift starts working rather than starts orienting.
The second field is the difference between a model that compounds progress and one that circles. There is a fuller version in the end of day handoff template.
Why it strains teams of five to fifty
Three reasons, and they are structural rather than cultural.
It needs redundancy you do not have. True follow the sun means every skill exists in every zone. A team of twenty with one person who understands billing cannot hand billing work around the clock, whatever the schedule says.
The handoff overhead is fixed. Fifteen minutes of writing and reading per shift change, three times a day, is a real cost. On a large operation it is a fraction of throughput. On a small one it is a meaningful share of the day.
The failure is quiet. When a handoff is thin, the next shift does not stop. They make reasonable assumptions and carry on, and the divergence only shows up days later in rework. Nobody reports it as a handoff problem.
Partial follow the sun
The version that works at this size is narrow. Pick one workstream where the state can genuinely be written down, usually support or incident triage, and run it round the clock. Leave everything else on ordinary single zone ownership with a good daily handoff.
That gives most of the benefit, which is that customers and incidents are covered, without asking a small team to maintain duplicate expertise everywhere.
What makes even the narrow version work is that the handoff carries the state honestly. This is what StandIn is built for. At the end of a shift a person spends about ninety seconds on a brief: what moved, what is open, what is blocked, what is next, mostly drafted from the work itself. The incoming shift can then ask questions and get answers from that brief, in the writer's words, with a source under each one. It never guesses, and when something was not covered it says so and names who to ask, rather than producing a plausible summary of a shift it did not observe. The next shift knows what was ruled out, and knows what is genuinely unknown. See working across time zones and follow the sun without 24 hour availability.
Common Questions
How many time zones does it need?
Three roughly eight hours apart for full coverage. Two gives extended coverage rather than continuous, which is often enough and much cheaper.
Does it actually make things faster?
For queue based work, yes, because response time is the measure and the queue never sleeps. For project work it frequently makes things slower once rework from thin handoffs is counted.
Do the shifts need an overlap?
Thirty minutes helps a great deal and is not always affordable. Where there is no overlap, the written handoff has to do the entire job, which makes the "ruled out" field mandatory rather than nice to have.
Is this the same as a global on call rotation?
Related but not the same. On call is about responding to interruptions in your own zone's night. Follow the sun is about continuing work in someone else's day. A team can have one without the other.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.