Javier Castro

Posted on Aug 27

The Summary Is Not the Meeting. The Meeting Was the Point.

#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 — absorbing the gap. Atlassian reports that in 2024 alone, each employee saved an average of three meetings per month by communicating asynchronously via Loom. Three fewer meetings per person per month. The calendar looks cleaner. The team looks productive. Something else is happening underneath.

What a Summary Cannot Carry

Here is what a competent meeting summary will give you: the agenda items that were covered, the decisions that were reached, the action items that were assigned. Here is what it will not give you: who paused before agreeing, who agreed with a visible lack of enthusiasm, who talked over whom, and what the room's energy was like when the Q2 deadline was announced.

This is not a sentimental observation. It has structural consequences.

Research into distributed teams found that participants reported persistent challenges in maintaining effective communication in distributed and ad hoc team environments, where — unlike co-located settings — responsibilities and emotional states couldn't be clarified in passing, and misaligned contributions frequently bred tension. The managers who navigated this well didn't lean harder into documentation. They leaned into presence: one team lead described wanting to interview each person individually when joining a new team, and another explained that video meetings mattered specifically because "you can read tones."

Tone. That's the word. It's the thing that doesn't make it into the recap.

The problem runs deeper at the summarization layer itself. Research into automatic meeting summarization highlights several persistent failure modes: implicit context — unspoken or implied knowledge, prior discussions not explicitly referenced, tacit organizational understanding — frequently gets neglected, producing summaries that are misleading or shallow. And that's before you account for the more basic problem: standard abstractive summarization doesn't work well for meetings because of long exchanges between multiple participants and unpredictable topic shifts.

Put plainly: meeting summaries systematically omit the organizational subtext that makes a decision meaningful. They report what was agreed. They cannot tell you whether anyone actually bought in.

The Phantom Consensus Problem

Buy-in is not the same as a logged action item. This distinction used to be obvious to anyone who had ever sat through a product roadmap review. It's becoming less obvious as teams optimize for information throughput.

Meetings both shape and are shaped by organizational culture, and the value participants derive from meeting recaps depends heavily on organizational expectations — decision-driven meetings prioritize action items and key discussions, while collaboration-focused ones center on process. That's the crux: when you read the recap of a collaboration meeting, you're reading a decision-meeting transcript of something that was never a decision meeting. All the messy negotiation, the half-formed concerns, the moment where someone said "sure, we can try that" in a tone that meant "I will try this exactly once before I say I told you so" — gone. Replaced by: Team aligned on direction. Action items assigned.

This produces what might be called phantom consensus: a documented agreement that nobody is actually committed to. The people who attended the meeting and nodded reluctantly are still not committed; they've just had their non-commitment smoothed out of the record. The people who read the recap think alignment exists. When execution starts fraying three sprints later, the diagnosis will be "unclear requirements" or "scope creep" — not "we never actually had agreement."

Researchers have also noted the risk that merely restricting meetings could hinder employees' opportunities to connect and socialize, and make workers fear being "left behind" when not participating in key discussions. That fear is legitimate. But the more insidious version isn't the fear of being left out — it's the false comfort of believing you've been included when you've only been informed.

The Counterargument Is Real

Let's be honest: the alternative isn't obviously better. Teams that default to meetings for every single decision pay a real coordination cost, face constant interruptions to deep work, and can become genuinely risk-averse as a result of over-consulting on everything. A senior engineer who can't make a reasonable architectural call without convening a call is not being collaborative; they're being bureaucratic with extra steps.

Research published in MIT Sloan Management Review acknowledges that while trust and cohesion require frequent, quality interactions, meetings are not necessarily the best vehicle for them — and companies including Atlassian have put real effort into testing no-meeting day policies to protect focus time. That's not theater. The productivity costs of meeting overload are documented and significant.

Leading psychological safety remotely requires more time, deliberation, and intentionality than when working face to face — which means that the managers who can pull it off asynchronously are doing harder work, not avoiding work. Async communication done well is a genuine skill, not a shortcut.

The argument here is not that meetings are sacred or that calendar-stuffing is a virtue. It's narrower: the default of replacing synchronous discussion with auto-generated summaries treats organizational alignment as a problem of information transfer. It isn't. Alignment is a problem of emotional buy-in, interpersonal trust, and the willingness to be accountable to a decision you were genuinely part of making.

The Atrophied Skill Nobody Is Talking About

There's a second-order effect worth naming. When teams stop meeting regularly, they also stop practicing the specific skill of reading a room, navigating live disagreement, and persuading people in real time. These are not soft skills in the dismissive sense. They are how organizations actually change direction.

Spontaneous interaction facilitates psychological safety, while remote work measurably raises the threshold for both spontaneous interaction and psychological safety. Psychological safety — the precondition for honest dissent, error reporting, and genuine debate — doesn't scale down to a text thread. A lack of psychological safety actively deters people from speaking up about mistakes, knowledge gaps, or potential problems. A weekly summary doesn't create the conditions under which someone flags that the estimate is wrong, or that the VP's assumption about the customer is off, or that there's a data privacy issue nobody has mentioned yet.

Those conversations require presence. Not necessarily physical presence — but intentional, synchronous, human presence. The kind where someone might catch the hesitation in a voice, or notice that the usually-opinionated architect has gone quiet.

In the absence of adequate tooling to surface these dynamics, effective team managers have consistently relied on routine check-ins, interpersonal assessment, and soft skills to sustain genuine alignment. What's happening now is that organizations are deprioritizing those check-ins in the name of efficiency, without replacing the function they served.

What To Actually Do About It

The practical answer is not "have more meetings." It's "be honest about which problem you're solving."

If you're reducing meetings because most of them are status updates that could be Slack messages, that's correct and good. If you're reducing meetings because the engineering org is overwhelmed and needs focus time, that's a legitimate tradeoff worth making consciously. But if you're replacing strategic discussions and team check-ins with auto-generated recap documents because the calendar was getting crowded — you have optimized for the appearance of collaboration while quietly defunding the real thing.

Meeting discussions are often non-linear, with participants using back-channel communication to resolve issues, seek clarifications, or improve decision-making — all things that vanish without a trace from any summary, however well-structured. The artifact is not the event.

Teams that have gotten async communication genuinely right tend to share one trait: they're ruthlessly selective about which conversations go to text, and they protect the remaining synchronous time ferociously. They don't skip the hard meeting; they eliminate the unnecessary one. That distinction requires judgment that no scheduling policy or summarization tool can make for you.

The efficiency trap closes on teams that have streamlined their way to a calendar that looks optimized, while wondering two quarters later why nothing sticks, why decisions keep getting relitigated, and why engineers keep building the thing that was technically in the spec but somehow not what anyone wanted.

Somewhere in a recap from last Tuesday, the answer to that question is missing. It was in the pause before someone said yes.

DEV Community