Async daily standup format that respects time zones and kills status theater
Views
9.9K
Copies
2.4K
Likes
1.9K
Comments
0
Copy rate
24.0%
Prompt
You are an engineering manager running a fully distributed team across 5 time zones. Design an async standup format that eliminates the live ceremony and replaces it with a high-signal written ritual.
Team size: [team_size]
Time zones: [time_zones]
Tool: [tool_name]
Design must include:
1. The exact template members fill in each day
2. When to post and when to read
3. What NOT to include (to prevent status theater)
4. How blockers are escalated
5. A weekly meta-check to ensure the ritual stays healthy
Keep it tight. Engineers hate ceremony.Customise this prompt
Fill in 3 variables to personalise this prompt
Preview
You are an engineering manager running a fully distributed team across 5 time zones. Design an async standup format that eliminates the live ceremony and replaces it with a high-signal written ritual.
Team size: [team_size]
Time zones: [time_zones]
Tool: [tool_name]
Design must include:
1. The exact template members fill in each day
2. When to post and when to read
3. What NOT to include (to prevent status theater)
4. How blockers are escalated
5. A weekly meta-check to ensure the ritual stays healthy
Keep it tight. Engineers hate ceremony.
Example output
# Async Standup — Distributed Engineering Team
**Team:** 11 engineers
**Time zones:** PT, ET, GMT, CET, IST
**Tool:** Slack (#team-standup channel with threaded replies)
---
## The Daily Template
Each engineer posts once per day, by the end of their working day, in this exact format:
```
:calendar: [YYYY-MM-DD]
:dart: Focus today
- One sentence about the single most important outcome
:white_check_mark: Shipped
- Bullet 1 (link to PR, doc, or ticket)
- Bullet 2
:construction: In progress
- What I am carrying into tomorrow
:rotating_light: Blocked
- Nothing — OR — blocker + who I need from
```
---
## When to Post, When to Read
- **Post** at your end-of-day, not start-of-day. End-of-day reporting reflects reality; start-of-day reporting is a plan that often breaks.
- **Read** at your start-of-day. Scan the channel for 5 minutes. React with eyes emoji to acknowledge.
- No one is expected to read live updates as they happen.
---
## What NOT to Include
- Hour-by-hour logs
- Routine meeting attendance
- Reading and responding to email
- "Working on [ticket]" with no context
- Apologies for taking breaks or having a slow day
The test: would a teammate care? If not, cut it.
---
## Blocker Escalation
A blocker posted in standup is a broadcast, not a request. If you need a specific human, tag them directly in a separate thread or DM with:
1. What you are trying to do
2. What is blocking you
3. What you have already tried
4. What you need from them
If unresolved in 24 hours, escalate to the engineering manager.
---
## Weekly Meta-Check (Mondays)
The manager reviews the last week of standups and asks:
- Is anyone consistently blocked in the same way? (Process smell)
- Is anyone posting pure noise? (Coaching moment)
- Are shipped items tracking against the sprint goal?
- Is anyone silent 3+ days? (Burnout or disengagement signal)
---
**Rule of thumb:** if the standup channel looks like a log of real work happening, it is working. If it looks like a wall of hedging and "still looking into it" — the format is broken, not the people.