Run Async Standups
Your team's daily standup eats the first productive hour: timezone gymnastics, late joiners, and fifteen minutes of status that could have been a message. Async standups move the ritual to writing — everyone posts their update, everyone reads on their own schedule. Done right, the team stays aligned and mornings stay yours.
TL;DR / Quick Fix
Quick fix: replace the live standup with a written update in your team chat — each person posts yesterday's progress, today's plan, and blockers by a set time, using a fixed template. The lead reads and unblocks in minutes. Keep live meetings only for blockers that truly need discussion.
Follow these steps
- Pick one channel and one deadline. Standup updates live in a single thread or channel, posted by a fixed time each morning. One place, one rhythm — scattered updates across DMs defeat the purpose.
- Use the three-question template. Yesterday, today, blockers — the classic format works because it is scannable. Keep each answer to a line or two; the readable agenda template discipline applies to updates too.
- Make blockers the star. The update's real value is surfacing what is stuck. Teach the team that 'no blockers' is fine but hiding blockers is not — the lead's job is clearing them, not collecting statuses.
- The lead responds in writing. Read the thread, acknowledge blockers, and assign help — all in the channel. Visible responses prove the updates are read, which is what keeps people posting them.
- Keep a weekly live touchpoint. Async handles status; it does not replace human connection. One short live call a week preserves the team feel that pure writing slowly erodes.
- Measure mornings, not messages. Success is calendar time returned, not update volume. If the calendar still fills with replacement meetings, the standup was not the real problem.
What to avoid
- Do not let updates become essays. Three lines each is the target — long updates do not get read, and unread updates kill the ritual.
- Do not run async standups in DMs. Private updates hide blockers from the people who could help — the channel is the point.
- Do not keep the live standup 'just in case'. Running both doubles the cost; commit to async and keep live time for real discussion.
- Do not skip timezones in the deadline. 'By 10am' means nothing across zones — set the deadline in each person's local morning explicitly.
Frequently asked questions
What if people stop posting updates?
Usually because nobody reads them visibly. The lead's daily written response is the engine — no response, no ritual, within two weeks.
Do async standups work for big teams?
Better than live ones do — a 20-person live standup is a lecture, while a written thread scales fine. Split threads by squad past a dozen people.
How is this different from just chatting?
The fixed template and deadline turn chat into a ritual. Without them it degrades into random messages nobody tracks.