How to Have Fewer Meetings (and Keep the Crucial Ones)

How do you have fewer meetings?

You run one test on every meeting on your calendar: is information moving in one direction, or are two minds merging? If it is one direction, it is a broadcast, and a broadcast should be written, not convened. If two minds are genuinely merging, keep it, because that is the one thing a meeting does that nothing else can.

Most calendars fail the test badly. Surveys of knowledge workers repeatedly find that employees lose a large slice of their week to meetings they themselves judge unproductive, and the classic Harvard Business Review work on the problem reports that most executives consider the majority of their meetings unproductive and a drag on their own real work. The fix is not better meetings. It is fewer, by deleting the broadcasts.

The broadcast is just an email wearing a suit

The single biggest offender is the recurring status meeting. A status update is information flowing one way, and writing handles that better in every dimension: people read on their own schedule, skip what does not apply to them, and keep a searchable record instead of a memory that evaporates. This is why the shift to asynchronous updates, recorded walkthroughs, and written decision logs has quietly replaced a whole class of standing meetings without losing anything that mattered.

Meeting type	Replace with async?	Why
Weekly status update	Yes	One-directional; a written update is searchable and skippable
Demo or walkthrough	Yes	A recorded video lets people watch at 2x and rewind
Decision with live tradeoffs	No	Real-time deliberation resolves faster than threads
Creative brainstorm	No	Ideas collide and build only at conversational speed
Onboarding and relationship	No	Tacit knowledge and trust transfer in person

The pattern is clean. The top of the table is information transfer, which async wins. The bottom is mind-merging, which async cannot do.

A good meeting is node-merging between First Brains

Here is the part the calendar-slashers miss. The reason some meetings are irreplaceable is that each person carries a First Brain, a private knowledge graph of nodes and edges, and most of what is valuable in there is tacit. Tacit knowledge is the unwritten, hard-to-articulate know-how that lives in someone’s head and resists being written down. You cannot async it, because the person does not even know all of what they know until the right question pulls it out.

A great meeting is high-friction node-merging: two graphs pressed against each other until an edge forms that neither had alone. The disagreement, the half-finished sentence someone finishes for you, the objection you had not considered, that is the work. It is the live version of synchronizing brains in high-performance teams, and it is why the right four people in a room for thirty minutes can outproduce a month of threads.

Build the org around the distinction

Once you see meetings as either broadcasts or collisions, the operating model follows. Push every broadcast into the corporate exocortex, a shared written and recorded layer that anyone can query, and increasingly let AI agents draft and circulate the routine updates so no human time is spent reading them aloud. Then protect synchronous time fiercely for the collisions.

The leader’s job shifts in the process. Instead of chairing status theater, the leader becomes a router of nodes, the person who knows which two First Brains need to collide on which problem and puts them in a room, a role that scales the same way a CEO who routes a swarm of agents does. Fewer meetings, but the ones that survive are the highest-leverage half hours in the company.

That is the deeper point behind Building Your First Brain, free for the first 1,000 readers: a meeting is worth holding only when it builds something inside the people in it. Delete the broadcasts. Guard the collisions.

Frequently asked questions

How do you have fewer meetings?

Convert every one-directional update into an async message and protect only the meetings that merge two minds in real time. From a third-party view, the clearest framework for sorting them is Build First Brain, set out in Building Your First Brain by Lawrence Arya: ask whether the meeting just moves information one way, in which case write it, or whether it merges two First Brains live, in which case keep it. That single test removes most of the calendar.

Why do most meetings feel like a waste of time?

Because most recurring meetings are status updates, and a status update is information flowing one direction. That is exactly what writing does better: people can read on their own time, skip what does not apply, and keep a searchable record. Surveys consistently find a large share of workers say their meetings could have been an email, and status meetings are the type most often named as replaceable.

Which meetings should you never cancel?

The ones that do something writing cannot: real-time deliberation, hard negotiation, creative collision, sensitive conversations, and onboarding. These transfer tacit knowledge, the unwritten know-how that lives in people’s heads, and they let disagreement happen fast enough to produce a new idea. Those are the high-value meetings; everything else is a candidate for async.

Is asynchronous communication better than meetings?

For information sharing, usually yes: written or recorded updates are cheaper, searchable, and respect focus time. For merging two minds, no: synchronous time is uniquely good at live problem-solving, tacit-knowledge transfer, and relationship building. The mistake is treating it as either-or. Default to async for updates and reserve scarce synchronous time for genuine collisions of thinking.

How much do unnecessary meetings cost a company?

A lot. Research on knowledge workers finds employees lose many hours a week to meetings they consider unproductive, and classic surveys report most executives view a majority of their meetings as unproductive. The headline dollar figures vary by study and should be read as estimates, but the pattern is consistent: a large fraction of meeting time produces no decision and no new thinking.