A one-hour meeting with six people costs six hours of work, not one. When that math repeats several times a day, a team spends its workday talking about the work instead of doing it. Pomodoro for remote work promised to free us from this, but plenty of teams fell into the opposite trap: replicating every hallway conversation as a video call, until the calendar became a wall of blue blocks with no gap left to think. The way out isn't tighter meeting discipline; it's needing far fewer of them.
The missing piece is almost always the same: learning to work asynchronously. It isn't an organizational trick but a change in how information flows through the team. And when it works, meetings stop being the operating system of the day and go back to being what they should be—the exception.
Synchronous vs. asynchronous: the distinction that changes everything
Synchronous communication requires two or more people to be present at the same time: a call, a video conference, a message waiting on an immediate reply. Asynchronous communication doesn't: someone writes now, another person reads and answers whenever it suits them, with nobody forced to stop what they were doing.
The difference seems trivial and isn't. Every synchronous interruption fragments the attention of whoever receives it. The researcher Cal Newport popularized the term Deep Work for the uninterrupted improve concentration that produces genuinely valuable output; constant meetings are exactly what makes it impossible. A team that reacts in real time to every question doesn't move forward—it only responds.
The principle adopted by companies like GitLab and Basecamp boils down to one phrase: default to async. The question is no longer "should we have a meeting?" but "does this actually need a meeting, or can it be settled in writing without anyone stopping?" Most of the time, the honest answer is the second one.
Writing well is the remote team's core skill
On a co-located team, poor communication gets patched with proximity: you walk over to someone's desk and clear up the misunderstanding in thirty seconds. Remotely, that patch doesn't exist, and the quality of what you write becomes the quality of how the whole team works.
Writing well here doesn't mean elegant prose. It means thinking about the message from the reader's side, since they can't turn around and ask you:
- Give the full context up front. A useful async message doesn't need a back-and-forth to be understood. Explain the what, the why, and what you expect to happen next—all in the first send.
- Be explicit about what you're asking. "What do you think?" opens an endless thread. "Do you approve this version, or do you want changes? If I don't hear back by Thursday, I'll proceed" closes the loop.
- Structure it to be read fast. Headings, lists, the important thing on top. Whoever receives it shouldn't have to dig to find the decision that's theirs to make.
Amazon is famous for having replaced slide presentations with six-page memos read in silence at the start of each meeting. The reason is exactly this: writing out a complete argument forces you to actually think it through, while a series of bullets lets you hide half-baked ideas.
Documenting decisions: a single source of truth
The silent enemy of a remote team is knowledge that lives only inside someone's head or buried in a chat from three weeks ago. When a decision isn't written down anywhere stable, it gets relitigated again and again, and each person remembers a different version of what was agreed.
The fix is to have a single source of truth: a known place where the current version of everything important lives. Not the chat, where everything sinks beneath the scroll, but a document or a wiki anyone can consult without having to ask.
Chat is for talking; documentation is for remembering. Confusing the two is why remote teams keep relitigating the same discussions without moving forward.
It's worth documenting at least three things:
- Decisions and their reasons. Not just what was decided, but why. Six months from now, someone will ask why this path was chosen, and "because we just talked it through on a call" won't cut it.
- Recurring processes. How a release ships, how a new hire is onboarded, how time off is requested. Writing it down once spares you from answering the same thing fifty times.
- Project status. A place to see where each thing stands without having to schedule a check-in meeting to find out.
Response expectations and time zones
The most common fear about working async is being cut off: if nobody answers instantly, how does anything move? The answer is paradoxical—what kills productivity isn't the waiting, but the expectation of immediacy. If the whole team assumes every message deserves a reply within five minutes, nobody can concentrate on anything, because everyone is watching the inbox just in case.
The agreement that frees a team is explicit: regular messaging is not urgent. A reply within a few hours (or the next day, when there's a time difference) is perfectly fine. For what genuinely can't wait, there's a separate, agreed-upon channel—a call, a notice flagged as urgent—which keeps its force precisely because it's rare.
When the team is spread across time zones, this discipline stops being a luxury and becomes mandatory. If your teammate is asleep while you work, you have no alternative but to leave her the full context in writing. The few hours of overlap are reserved for what truly needs to be synchronous; the rest of the day, everyone moves forward on what's already documented.
Which meetings are actually worth it
Working async doesn't mean never seeing each other. It means saving shared time for what text does badly. Some things still call for a live conversation:
- The ambiguous or sensitive. A hard conversation, a conflict, a decision loaded with emotional nuance are better resolved by talking than by writing.
- Real brainstorming. Generating raw ideas and building on each other's in the moment benefits from real time—though it's wise to close with a document capturing what was agreed.
- The human relationship. A team that never sees each other's faces turns cold. An unstructured stretch of plain conversation sustains the trust the rest of the async work takes for granted.
The practical rule: a meeting needs a decision to make or a conversation that genuinely requires voices, not just "catching up." For catching up, there's documentation. Tools like Pomodomate help protect the focus blocks that async work makes possible—the very gaps that constant meetings used to devour.
Frequently Asked Questions
Doesn't everything get slower if nobody answers instantly?
It's the opposite of how it looks. What slows down is the individual reply to a single message; what speeds up is the real work, because each person gets long blocks of concentration instead of a day diced up by interruptions. A project moves further on four uninterrupted hours of focus than on those same four hours split into twelve pieces by messages that "couldn't wait."
How do I start if my team is hooked on meetings?
With something concrete and small. Pick one recurring meeting and turn it into a written update for a couple of weeks. If nobody misses the meeting—and they almost never do—you've got the evidence to propose the change elsewhere. The habit comes apart one meeting at a time, not by general decree.
Doesn't async work isolate people?
It isolates if the only thing you remove is contact and you put nothing in its place. That's why healthy remote teams reserve deliberate space for the social: unstructured time, an in-person gathering once a year, channels for talking about things that aren't work. Human connection has to be designed on purpose, not left to emerge on its own the way it did in the office.
Does this work for a small team or only for large companies?
It works, and often more so. A small team has less room to lose hours in avoidable meetings, so the savings show up sooner. And with fewer people to coordinate, building the habit of documenting and answering without urgency is easier than in an organization of hundreds with ingrained customs.
