Fewer meetings, deeper work, happier team. Async-first isn't just a policy — it's a culture shift that takes months to stick.
We went async-first 18 months ago. Our meeting count dropped by 60%. Engineer satisfaction went up. Output went up. Here's the full story.
What async-first actually means
It doesn't mean "no meetings." It means meetings are the last resort, not the default. Before scheduling a meeting, you ask: could this be a doc? A Loom? A comment thread? If yes, do that instead.
The hardest part: trust
Async communication requires trusting that people will respond, engage, and follow through without being in the room together. Building that trust takes time and consistent behaviour. The first two months were rocky. People reverted to Slack pings and "quick syncs."
We held firm. We celebrated good async communication in team retrospectives. Slowly, the culture shifted.
The tools that made it work
- Loom for video walkthroughs (a 3-minute Loom beats a 30-minute meeting for most demos)
- Linear for decisions embedded in issues (no separate decision doc, the context lives where the work lives)
- PMT for project visibility (no status meetings needed when the board is always up to date)
When to break the rule
Some conversations need to be synchronous: conflict resolution, major strategic pivots, anything emotionally charged. Async-first doesn't mean async-always. Know when to pick up the phone.