Async Standup English: Writing Clear Status Updates
5 exercises — reporting progress, describing blockers, setting today's intentions, flagging dependencies, and writing help requests in async standups.
0 / 5 completed
1 / 5
Which async standup message BEST reports yesterday's progress?
Progress reporting in async standups should name the specific task, link the deliverable (PR number), and include a measurable outcome if available. Option B gives: what was done, the PR number for traceability, and a concrete result (3× query reduction). This lets teammates know the PR is ready to review without asking separately.
2 / 5
Which message BEST describes a blocker in an async standup?
Async blocker messages need: the 🚫 label for skimmability, what exactly is blocked, the specific error (so someone can help immediately), where you've asked for help, who can unblock, and impact on timeline. Option A provides all of these. 'Will figure it out' in B means no one knows to help you.
3 / 5
Which is the BEST 'Today' section of an async standup?
'Today' section: List specific tasks with expected time/ETA where relevant, mention who you are collaborating with, and include any synchronous touchpoints (calls/meetings). Option B gives a numbered list, time estimates, task names, and a cross-team dependency — everything a teammate or manager needs to understand your day.
4 / 5
You are waiting on another team to merge their API changes before you can complete your integration. Which async standup entry BEST flags this dependency?
Dependency flagging: Name the team, the specific item (PR number), and the downstream impact (mobile release date). Option A does this and explicitly says 'critical path' and 'risk' — the language that triggers management attention. Vague dependency mentions get ignored in async channels.
5 / 5
You need help from a teammate with a complex TypeScript generic type error you have been stuck on for 2 hours. Which help request is MOST effective in an async standup?
Help requests should: use a help signal (🙋), state how long you've been stuck (signals genuine effort), name the specific error, link the code, estimate the time needed, and tag a specific person who might know. Option B does all of this. Tagging a specific person (not 'anyone') dramatically increases response rate.