The Async-First Stack: How Sean Got His Evenings Back
Async-first is a culture decision, not a tool decision. The tools only work after the culture is established.
The Before State
Two years ago: 14 recurring weekly meetings plus ad-hoc requests. Available 7am to 8pm. Evenings effectively on-call. Sean audited his calendar for three months in 2023 to categorize each meeting. Result: 9 of 14 recurring meetings were status updates, reviews, and one-directional information sharing. All nine were candidates for async replacement.
The Tool Changes
Loom replaced 5 recurring meetings. A structured weekly written update replaced 3 more. Linear comment threads replaced 1. The remaining 5 meetings are conversations that genuinely benefit from real-time interaction. From 14 weekly meetings to 5 — the tools made this possible. But the tools were not the root cause of the change.
The Culture Change That Enabled the Tools
The tools did not work before one specific change: Sean explicitly communicated that async responses within 24 hours were acceptable and expected — that nobody should expect faster responses outside of emergencies. Until that expectation was set, people sent follow-up messages asking why their Loom had not been watched. The tools create infrastructure for async communication. The expectation creates permission to actually use it.
The Outcome
5 recurring weekly meetings instead of 14. Calendar blocks focus time from 9am to 12pm daily. Evenings are no longer work time except by choice. The tools did not produce this outcome. The decision to change the communication culture produced it. Loom, Linear, and Notion made the new culture sustainable.