Async Doesn’t Break Anything. It Just Stops Hiding What Was Already Broken.

Nobody asked the obvious question at the time. How did this person become CEO without ever producing a written strategy? Like, at all? The answer to that question is exactly what async work actually does—and why it terrifies a very specific kind of successful person.

His CTO sent a late-night Slack after month four: “14 strategy meetings, zero documented outcomes. We can’t operate like this.” Brutal. Also correct. Eleven months later the company was gone, $1.8M unspent, a graveyard of verbal commitments nobody could reference because nobody had written them down.

This isn’t a cautionary tale about one bad CEO. I’ve watched this exact pattern across four different companies in three years. Different industries, different team sizes, same collapse point. And every time, the post-mortem blamed “async adoption challenges” or “communication tool friction.” Both explanations are wrong. Politely, professionally wrong.

What Changed. And What Didn’t.

Async didn’t make that CEO less capable. It revealed he’d never been capable in the way everyone assumed. That’s an important distinction, and most companies get it backwards.

Office culture measures presence. Async measures artifacts. That’s the whole shift. Everything else—the tools, the frameworks, the async manifestos—is downstream of that one measurement change.

Neither is morally superior. Seriously—I’ll say that plainly because a lot of async evangelism skips past it. But for distributed teams, artifacts matter more than presence. Not philosophically. Practically. You can’t reference a conversation that happened in a room across three time zones. You can reference a document. That’s it.

Where Things Actually Stand in 2026

Before going further—how widespread is this shift? Because some people still treat async-first as an edge case for remote-native startups. It isn’t anymore.

That 68% number is worth pausing on. The dominant narrative is that remote workers struggle with isolation. The data says the actual pain point is collaboration—which almost always means: not enough artifacts, unclear decisions, no way to know what was actually agreed.

Async doesn’t solve that automatically. Bad async creates its own mess. But the companies getting it right are seeing the 18% outperformance. The ones getting it wrong are creating documentation theater that nobody reads.

The Real Pattern: Who Struggles and Why

I’ve watched this across four company transitions. The same profile keeps appearing. It’s not the quietest people or the least experienced. It’s a very specific type of high-performer.

These aren’t stupid people. Not even close. They optimized for office-culture success metrics—verbal fluency, meeting presence, real-time synthesis—and those skills worked. For years. In some companies, for decades.

Async removes the performance layer. What’s left is output. And sometimes there isn’t much. That’s not a failure to adapt. It’s the exposure of a gap that never needed closing before.

But Writing Isn’t Everything. Don’t Get Smug About This.

Here’s where the async evangelists lose me—and lose a lot of converts along the way. The argument drifts from “distributed teams need artifacts” to “writing is the superior form of thinking.” Those are not the same claim, and conflating them is how you end up with a culture that rewards people who write beautifully and produce nothing.

Some brilliant thinkers are genuinely slow in text. Some fast writers produce polished nonsense. Strong facilitation—the kind that actually drives decisions—is a real skill that doesn’t fully translate to a written format. The goal isn’t more writing. It’s clearer output. Those aren’t the same thing.

Ask what your work actually requires. If you need to negotiate complex deals, body language and real-time reading matter. If you need rapid ideation, a whiteboard session beats three rounds of written RFC. If you need crisis response, async review cycles don’t work—full stop. Don’t async your incident response. I’ve seen it happen. It’s a disaster.

Async Has Its Own Pathologies. Let’s Name Them.

Async work is not morally superior. It has different failure modes—and if you’re managing a transition, you need to know these as well as you know the failure modes of office culture. Because they’re just as real and just as expensive.

• 📄Documentation theater. Beautiful RFCs that nobody implements. Notion wikis that grow and rot. The appearance of process without the substance of it. I’ve seen companies with 400-page strategy documents and no shared understanding of priorities.
• ⏳Decision paralysis from endless written deliberation. Synchronous decisions have natural forcing functions—someone in the room eventually says “okay let’s move.” Async discussions can spin for weeks if nobody owns the decision explicitly.
• 🔇Loss of serendipitous collaboration. The hallway conversation that changes a product direction. The lunch where two people realize their projects are blocked by the same thing. That stuff doesn’t happen in async by default. You have to design for it deliberately.
• 🛡️“Cover your ass” writing instead of clear thinking. When writing becomes the measurement system, some people optimize for writing that makes them look thorough rather than writing that helps the team move. Different incentive, same dysfunction as performative meeting attendance.
• 🪄People who write well but execute poorly. The flip side of the verbal performer is the written performer. Switching measurement systems doesn’t fix the underlying problem—it just changes who games it.

You can optimize for looking productive in async just like in meetings. The pathology changes. The possibility of pathology doesn’t.

What Actually Works: Meet People Where They Are

The hospital case is the one I keep coming back to, because it illustrates the real insight here. Not “make everyone write” but “produce artifacts that distributed teams can use.”

A hospital implemented written shift handoffs. Physicians resisted hard. “I can verbally explain patient status in two minutes versus fifteen minutes to write it.” Reasonable objection. Written handoffs also demonstrably reduce error rates, but the friction was real.

Adoption Without Dictation Software

Then they added dictation software with structured templates. Doctors verbalized into voice-to-text. Templates gave rambling a shape. Six weeks later:

Adoption With Dictation + Templates

Same outcome requirement. Radically different path to get there. The doctors didn’t need to rewire how they think—they needed the artifact to exist. Format didn’t matter. The output did.

The tools that help most aren’t the ones that demand cognitive rewiring. They’re the ones that capture what people already do naturally:

The Question Nobody Wants to Ask

How many careers were built on presence rather than output?

In co-located offices, you can succeed—genuinely, sustainably succeed for years—by showing up, sounding confident, and facilitating discussions that lead nowhere. Those are real skills. They just don’t translate to distributed work. They never did. Offices were just kind enough not to check.

When companies go async and certain people struggle, the comfortable narrative is “they can’t adapt to new tools.” That narrative lets everyone off the hook—the individual, the company, the culture that rewarded the wrong things for a decade.

More honest: the company is now measuring something different. What it used to reward—presence, verbal fluency, meeting performance—no longer matters as much. What it now requires—artifacts, decision clarity, asynchronous communication—was never developed. That’s not a cognitive mismatch. That’s a skill gap that office culture made invisible.

The Part That Will Make People Uncomfortable

The people struggling loudest with async are often the ones who were overvalued in office culture.

Not because they’re incompetent. Because the skills that made them successful—verbal confidence, real-time synthesis, meeting presence—matter less in distributed work. And the skills distributed work requires were never part of their development. Nobody asked for them. Nobody measured them. Why would anyone build them?

When they struggle, it’s easy to frame it as “cognitive mismatch” or “can’t adapt to change.” That framing is comfortable for everyone and accurate for nobody.

Here’s what’s also true: there are people who were invisible in office culture who are thriving now. The engineer who thinks slowly and writes brilliantly. The analyst who never spoke loudly in meetings but produces the clearest decision memos anyone’s read. The product manager who couldn’t command a room but whose written specs ship to production without revision. They were there the whole time. The measurement system just couldn’t see them.

Async didn’t reveal who can think and who can’t. It revealed who built skills that match what distributed work actually requires—and who built them for a different game entirely.