Twelve calendars light up for a meeting about a document that already contains the answer. One person is still commuting, another is searching for headphones, and a third has joined from a supermarket car park with a camera pointed at the ceiling. Someone says, “Let’s give everyone a chance to weigh in,” and the hour begins disappearing. Modern work has created a peculiar ritual in which gathering people together is often mistaken for moving work forward, even when the gathering itself becomes the largest obstacle.
Meetings are not inherently useless. Some conversations need speed, disagreement, facial expressions, negotiation, or the uncomfortable pause before someone finally says what everyone has been avoiding. The trouble begins when synchronous communication becomes the default rather than a deliberate choice. A status update becomes a meeting, a question becomes a meeting, a document review becomes a meeting, and eventually the calendar becomes a map of organizational anxiety. People attend because absence looks like disengagement, even when presence contributes almost nothing.
Basecamp built much of its operating philosophy around written communication and fewer meetings, while GitLab developed extensive documentation to support collaboration across a distributed organization. Their significance is not that every company should copy them. The deeper lesson is that work improves when information does not have to travel through a room full of people before becoming useful. At a design firm, Priya replaced a daily status meeting with written updates and a weekly decision session; within weeks, colleagues were reading one another’s work more carefully because nobody could hide behind the reassuring noise of simply being present.
Then came the predictable mistake. Marcus, a department head, decided his organization had too many meetings and removed nearly all of them. Within a month, employees were trapped inside sprawling message threads, decisions were being interpreted differently by different teams, and difficult disagreements lingered because nobody wanted to write what they were unwilling to say aloud. Async work had not failed. The design had. Communication had been optimized for fewer interruptions without being redesigned for clarity, ownership, escalation, and human connection. Removing the room did not remove the need for a room.
That distinction matters because asynchronous work is not really about time zones or remote employment. It is about separating communication from simultaneous attention. A thoughtful written proposal gives people time to absorb context before responding; a recorded decision preserves institutional memory; a clearly assigned owner prevents a group from becoming responsible for nothing. Managers therefore face a more interesting question than “How many meetings can be cancelled?” They should ask which moments benefit from simultaneity and which merely inherit it from habit. Synchrony should be valuable enough to justify itself.
A workplace becomes calmer when every gathering has to earn its existence. Some meetings will survive that test because human presence changes what can happen. Others will collapse under the weight of their own calendar invitation. That is not a loss. It is evidence that the organization has learned to distinguish conversation from coordination, participation from contribution, and visibility from progress. Somewhere between a crowded conference room and an unanswered message lies a better operating principle: bring people together when presence changes the outcome, and let everyone else get back to work.
