The remote work world has split into two camps: "meetings are evil" and "we need more face time." Both are wrong. The real answer is knowing which communication needs synchronous interaction and which doesn't.
The decision framework
Ask yourself two questions about any recurring meeting:
- Does it require real-time discussion? (brainstorming, conflict resolution, complex decision-making)
- Or is it primarily information sharing? (status updates, progress reports, announcements)
If it's information sharing, it should be async. If it requires real-time back-and-forth, keep it synchronous.
What should be async
- Daily standups – Status updates don't need everyone in the same room at the same time
- Weekly progress reports – Record a 3-minute video, let AI summarise it
- Project updates to stakeholders – They can watch on their own schedule
- Sprint reviews – Team members walk through what they shipped, viewers watch when convenient
- Onboarding updates – New hires share their progress without interrupting the team
What should stay synchronous
- 1-on-1s – These need emotional nuance and real-time rapport
- Brainstorming sessions – Ideas build on each other in real time
- Incident response – Urgency requires immediate coordination
- Conflict resolution – Tone matters, and async can amplify misunderstandings
- Strategic planning – Complex decisions benefit from live debate
The hybrid sweet spot
Most teams land on a hybrid approach:
- Async by default – Record video updates, share written briefs, use threaded comments for follow-ups
- Sync when needed – Schedule live meetings only when the topic genuinely requires real-time interaction
- Clear escalation – If an async thread gets complex, anyone can say "let's hop on a call" without guilt
This typically reduces meeting load by 40–60% while improving the quality of the meetings that remain.
The hidden benefit: better documentation
When status updates happen via recorded video, you get an automatic archive. AI extracts action items, flags blockers, and tracks sentiment. Six months later, you can search "database migration" and find exactly who said what and when.
Live meetings don't give you that – unless someone takes meticulous notes, which nobody does consistently.
Making the switch
Start by auditing your team's recurring meetings. For each one, ask: "Could this be a recorded video update instead?" If the answer is yes, try it for two weeks and see what happens.
The goal isn't zero meetings. It's the right meetings.