A meeting is the most expensive way to make a decision that an email could have made. This is obvious when you say it plainly, and yet meetings multiply anyway, because they don't feel expensive. They feel productive. People talked, alignment happened, everyone left with a shared understanding. The cost is real but invisible, and invisible costs are the ones organizations accumulate without limit, one reasonable meeting at a time.
The cost isn't just the hour, though the hour is bad enough when you multiply it by everyone in the room. The real cost is the focus on either side of it. A meeting at eleven doesn't just take an hour; it poisons the hour before, which you can't start anything serious in because the meeting is coming, and the hour after, which you spend reassembling the concentration the meeting scattered. One hour-long meeting can cost a builder a whole morning.
For makers this is devastating in a way it isn't for managers, and the difference explains a lot of organizational conflict. A manager's day is already chopped into intervals; a meeting fits the existing rhythm. A maker needs long unbroken stretches to hold a complex thing in their head, and a meeting in the middle of the afternoon doesn't cost one hour, it costs the whole afternoon, because the deep state it interrupted takes an hour to rebuild and won't survive a second interruption.
The reason the habit creeps in is that meetings feel like work, and often feel like more important work than building, because they're where the social signals of importance live. You were needed. You were consulted. Decisions were made in your presence. But presence at decisions is not the same as making things, and a calendar full of meetings can perfectly disguise a week in which nothing was actually built. The busyness is real. The output is missing.
The best small teams I've seen are almost suspiciously quiet, and it's not an accident. They've defaulted to writing things down instead of gathering to discuss them, which means decisions get made on people's own time, asynchronously, without dragging five calendars into alignment. The quiet isn't disengagement. It's what a team sounds like when it has stopped paying the meeting tax and started spending the recovered time on the actual work.
There's a deeper reason async beats real-time for most decisions, beyond just saving the hour. Writing a decision down forces you to actually think it through, in a way that talking doesn't. A meeting rewards whoever speaks most confidently; a written proposal rewards whoever's argument survives being read slowly. So the move to writing doesn't just save time, it improves the decisions, which is the part people miss when they defend meetings as necessary for alignment.
None of this means meetings are never worth it. Some problems genuinely need real-time, high-bandwidth, everyone-in-the-room discussion — the messy, ambiguous ones where you have to react to each other to find the answer. Those meetings earn their cost. The problem is that they're rare, and the calendar fills with the other kind, the status updates and the alignments and the could-have-been-an-email, until the rare valuable meeting is buried in routine ones.
So the discipline isn't to ban meetings. It's to make the default 'no,' write it down instead, and reserve the real-time gathering for the few problems that actually need it. Every recurring meeting you cancel is an hour of building you get back, doubled, because you also get back the focus around it. For a small team, where focus is the only resource that truly scales, that's not a minor optimization. It's most of the game.