Run an Asynchronous Distributed Standup
Design a lightweight standup that gathers meaningful progress and blockers across time zones without creating another noisy status feed.
The brief
Understand the problem
Background
A daily video standup can be unfair to distributed teams, but replacing it with unstructured posts makes blockers hard to notice and updates tedious to scan. Teams need a useful rhythm that respects local schedules.
User context
Jon's six-person team works across Kuala Lumpur, Berlin, and Toronto. He needs a clear view of delivery risk before his workday ends without asking Toronto teammates to post at dawn.
Product problem
Team members need flexible response windows while the lead needs a concise, accountable view of blockers, handoffs, and missing updates.
Objective
Create the daily response, team digest, blocker handoff, and late-update states for an asynchronous standup.
What to design
Define the experience
Required experience
- Submit progress, next focus, and blockers in a local response window
- Scan a digest organized around action rather than chronology
- Assign or accept help on a blocker
- Catch up after an absence without filling past reports
Screens and states
- Personal standup prompt
- Team digest
- Blocker detail
- Late or absent update state
Core user flow
Follow the critical path
- 01
Jon schedules one shared standup cycle with local reminders for each region
- 02
Team members post concise updates and link relevant work
- 03
The digest groups two related blockers and highlights a required handoff
- 04
A Toronto teammate accepts the handoff when their day begins
- 05
Jon sees the ownership change without sending a separate status request
Product rules
Requirements and constraints
Requirements
- Show deadlines and reminder times in each member's local time zone
- Allow a member to mark leave, no material change, or a sensitive update
- Prioritize blockers, decisions, and cross-time-zone handoffs in the digest
- Keep comments attached to the relevant update across daily cycles
- Avoid rewarding posting time, update length, or uninterrupted attendance
Constraints
- No member should be expected to respond outside their stated work hours
- Private blockers must have a restricted handoff path
- The exercise covers one team and one daily cycle, not workforce monitoring
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens showing submission, digest review, and an accepted blocker handoff
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.