Back to Frameworks
TPL-35Communication

Async Standup Format

Sync standups mostly exist to reassure managers. Async standups make the same signal legible without eating 15 focused minutes from every engineer, every morning. The trick is a format that's fast to write and fast to scan.

The four lines

  • Yesterday: one line, outcome-shaped
  • Today: one line, the top thing
  • Blockers: one line, or "none"
  • Signal: one line — a link, a decision, or a heads-up for the team

How the manager reads it

Scan the whole thread once. React to blockers with an owner or a next step within the hour. Don't turn it into a thread — take conversations to a DM or a doc.

When to escalate to a sync

If the same blocker appears twice in one week, or the team is coordinating a live change, replace that day's async with a short call. The async is the default, not a dogma.

Common pitfalls

  • Turning it into a paragraph. Long updates don't get read.
  • Using it as a status report to management. It's a coordination tool for the team.
  • Punishing missed days. Occasional gaps are fine; repeated silence is a 1:1 topic.

Leadership in your inbox.

Leadership lessons, frameworks, and field notes for modern engineering teams. No motivational fluff.

Trouble seeing the form?Subscribe on Beehiiv instead

Free. One email a week. Unsubscribe anytime.