The async standup that actually saves time.
Most teams that "switch to async standups" end up with a slower version of the meeting they were trying to escape. Here is the format that actually returns the time.
The two failure modes
Failure mode one: a wall of text nobody reads. Failure mode two: a thread of "any questions?" replies that recreate the original meeting. Both happen because async needs structure, not a chat channel and a hope.
The format that works
A shared posting cutoff (10am local). One post per person with three sections: yesterday (max 3 bullets), today (max 3 bullets), blockers (one line or none). Reactions only — questions move to the relevant ticket, not the standup thread. Reading time per person: under two minutes.
When video helps
Some updates are easier to show than describe — a confusing UI, a half-finished design, a flaky build. A 60-second screen recording embedded in the post replaces a paragraph and is faster to consume.
What to do about real blockers
Blockers escalate to a real conversation, not a thread reply. The standup post is the trigger; the resolution happens in DM or on a call. The standup itself stays short.
Frequently asked
What about teams in three timezones?
Two posting cutoffs, one per major timezone cluster. Read across both each morning.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free