标签：#organizationalrealitymana

Async-first teams have correctly diagnosed the disease of meeting overload — and then prescribed a treatment that quietly kills something they didn't know they valued. Picture this: a senior engineer, somewhere in a distributed engineering org, opens their laptop on a Monday morning to find three Slack threads, two auto-generated recaps from the previous week's planning sessions, and a Confluence page summarizing a strategy discussion they weren't invited to. They read all of it in eleven minutes. They feel fully informed. They feel efficient. And they have absolutely no idea that the head of product spent the last forty minutes of that strategy call sounding resigned — not convinced — about the new roadmap direction. That engineer will build the wrong thing. Not because the summary was inaccurate. Because it was accurate. This is the efficiency trap: the belief that capturing the output of a conversation is equivalent to having been present for it. Teams increasingly act on this assumption, and the organizational cost is not yet showing up in any dashboard anyone is measuring. How We Got Here The backlash against meetings has genuine merit behind it. A 2012 work efficiency survey of 3,200 employees found that 47% of participants identified corporate meetings as the single leading time-wasting factor at work. About 15% of an average organization's time budget is spent in meetings, with middle management spending up to 35% of their time there and upper management approaching 50%. Those numbers are hard to defend when the actual decision could have lived in a three-paragraph document. Researchers have been calling for more intentional use of meetings and a reduction of unnecessary ones, partly in response to documented issues like Zoom fatigue and meeting overload. That's a reasonable prescription. The problem is that "fewer bad meetings" got operationally translated into "fewer meetings," full stop, with async tools — Slack, Loom, Notion, automated recap systems — ab

Async-first culture is making teams faster and lonelier — but the real damage isn't loneliness. It's that people stopped owning decisions they were never in the room to make. Picture a mid-sized software company, somewhere between Series B and exhaustion, that has gone fully async. No standups. No sprint reviews that anyone actually attends. A bot joins every Zoom, spits out a bulleted summary, drops it into Confluence, and everyone reads it — or doesn't — in their own time. The calendar is clean. The focus time is protected. And six months later, a major architectural decision made in a Loom video that half the engineering team never watched has quietly become the source of a simmering, passive-aggressive standoff between backend and platform. Nobody was in the room. Nobody feels they own it. This is the efficiency trap, and it's subtler than its critics usually admit. The problem isn't that async communication is bad. Much of what passes for a meeting in most organizations is theater: 77% of workers attend meetings that end in a decision to schedule yet another meeting, and 62% regularly sit through meetings that didn't even state a goal in the invite. Cutting that noise is not just reasonable — it's overdue. The real issue is what happens when the pendulum swings past optimization into avoidance, and teams start treating the absence of synchronous contact as a metric of operational maturity. Presence Isn't the Point — Participation Is There's a distinction the async evangelism wave has systematically glossed over: the difference between being informed and being part of something . A well-structured meeting summary tells you what was decided. It does not tell you that the decision was almost different, that someone pushed back and was overruled, or that the VP's sudden hedge on a key tradeoff means the whole thing is about to be relitigated in three weeks. Those signals live in tone, in the slight pause before someone agrees, in who did and didn't speak. In face-t