I counted my meetings last Tuesday. Seven. The actual decisions that came out of those seven meetings? Two. The rest were status updates that could have been a Slack post, a brainstorm that needed a whiteboard and got a grid of webcam faces instead, and one meeting that existed purely because it was on the calendar from three months ago and nobody had canceled it. If you've worked remotely for more than six months, this math feels familiar. The question isn't whether your team communicates enough. It's whether you're using the right mode for what you're actually trying to accomplish.
The real cost of defaulting to meetings
A study analyzing remote engineering teams found that a 60-person team wastes approximately $66,000 per employee per year on inefficient meeting culture when you factor in direct costs, context switching, and lost focused work time. That number sounds abstract until you do the personal math. If you're in three unnecessary meetings a day, that's roughly 7.5 hours a week, almost an entire workday, spent in conversations that didn't need to happen in real time.
For parents working remotely, those hours aren't just unproductive. They're irreplaceable. A meeting scheduled over your only deep-work window between school drop-off and the 11 AM standup doesn't just waste time. It eliminates the only block in your day where you could have done the work that actually moves your projects forward.
Stanford's research on video call fatigue identified four specific reasons Zoom meetings drain cognitive resources: excessive close-up eye contact, the stress of seeing your own face, reduced physical mobility, and the heightened cognitive load of processing nonverbal cues through a screen. Women reported significantly higher fatigue levels than men. These aren't minor annoyances. They're physiological costs that accumulate across every unnecessary synchronous meeting on your calendar.
Async-first isn't about fewer conversations
The companies doing remote communication well in 2025 and 2026 have mostly landed on the same principle: default to async, escalate to sync when needed. Research from GitLab found that teams with strong documentation practices experienced 67% fewer blocking delays compared to teams that relied primarily on real-time communication. Not because they talked less, but because they wrote things down.
Async-first means your default reaction to "I need to tell the team something" is a written message or a short recorded video, not a calendar invite. It means decisions get documented in a channel or a project tool, not trapped in a meeting that four people attended and six people missed. It means the person in a different time zone, or the parent who was at a doctor's appointment during the 2 PM sync, can get the same information and contribute the same input without having been physically present for the conversation.
What async-first looks like in practice:
- Status updates go in a shared channel, written or as a two-minute Loom recording
- Decisions are proposed in writing, with a deadline for input (e.g., "respond by Thursday if you have concerns")
- Meeting agendas are shared 24 hours in advance so attendees can flag items that could be handled async instead
- Recurring meetings get audited monthly: if the last three had no real-time decisions, cancel them
The parent advantage nobody mentions
Here's something that rarely makes it into the productivity content about async communication: it's disproportionately beneficial for parents and caregivers. Not as a perk. As a structural accommodation for the reality that your workday isn't a continuous eight-hour block.
When communication is async by default, you choose when to engage. The message your colleague sent at 10 AM sits in the channel until you get back from the pediatrician at 11:30. The project update that went out at 3 PM is there when you sit down after bedtime. Nobody is penalized for not being online at the exact moment information was shared, because the system was designed around the assumption that people aren't always available simultaneously.
The Owl Labs survey found that nearly 7 in 10 Gen Z and Millennial workers prefer "microshifting," breaking their day into non-linear blocks that fit around other responsibilities. Async communication makes microshifting possible. Sync-heavy cultures make it impossible, because if you miss the meeting, you miss the conversation, and there's no record of what was decided.
When sync is genuinely the right call
Async isn't always better. Some conversations need to happen live, and pretending otherwise creates its own problems.
Use synchronous communication (a call, a video meeting, even a phone call) when:
- The topic is sensitive, involves conflict, or carries emotional weight. Tone matters here, and text doesn't carry tone.
- You've exchanged more than four or five messages on a topic without resolution. If the thread is getting longer, the medium is wrong.
- You're brainstorming or building on each other's ideas in real time. Async brainstorming tends to produce parallel thinking rather than collaborative thinking.
- You're onboarding someone or teaching a new process. Screensharing with live Q&A beats any written walkthrough for learning speed.
- The relationship needs investment. Trust between remote colleagues requires some live interaction, particularly early in a working relationship or after a period of absence.
The Buffer data shows that loneliness and disconnection remain top struggles for remote workers year after year. Async solves for efficiency. Sync solves for connection. You need both, and the skill is knowing which one a given moment calls for.
A decision framework that fits on a sticky note
Before creating a meeting or typing a long message, ask two questions. First: does this need a real-time response, or can people engage on their own schedule? If it can wait, it's async. Second: does this need nuance, tone, or live collaboration? If yes, it's sync.
Most status updates, FYIs, and non-urgent questions are async. Most conflict resolution, complex brainstorms, and relationship conversations are sync. The gray area in between (quick questions, feedback requests, planning discussions) defaults to async unless it hasn't resolved after a few exchanges.
This week's move
Look at your calendar for next week. Pick one recurring meeting and ask yourself honestly: did this meeting produce a real-time decision in the last three weeks? If not, cancel it and replace it with a shared channel update. You'll get back 30 to 60 minutes, your team will get the same information, and the person who always misses that meeting because of a time zone or a pickup schedule will finally be included.