It is 7 p.m. in Amsterdam. Alex has one task left before he can ship: a single question only Sarah can answer. Is the old export format still supported, or did last month's change quietly drop it? He writes it out, sends it to Tokyo, and glances at the clock.
In Tokyo it is 2 a.m. Sarah is asleep. His question is already sitting in a queue she will not open for hours.
The wait nobody scheduled
Alex does the reasonable thing. He picks up something else. But the shippable task is now parked, and part of his attention stays parked with it. He is not blocked in a way anyone would log. He is just waiting, quietly, on a person in another time zone.
His teammates do the same thing to each other all day. A question to an engineer in Berlin, a question to someone in San Francisco, each one landing when the other side is out. The team feels busy and slow at the same time, and no one can quite point to why.
The question itself is small. Sarah could answer it in one sentence. She wrote the change; she knows the answer cold. The problem is not difficulty. It is that the only copy of the answer is inside a person who is nine hours behind and fast asleep.
Morning in Tokyo, evening gone in Amsterdam
Sarah wakes, sees the message, and replies before her coffee. For her it is a thirty-second task. But it is now 9 a.m. in Tokyo and midnight in Amsterdam. Alex is offline. Her answer lands in an empty room and waits again.
Count the hours. Alex sent his question at 7 p.m. He reads the reply the next morning, close to fourteen hours later. Two people, both fast, both willing. One tiny question. Most of a day gone, and neither of them did anything wrong.
Why it keeps happening
This is not a story about a slow teammate. It is a story about where the answer lives. When the only way to get it is to reach the person who holds it, every time-zone gap becomes a delay, and every delay stacks on the next. Ask one follow-up and the same overnight wait starts over from the top. A two-message exchange, the kind that takes five minutes in a shared room, can burn two full days across a nine-hour gap.
The wait is invisible on any dashboard. No ticket says waiting for Tokyo to wake up. It just shows up later as work that took a week when the actual thinking took a minute. Nobody is to blame, so nobody fixes it, and the pattern repeats with the next question and the next.
You can feel it in the small habits it creates. People batch their questions to avoid the overnight loop, then guess when they cannot wait, then quietly redo the work when the guess turns out wrong. The gap does not just slow things down. It pushes careful people into cutting corners.
Closing the gap
The fix is not to make Sarah wake up earlier. It is to let the answer live somewhere that does not sleep. If what Sarah already knew were written down in a place Alex could ask, he would have had his one sentence at 7 p.m., and shipped before dinner.
That is what StandIn does. Sarah writes one short brief at the end of her day. While she is off, it answers questions like Alex's from what she wrote, in her words, with a source under the answer, and it says so when something is not on record. The question stops sitting through the night. It gets answered while its owner sleeps.
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.