Open your calendar and sort your meetings by their real purpose. Not their names — their purpose.
Some exist to decide something. Keep those. Some exist to build something together. Keep those too. And some — be honest now — exist so that people can find out what’s going on. The status meeting. The weekly sync. The alignment call. The check-in about the check-in. Count them.
In most companies, that last category is the majority of the calendar. And I want to say clearly what those meetings actually are, because once you see it you can’t unsee it:
A status meeting is a live performance of a dashboard that doesn’t exist.
—
Here’s how the multiplication happened — and notice that nobody chose it, which by now should feel familiar.
In a company without visibility infrastructure, information can only move one way: through humans, in conversation. We named this in Chapter 9 — oral tradition. At twelve people, proximity handles it; everyone overhears everything, and the company stays synchronized for free.
Then growth adds people, departments, handoffs — more moving parts that need to stay coordinated — while the information still moves at the speed of talk. So synchronization becomes manual labor. And the meeting is the manual synchronization protocol: gather the humans, have each one recite their fragment of reality, reconcile the fragments live, repeat next week because reality moved.
Meetings become synchronization rituals for systems that no longer naturally synchronize themselves — I wrote that line in Part One, and this is the section it was waiting for. The meetings didn’t multiply because your people love meetings. Nobody loves meetings. They multiplied because they are the only infrastructure you built.
Then the meetings breed. The sync spawns a pre-sync, because departments need to reconcile their numbers before presenting them — the meeting before the meeting, where the real reconciliation happens so the official meeting can perform agreement. Congratulations: your synchronization protocol now needs its own synchronization protocol.
—
Eventually someone notices the calendar is unlivable, and the company attacks the symptom — because Chapter 10 is undefeated.
Meeting hygiene. No-meeting Wednesdays. Agendas required, thirty-minute defaults, a viral memo about respecting people’s time. And six months later the calendar is full again — or worse, the meetings died and the confusion bloomed, because the meetings were *load-bearing*. They were compensating for missing visibility, and killing a compensation without replacing its function doesn’t eliminate the need. Same law as the shadow systems, same law as Susan: the job doesn’t disappear. It just loses its venue — and reappears as forty Slack threads, each one a tiny meeting that never ends.
You don’t have a meeting problem. You have a visibility problem with a calendar symptom. The communication overhead exists because the visibility infrastructure doesn’t — and no amount of meeting hygiene changes what the meetings are *for*.
People need meetings to find out what should already be visible to them. Fix the visible part, and watch what happens to the calendar.
That’s the last section of this chapter. But first: the five-people problem, up close.