Standups across time zones

A live standup needs one meeting slot that works for everyone, which is exactly what a team spread across time zones does not have. An async standup replaces that slot with three clocks you set once: when the questions go out, how long people have to answer, and when the digest posts. Get those three right and the spread stops being a problem. Get them wrong and you have quietly built a 6:00 meeting for whoever sits furthest from HQ.

1Ask at everyone's own 9:00

Delivery should follow the person, not the office. 9:00 means 9:00 in Zagreb for the person in Zagreb and 9:00 in San Francisco for the person in San Francisco. A single company-clock time feels tidy on the settings page and taxes the edges of the map: someone is always answering before breakfast or at midnight, and people who are asked at a bad hour first answer badly, then stop answering.

This is a setting, not a habit. In asyncmate it is the default: the schedule says 9:00 and each participant's DM arrives at their local 9:00.

2Decide when the digest posts

Once answers arrive across a whole day, the digest has a timing question of its own. There are two reasonable answers, and which one you want depends on who reads it.

• Stream answers as they come. Each update lands in the channel when its author submits. The channel feels alive and overlapping time zones see each other's mornings in real time. The cost is that there is no single moment when "the standup" is readable as one document.
• Hold the digest for a fixed time. Answers collect quietly and one digest posts at, say, 9:00 in the team lead's timezone, with everything from the last cycle in it. One message, read once, with the whole picture.

If the team genuinely reads each other during the day, stream. If in practice one person reads the standup each morning and everyone else skims, fix the digest to that person's morning. asyncmate supports both, per check-in.

3Size the response window to the spread

A 30-minute response window works when everyone shares an office. Across ten time zones it guarantees that someone is asked while asleep and marked as missing before they wake up. The window has to cover every participant's working morning, which usually means leaving it open for most of a day and closing it before the digest posts.

Resist the urge to nag. Repeated pings do not raise response rates; they train people to ignore the bot. asyncmate sends one prompt per run and lets each person snooze it to a better moment; if the window closes without an answer, the digest simply says who is missing.

4Plan the handoff, not just the standup

With a gap of ten hours or more, a follow-up question asked in a thread dies overnight: by the time the author wakes up, the asker has gone home. Two habits keep work moving through the gap.

• Write for the reader who acts next. "Blocked on the staging certs, I need Maja to renew them before EU morning" hands someone a task. "Still blocked" hands them nothing.
• Add an end-of-day wrap where the handoff happens. A second, lighter check-in at the end of one cluster's day, asking what got done and what the next timezone should pick up, turns the overnight gap into a relay instead of a wall. The question sets page has a ready-made wrap set.

5When one standup should become two

An honest limit: if the team spans twelve hours and is really two clusters that do not share day-to-day work, one global standup produces a digest where half of every update is irrelevant to every reader. Split it. Run one standup per cluster, in each cluster's own rhythm, and let leads share a short weekly summary across them. A single worldwide ritual is only worth it while people actually read each other's answers.

Set it up: asyncmate delivers at each person's local time by default, and can hold the digest for a fixed hour in the timezone you choose. See how to run daily standups in Slack or create your first check-in. Free for up to 10 people who answer.