Async Is the Real Remote Skill. Most 'Remote' Companies Just Moved the Meetings to Zoom.

"Remote" was never the productivity unlock. Written, asynchronous communication was. The location was always a red herring, and the companies that confused the two ended up with the worst of both worlds: the isolation of working alone plus the interruption of working in an open-plan office, now piped through a webcam.

Here's what most people get wrong. They think the gain comes from skipping the commute and working in pajamas. It doesn't. The gain comes from a specific habit almost no remote team actually builds: defaulting to a written message instead of a live call. Skip that habit and "remote" just means you took the meeting-heavy office and bolted a camera onto it. Microsoft's own data says the average knowledge worker is now interrupted every two minutes during core hours by a meeting, email, or ping. That is not remote work. That is the office, transmitted.

What's the actual difference between asynchronous work and remote work?

Remote is a location. Async is a communication protocol. They get bundled together because they often arrive at the same company on the same day, but they are not the same thing, and only one of them produces the focus everyone was promised.

Remote answers the question "where do you sit." Async answers the question "do I have to interrupt you to get this done." A team can be fully remote and 100% synchronous, living inside back-to-back video calls. A team can also be fully co-located and async, leaving each other documents and recorded walkthroughs instead of tapping shoulders. The productivity research keeps pointing at the second variable, not the first.

When Microsoft studied 61,182 of its own employees after a forced shift to remote, the workers naturally moved toward asynchronous channels, email and messaging, and away from real-time conversation. Total meeting time even fell about 5%. That is the key tell. Remote did not force more meetings. Left to default human behavior, it nudged people toward async. The meeting explosion everyone complains about was a choice layered on top, not a law of remote physics.

Why did "going remote" make the meetings worse, not better?

Because companies ported the office's synchronous reflex straight onto Zoom and Teams without questioning it. The shoulder-tap became a calendar invite. The "quick sync" became a recurring 30-minute block. The hallway conversation became a meeting because nobody had been taught to write the thing down instead.

The numbers are blunt. For the average Microsoft Teams user, the number of weekly meetings rose 153% since February 2020, and double-booked, overlapping meetings climbed 46% per person in a single year. People are so checked out inside these calls that 42% multitask by sending an email or a ping while the meeting runs. A meeting that 42% of attendees are ignoring is not collaboration. It is a status-anxiety ritual.

And the day keeps fragmenting. Microsoft's 2025 data found that 57% of meetings are ad hoc calls with no calendar invite at all, and after-hours meetings past 8 p.m. are up 16% year over year. This is what "moving the meetings to Zoom" actually produces: not fewer interruptions, but interruptions with no walls, no end time, and no commute to escape them.

How async-first is a genuinely remote company, really?

Genuinely async companies look nothing like the median "remote" employer, and the gap is enormous. They write first, talk second, and they treat a live call as the expensive exception rather than the default.

At Doist, the company behind Todoist, 80 to 90% of all internal communication happens asynchronously, in writing. The company describes itself, plainly, as "writing first." That is the benchmark. Not "we have Slack." Not "we record some meetings." Eighty to ninety percent of everything, written down, on purpose, so the work can move without two people being awake at the same minute.

Now compare that to what's actually out there. Buffer surveyed 3,000 remote workers and found that 74% work across multiple time zones, the exact structural condition that demands async, yet only 29% want a mostly-async setup. Most distributed teams have the time-zone spread that makes synchronous coordination physically painful, and most still default to live calls anyway. The need for async far outruns the adoption of it. That gap is the whole problem in one statistic.

Dimension	"Remote" (sync-default)	Async-first
Default channel	Live video call	Written doc or recorded video
Internal comms in writing	A minority	80–90% at Doist
Weekly meeting load	Up 153% since 2020	Meeting is the exception
Time-zone handling	Everyone joins at 9am someone's-time	Hand off work, no overlap needed
Reported productivity	Fragmented, interrupted every 2 min	42% report increased productivity at GitLab

What does written-first actually buy you in hours?

It buys back the single scarcest resource in knowledge work: uninterrupted time to think. And unlike most workplace advice, the hours are measurable.

Atlassian studied 5,000 knowledge workers and found that in organizations with poor meeting cultures, people spend 50% more time in unnecessary meetings than making progress on their actual top priorities. Worse, 65% of those workers prioritize answering messages quickly over doing the high-value work, the responsiveness trap that async is supposed to kill. The fix isn't subtle. When 43% of Atlassians swapped a single meeting for an async Loom video over two weeks, it freed up 5,000 hours of focus time. One meeting, replaced by a recording, across a fraction of the company, recovered thousands of hours nobody had before.

