Async by default: designing a team that doesn’t need to be in the room

There is a version of distributed work that looks modern and feels exactly like the office you left. The calendar is still a wall of meetings. They just happen over video now. Decisions still wait for the next sync. People still spend the day reacting to pings, on call and available, their real work squeezed into whatever gaps are left. The location changed. The dependency did not.

That dependency is the thing worth looking at hard. When a team can only move in shared real time, when nothing gets settled until everyone is in the room together, you have not built an autonomous team. You have built the same team that happens to own laptops. Real autonomy needs something more structural underneath it: work that can keep moving even when half the people are asleep, off for the day, or simply heads-down on something else.

Live time is the most expensive thing you own

A meeting is never really one hour. It is one hour times everyone in the room, plus the damage it does on either side of itself. A day chopped into thirty-minute pieces by standing calls leaves almost no runway for the kind of long, unbroken concentration that hard work actually requires. That cost almost never shows up anywhere you can point to, which is exactly why it grows unchecked for years.

The discipline of async work is really just one question, asked honestly before every meeting. Does this genuinely need us in the same place at the same time? A surprising amount of what we reflexively schedule does not. Status updates, information sharing, most decisions that already have a clear owner: none of that needs a live call. It needs a written thing and somewhere to respond. Save real-time conversation for the moments that truly earn it. The tense disagreement. The messy early creative work. The occasional talk that only works with a human voice attached.

A meeting is never one hour. It is one hour times everyone in the room, plus the damage it does on either side of itself.

Writing is the engine, not the paperwork

Async teams run on writing, and the ones that struggle with async almost always struggle with writing first. When a decision lives in a document instead of in someone’s memory of a call, three genuinely useful things happen at once. People who missed the moment can still act on it. The reasoning is visible, not just the verdict. And the team builds a record it can actually go back to, instead of relitigating the same question every few weeks like it is brand new.

Yes, this feels slower at first, and in the narrowest sense it is. Writing a clear proposal takes longer than saying it out loud in a room. But it quietly replaces something far more expensive: the meeting to get aligned, the follow-up to clear up confusion, the second meeting because the first one did not stick. Writing front-loads the effort into a shape that keeps paying you back long after.

What default actually means

The phrase that carries the weight here is async by default, not async at all costs. The goal was never to abolish live conversation, which would be its own kind of broken. The goal is to flip which one you reach for first. Instead of defaulting to a meeting and occasionally writing something down, you default to writing something down and occasionally call a meeting. The exceptions still exist. They just have to make a case for themselves now.

Get that flip right and autonomy stops being a slogan on a careers page and becomes a property of how the place runs. People can do focused work without asking permission. They can make progress without waiting on anyone. They can shape the day around when they actually think well, instead of around a window everyone once agreed to sit in. The room is still there when you need it. You just stop needing it for everything.