The Meeting You Skipped Was the One That Actually Mattered
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,…
The meeting that no one attended proved to be the most crucial. In a mid-sized software company that had transitioned to an async-first culture, major decisions were made without the full participation of the team. A bot attended every Zoom call, summarizing discussions and dropping the output into Confluence, which people read or ignored according to their own schedule.
Six months later, an important architectural decision, made through a Loom video that only a fraction of the engineering team had seen, became the source of a tense standoff between the backend and platform teams. No one felt ownership over the decision, as they had not been present during its creation.
This scenario illustrates a wider issue: while async communication can increase efficiency by reducing interruptions and allowing for asynchronous work, it can also lead to a lack of shared understanding and ownership. Many meetings are seen as mere theater, with 77% of workers attending meetings that result in scheduling more meetings and 62% sitting through meetings without a clear goal.
The problem arises when the focus shifts from participation to mere presence, and teams start to view the absence of synchronous contact as a sign of operational maturity.
The difference between being informed and being part of something is critical. A well-structured meeting summary informs you of the decisions made but does not convey the nuances of the discussion, such as differing opinions that were overruled or sudden changes in strategy. These subtle cues are lost in virtual interactions, where facial expressions and body language that convey engagement and disagreement are absent.
When employees do not understand the 'why' behind their work, they become disengaged and produce lower-quality output. Transparency about how individual tasks connect to larger strategic goals is essential for fostering a sense of purpose and ownership, which drives better results.
Despite the efficiency gains reported, these are largely individual improvements rather than team-level advancements. Atlassian's 2025 State of Teams report reveals that while 89% of executives believe their organizations need to move faster, only 7% feel confident that their teams are aligned with company goals. The productivity gains from AI tools are minimal, with only 4% of executives reporting that AI helps teams solve previously unsolvable problems and 37% stating that AI causes teams to waste time or head in the wrong direction. Instead, the productivity improvements are indirect and often peripheral to actual collaboration.
Longitudinal studies tracking software development teams from 2023 to 2025 show that despite initial hopes that AI could transform team collaboration, core challenges of underperformance and communication breakdowns remained unchanged. Individual adoption of AI tools has not significantly impacted teamwork, as these tools offer convenience but rarely foster deeper shared understanding.
Employees who rely on non-meeting communication for interdependent tasks report that it is harder to pay attention, prompts less discussion, and takes longer than if they had met in person. They also feel less connected to their teammates during meeting-free periods, adding to a sense of isolation. The meetings that often get skipped are those that are crucial for building a sense of belonging and shared purpose, such as all-hands meetings, sprint reviews, and retrospectives.
These meetings are not captured on efficiency dashboards, but their value lies in the shared experience of the content, which fosters mutual awareness and ownership that AI-generated notes cannot replicate.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.