Async-First Beats More Meetings
A year into remote work, teams are trading video-call fatigue for Notion docs, Slack huddles, and Loom clips instead of piling on more Zoom.
We’re now more than a year into this remote-work experiment, and one pattern is impossible to ignore: the companies that seem to be handling it best aren’t the ones scheduling more meetings, they’re the ones scheduling fewer. The instinct early on was understandable — nobody’s in the office, so let’s just… video-call our way through it. Stand-ups became Zoom stand-ups. Planning sessions became hour-long screen-share marathons. And somewhere around month nine, everyone hit a wall.
Video-call fatigue is real, and it’s not just anecdotal grumbling. Spring surveys this year keep landing on the same conclusion: people are exhausted by synchronous video, and teams are actively looking for ways to communicate without requiring everyone to be staring at a camera at the same time. That’s where “async-first” comes in, and it’s quietly become one of the more interesting shifts in how software teams operate.
What async-first actually looks like
It’s not one tool, it’s a philosophy backed by a few specific ones. Notion has become the default home for the kind of documentation that used to live in someone’s head and get repeated in five different meetings — decisions, specs, project status, all written once and referenced instead of re-explained. Slack’s push into huddles is a nice middle ground: lightweight, low-ceremony voice chat that doesn’t require a calendar invite, so you can hop in for two minutes instead of blocking out thirty. And Loom has turned into the async stand-up’s best friend — instead of gathering six people to watch someone share their screen live, you record a five-minute walkthrough and people watch it on their own time, at 1.5x if they want.
The appeal here isn’t subtle. A meeting forces everyone into the same time zone and the same headspace at the same moment, whether or not that’s actually necessary for the task at hand. Most status updates don’t need that. Most “quick syncs” don’t either. What they need is clear written communication and a recording people can reference later — which, frankly, is often better documentation than a meeting produces anyway, since nobody’s taking notes in a meeting the way a Notion doc forces you to write things down.
None of this means meetings are going away entirely. Some things — sensitive conversations, complex brainstorming, anything with real disagreement to work through — genuinely benefit from real-time back-and-forth. The shift is about being more deliberate: defaulting to async and reserving synchronous time for when it actually earns its place on the calendar.
What makes this moment particularly interesting is that it’s happening right as companies start sketching hybrid-office plans for later this year. If async-first habits stick, they could end up shaping hybrid work more than the office layout does — because a lot of what makes async work well (clear written updates, recorded walkthroughs, less “let’s hop on a call”) doesn’t care whether you’re at a desk or on your couch. The tools built over the past year might outlast the circumstances that produced them.