A 25-person engineering team spread across four time zones replaced the daily standup nobody could schedule. A Slack bot collects async updates each morning, OpenAI compiles the digest, flags blockers, and leadership reads the whole picture by 9:30.
Typical results
9:30
Digest posted daily, every zone heard
0
Standup meetings, was 5 a week
31 hrs/wk
Engineer time reclaimed
2 hrs
To surface a blocker, was a day
Figures reflect typical results for this kind of automation.
The challenge
With engineers from California to Eastern Europe, there was no standup time that wasn't someone's midnight. The team tried rotating meetings and a written channel nobody read; blockers surfaced a day late or in DMs, leadership had no daily picture, and five weekly meetings burned over thirty engineer-hours while still missing half the team.
Before and after
Standup meetings per week
−100%Minutes per engineer per day
−87%Time to surface a blocker
−92%The automation
We built a Slack bot that prompts each engineer at 8:45 their local time with three quick questions — yesterday, today, blockers. As answers roll in across time zones, OpenAI compiles a team digest grouped by project, highlights blockers and cross-team dependencies, and tags the person who can unblock each one. By 9:30 the digest posts to the team channel, with a condensed leadership version and a weekly trends summary for planning.
How it works
- 01
Bot asks at local morning
Each engineer gets a Slack prompt at 8:45 their time — yesterday, today, blockers. Two minutes to answer.
- 02
Updates roll in across zones
Responses collect in one thread as each time zone wakes up.
- 03
OpenAI writes the digest
Work is grouped by project, with blockers and cross-team dependencies highlighted.
- 04
Blockers escalate instantly
Anything marked blocking tags the person who can unblock it, right away.
- 05
Leadership gets the picture
A condensed digest posts by 9:30, plus a weekly trends summary for planning.
Starts from
- Morning Slack prompts
- Updates from 4 time zones
Delivers
- Team digest by 9:30
- Blocker escalations
- Leadership digest
The impact
The standup meeting is gone — five a week became zero — and updates now take each engineer two minutes instead of fifteen. Blockers surface within two hours instead of a day, over thirty engineer-hours a week came back, and leadership finally reads one clear digest covering all four time zones.
Questions about this automation
How does the bot handle different time zones?
Each engineer is prompted at 8:45 in their own local time with three questions: what they did yesterday, what they plan today and what is blocking them. Answers collect in one thread as each time zone starts its day, and the digest is posted at a set time each morning.
What does the OpenAI digest include?
The digest groups updates by project, highlights blockers and cross-team dependencies, and notes who has not replied. A condensed version goes to leadership, and a weekly summary shows recurring blockers and trends for planning. The summary works only from what engineers wrote, and the original answers stay linked for anyone who wants detail.
What happens when someone reports a blocker?
Any update marked as blocking is picked up right away instead of waiting for the digest. The bot tags the person who can unblock it, based on the project or system mentioned, and posts the context in the thread. Blockers that stay open carry into the next day's digest so they are not forgotten.