Run the standup at 9:00 for each person, not at 9:00 for you
Pick a local send hour, one digest channel, and a rule for overlapping hours. Do not pick a Zoom time and call the stragglers async.
A "9am standup" is a time zone opinion. Take a team in Austin, Berlin, and Dubai. In summer, 9:00 in Austin is 16:00 in Berlin and 18:00 in Dubai. In winter Dubai slides to 19:00, because Dubai has no daylight saving. Someone is eating dinner. Someone just opened the laptop. Someone already did four hours of work and now has to recap it on camera.
Async only works if the prompt arrives at a local hour and the manager reads a digest, not a live roll call. We built Standup Smith around this pattern. You can steal the pattern without us. The bot just removes the spreadsheet.
Step 1: name the overlap you actually have
Write three columns: name, zone, and the hours they will answer a DM. Not "working hours." Answering hours. A parent who works 13:00 to 21:00 should not get a 9:00 local DM.
Pick one send hour per person in their zone. In Standup Smith that hour is set per member. A common setup:
- Americas: 9:00 local
- Europe: 9:30 local
- Gulf: 10:00 local
Do not chase a single UTC time. The digest is the thing that is single, not the prompt.
Step 2: pick one channel that is not the firehose
#eng-standup, not #engineering. The firehose channel will bury the thread under CI noise. The digest needs a quiet room. On Slack, that is a dedicated public channel. On Teams (Business and Scale), a dedicated Teams channel.
Post nothing else there. If you start dropping deploy notes into the standup channel, people mute it, and the standup has failed.
Step 3: freeze the questions for 20 working days
Use the default three (finished, next, blocked) or the split-weekend wording if UAE or KSA weekends are in play. Do not tweak daily. Twenty working days is long enough to see if people answer in two sentences.
Standup Smith caps you at three questions. Other bots let you add more. Adding more is how you recreate the Zoom.
Step 4: decide who reads, and when
The manager should read the digest 2 hours after the last local send hour, when the second ping has fired. On a team that spans Dubai to Austin, the last send is 9:00 in Austin, so the read is about 11:00 Austin time. Block 15 minutes. Read blockers first. Comment in the thread only on blockers, not on "looks good."
If you comment on every cheerful update, people start writing for you instead of for the work.
Step 5: chase blockers on a timer, not on memory
Write the owner and the person you wait on into the answer. "Blocked on API" is useless. "Blocked on Chris for the staging token" is a task.
On Standup Smith Business and Scale, the bot DMs the person who reported the blocker the next working day, and every working day after, until it is marked resolved. If you run this by hand, set a reminder to ping Chris on his next working morning in Chris's zone. Do not remind yourself at your 9:00. That is how Gulf blockers rot over a US weekend.
Step 6: skip days and real weekends
The US rests Saturday and Sunday. The UAE federal government rests Saturday and Sunday, and private employers set their own rest days, so some still use Friday and Saturday. KSA rests Friday and Saturday. If your bot has one weekend setting, people on the other weekend get DMs on their day off and nothing on one of their working days.
Standup Smith Business and Scale attach a country calendar per member: US, UK, UAE, or KSA. Public holidays become skip days. Annual leave is a skip range the person or manager sets. Free and Team do not include those calendars, so you enter skips by hand.
When you still get on a call
Use a live call when any of these is true:
- Three or more blockers name the same deploy or incident.
- Two people describe opposite facts about the same system.
- A new hire in week one still has not had the 20 minutes they asked for.
Cap that call at 15 minutes. The agenda is the digest, not "let's just go around." People in the zone where it is 21:00 can skip the call and read the thread. You cannot have both "we are async" and "everyone must attend."
A 12-person, 3-zone example
Backend in Austin (6), platform in Berlin (3), a data engineer in Dubai (1), and two contractors in Lisbon. Send hours: 9:00 America/Chicago, 9:30 Europe/Berlin, 10:00 Asia/Dubai, 9:30 Europe/Lisbon. Digest channel: #squad-checkin. The manager in Austin reads at 11:00 local, after every zone has answered. Blockers reported in Berlin get followed up the next European morning, not at 11:00 in Austin.
That is the whole design. Fancy dashboards do not fix a prompt that arrived at 2am.
Founding members
Founding members get 30% off regular prices for as long as they stay subscribed. 30-day money-back guarantee once the product opens. No card needed to join.
No public date yet. Founding members get the invite first, by email, before anyone else.