Async First: How We Cut Meeting Time by 60% Without Losing Alignment

In the spring of 2024, we tracked where our engineering team’s time went for four weeks. Meetings accounted for 31% of the average engineer’s week — over 12 hours. Of that time, roughly half was informational: updates, status reports, and announcements that could have been a well-written document.

The Default Audit

The first step was auditing every recurring meeting. For each meeting, we asked: what would happen if this meeting didn’t exist? For most informational meetings, the answer was: nothing bad. The information would need another channel — a written update, a shared document, a recorded walkthrough — but the decisions and progress wouldn’t be blocked.

What We Kept Synchronous

Decisions with significant tradeoffs that benefit from real-time discussion. Relationship-building conversations. Complex technical debates where written communication creates more confusion than it resolves. Crisis response. These are the legitimate uses of synchronous time. They’re a smaller fraction of most engineering team’s meeting load than people assume.

The Tooling Investment

Async-first communication requires better tooling than synchronous communication. Loom for asynchronous video walkthroughs. Well-structured documentation in a shared wiki. Threaded discussion in Slack with clear norms about response time expectations. The tooling investment is modest; the discipline investment is significant — async communication requires more written clarity than verbal communication can get away with.