Skip to main content
Culture

[FAKE] How we run async standups and retrospectives

2 min read

The meeting problem

A 15-minute standup with 8 people is 2 hours of collective time. Every day. That's 10 hours per week spent saying "no blockers" into a screen. We decided there had to be a better way.

Our async standup format

Every morning, each team member posts in a dedicated Slack channel using a simple template:

  • Yesterday: What shipped or moved forward
  • Today: What's the focus
  • Blockers: Anything slowing you down (tag someone if you need help)

The thread format means people read at their own pace, respond to blockers immediately, and skip the ceremony of "unmute, talk, mute."

Async retrospectives that work

Retros are harder to make async, but we've found a rhythm:

Week 1-3: Collect

A shared board (we use Notion) stays open all sprint. Anyone can add cards to three columns: "Went well", "Could improve", "Ideas." Adding in real-time means you capture moments when they're fresh, not two weeks later.

Week 4: Discuss & vote

Everyone gets 5 votes to distribute across improvement items. The top 3 become action items for the next sprint. One person writes a summary and posts it in Slack.

Monthly: Sync retro

Once a month, we do a synchronous retro. This is for the bigger topics that benefit from live discussion — team dynamics, process overhauls, strategic alignment.

Why this works

  • Introverts contribute more: Written format removes the pressure of speaking up in meetings
  • Time zone friendly: Everyone participates on their own schedule
  • Better records: Everything is documented automatically
  • Less fatigue: Fewer meetings means more deep work time

The tools

We use a simple Slack bot that posts the standup prompt at 9am in each member's local timezone. Responses are threaded and we have a dashboard that flags missed updates (not for surveillance — for catching people who might be stuck).

Tags

Team Ops Automation