You can run a daily standup without a meeting if the team is clear about the purpose: surface blockers, maintain awareness, and coordinate work. The meeting is not the point; the information flow is.
Why the daily standup meeting often fails
Live standups fail when they become status reports, run too long, or interrupt deep work for updates that did not need a live conversation.
For distributed teams, the cost is higher. Someone is always joining too early, too late, or outside their best working hours.
What async standup looks like
An async standup is a short written check-in submitted by each teammate on their own schedule. The team reads updates in a shared feed and follows up on blockers directly.
ScrumTool's async standup tool adds configurable questions, submit links, blocker tracking, and AI digests for teams that want the signal without the meeting.
The three questions that actually matter
The classic questions still work: what did you finish, what are you doing next, and what is blocked? The key is to ask for useful information, not performative detail.
A good update names specific work and specific blockers. "Working on API" is weak. "Finishing payment webhook retries; blocked on test Stripe account access" is useful.
How to handle blockers asynchronously
Blockers need an owner and a follow-up path. If someone marks a blocker, the Scrum Master or responsible teammate should respond in the team's normal communication tool.
Async does not mean passive. It means the live meeting is removed while accountability remains.
Setting up your async standup in ScrumTool
- Create a standup config.
- Set your questions and schedule expectations.
- Share the submit link with your team.
- Review the feed daily and generate an AI digest when needed.
What to do when people don't submit
First, reduce friction. Make the link easy to find and the form short. Second, make it clear that updates are read and blockers are acted on.
If nobody reads the standup feed, people will stop submitting. The loop only works when the team sees that useful updates change what happens next.
For the format tradeoffs, read Async Standups vs Live Standups.