How We Run Async by Default

The default setting for most teams is synchronous: when something needs to happen, someone calls a meeting. When a decision needs to be made, everyone gathers in a room (or a Zoom) and talks until there’s an answer.

We don’t operate that way. Not because meetings are inherently bad, but because the default of synchronous communication creates a specific set of problems that compound at scale — even at the five-person scale we deliberately stay at.

What Async Actually Means

Async doesn’t mean slow. It means the default mode of communication is written and non-blocking. Someone shares context; the recipient responds when they have the attention to respond well, not when a calendar notification fires.

The practical implication: almost every discussion that isn’t time-sensitive lives in a written thread. Decisions get documented in a shared space before they’re executed. Status updates are written, not recited in standups.

Real-time communication is reserved for things that genuinely benefit from it: working sessions where two people need to think together in real time, calls where tone and nuance matter, and the occasional moment where a quick five-minute voice conversation is faster than twenty messages.

How Decisions Get Made

The pattern we use for consequential decisions:

1. One person writes a short brief — the context, the options they see, the trade-offs, and their recommendation. Usually half a page.
2. The brief circulates for a fixed window (often 24–48 hours). Everyone reads and responds in writing.
3. If there’s rough consensus, the decision is made and recorded. If there’s real disagreement, a short call is scheduled — but only then.

The brief format forces the person proposing the decision to think it through before asking others to engage. The written responses mean everyone can review the reasoning later, not just the people who happened to be online when the discussion peaked.

The Written Default Changes Thinking

When you’re required to write your thoughts down before sharing them, you produce better thoughts. The act of writing forces specificity: you can’t gesture vaguely at an idea in a document the way you can in conversation.

This has a side effect that took us a while to name: it shifts accountability. When a decision is written down, with the reasoning visible, the person who proposed it is accountable for the reasoning — not just the outcome. That creates a culture where proposals are genuinely thought through, not floated casually.

What We Still Do Synchronously

Some things don’t translate well to async:

• Kickoffs. Starting a new engagement benefits from a real conversation where everyone can ask questions, align on tone, and establish a working relationship.
• Retros. Reflecting on what went wrong (and what went right) is more honest when people can respond to each other in real time.
• Anything involving emotional stakes. If someone is frustrated or a relationship needs repair, text is the wrong medium.

The goal isn’t to eliminate real-time communication. It’s to not make it the default — to only use it when it’s genuinely the right tool.

The Scale Implication

Running async by default doesn’t just make a five-person team more productive. It means the team can stay five people. When communication infrastructure doesn’t depend on everyone being available at the same time, you don’t need coordinators and schedulers and project managers whose job is to ensure the right people are in the room.

The information flows without the meetings. The decisions get made without the overhead. That’s not a productivity hack — it’s a structural choice that shapes the kind of team you become.