GitLab, which runs a documentation-first model and publishes a public handbook of thousands of pages, found that 42% of its survey respondents reported increased productivity and 81% said they were satisfied with their productivity working remotely. The report names documentation and transparency, not the location, as the core best practices. The output tracks the writing, not the working-from-home.

This is also why async is quietly becoming a load-bearing soft skill rather than a nice-to-have. Writing a crisp update that needs no follow-up call is a skill. Recording a two-minute walkthrough instead of booking a meeting is a skill. They are learnable, they are rare, and they compound.

What does this look like in a real message?

The difference between sync-default and async-first shows up in something as small as how you ask a coworker for input. One version forces a meeting. The other makes the meeting unnecessary.

Weak (sync-default, forces a live call): "Hey, can you hop on a quick call to talk through the Q3 plan? Got some questions on your section. When are you free this afternoon?"

Strong (async-first, resolves without a meeting): "Reviewed your Q3 section, left three comments inline. The only blocker is the budget line on slide 4, it conflicts with the number finance sent Tuesday (linked). If you reconcile those two, I think we're done, no call needed. If you'd rather talk it through, here's a 90-second Loom of exactly where I'm stuck."

The weak version offloads the thinking onto a future meeting and onto the other person's calendar. The strong version does the work up front in writing, isolates the one real decision, and makes the live call optional instead of mandatory. The second message costs you ten more minutes to write. It saves both of you a thirty-minute call and the context-switch tax on either side of it.

That's the entire async edge in miniature. You front-load clarity in writing so nobody has to be interrupted to deliver it.

Who does async-first leave out? (The part nobody mentions.)

Here's where the async evangelists go quiet. Async is not a free, universal upgrade, and pretending it is gets people hurt.

First, written-first communication penalizes whoever writes slowly or writes in a second language. A culture where status flows through clear writing rewards the strong writer and quietly disadvantages the person whose ideas are great but whose prose is slow. That's a real equity cost, even if the English-fluency premium is smaller than people fear. If you're building an async team, you have to coach writing, not just assume it.

Second, async can curdle into isolation. The same Microsoft study of its 61,182 employees found a darker number underneath the meeting drop: time spent collaborating across groups fell roughly 25% versus pre-pandemic levels. Networks calcified into silos. Async done badly means the weak-tie connections that actually help your career and surface new opportunities quietly starve. You have to manufacture the loose contact that the office used to hand you for free.

Third, async is genuinely worse for a narrow set of things: real-time crisis response, high-emotion conversations, brainstorming that feeds on interruption, and onboarding a brand-new hire who doesn't yet know what to even write down. The honest rule is not "never meet." It's "meet on purpose, for the things meetings are actually good at, and write down everything else."

And fourth, the career risk. If your manager is sync-default and you go heads-down async, you can vanish from the promotion conversation because the people deciding only register the colleagues they see and hear. Async protects your focus. It does not, by itself, protect your visibility. You have to manage that separately and deliberately.

Is async-first where work is actually heading?

Yes, structurally, even if culture is dragging its feet. The same forces pushing the four-day week into knowledge work, output measured over hours-in-seat, are pushing toward async, because async is what makes output-based work legible in the first place.

The economics keep nudging in this direction too. When remote pay gets localized against you, the only durable defense is being demonstrably, measurably productive from anywhere, and async written work is the thing that makes your contribution visible across time zones without you having to sit in a 6 a.m. call to prove it. The teams that win the next decade won't be the ones that "went remote." They'll be the ones that learned to write.

What to do now

1. Audit your own meeting load for one week. Count how many meetings could have been a comment thread, a shared doc, or a two-minute recording. Atlassian's 5,000-hour result came from swapping just one meeting for a Loom. Find your version of that meeting and kill it.
2. Default your next three updates to writing. Before booking a call, write the thing down. Isolate the one decision that actually needs a human. Most of the time you'll find there isn't one.
3. Build the async muscle deliberately. Write updates that need no follow-up. Record short walkthroughs. This is a learnable, rare, increasingly hard skill, and it shows up on your resume as "drives clarity across distributed teams."
4. Protect your visibility separately. Async safeguards your focus, not your standing. Schedule the small number of live touchpoints that keep you in the room where decisions, and promotions, get made.
5. Pressure-test the job before you take it. In interviews, ask how the team actually communicates. "Mostly async, written-first" and "we have a lot of syncs" describe two completely different lives. Don't confuse the company's remote policy with its real protocol.

Trying to figure out whether a "remote" role is actually async or just the office on Zoom, or how to frame your distributed-work skills so they land on a resume? Message Praxy on WhatsApp. We'll read the job's real communication culture, sharpen how you describe your async wins, and rehearse the questions that reveal which kind of remote you're really walking into.