The Oldest Waste of Everyone's Afternoon

Somewhere right now, someone is sitting in a meeting about a problem that will not be solved in that meeting. They know it. The person running the meeting knows it. The person who scheduled the meeting knew it before they sent the calendar invite. And yet here everyone is, in a conference room or on a video call, going through the motions of collective deliberation.

This is not a modern failure of corporate culture. This is not a tech industry quirk or a government bureaucracy problem. This is one of the oldest and most consistent behaviors in the entire human record. We have been calling meetings to perform concern about problems we have no intention of fixing for at least five thousand years, and the evidence suggests we're not going to stop.

Egypt Had This Problem Before Paper Did

The Egyptian pharaohs ran one of the most sophisticated administrative machines the ancient world ever produced. They had tax collectors, grain accountants, military logistics officers, and a professional class of scribes who documented everything. They also had councils.

The royal council—the djadjat—convened regularly to advise the pharaoh on matters of state. Inscriptions and administrative records from the Old and Middle Kingdom periods describe these gatherings in terms that will feel immediately familiar to anyone who has ever attended a quarterly business review. Officials presented reports. Problems were acknowledged. The pharaoh listened. Decisions were recorded.

What the records show less clearly is what actually changed as a result. Historians studying Egyptian administrative continuity have noted that the same categories of problems—grain shortages in particular nomes, disputes over land boundaries, labor allocation for state projects—appear in council records across generations. Not because the problems were unsolvable, but because the council was not really designed to solve them. It was designed to demonstrate that the pharaoh was engaged, informed, and appropriately surrounded by wise advisors.

The appearance of governance and the practice of governance are not the same thing. Egypt knew this. They just didn't write it down in those terms.

The Roman Senate and the Art of Magnificent Inaction

If Egypt invented the administrative meeting, Rome perfected it as performance.

The Roman Senate was, at its peak, a body of several hundred men who could speak at essentially unlimited length on any topic before the house. Senatorial debate had rules, but those rules were primarily procedural—who could speak, in what order, with what forms of address. They were not rules designed to produce timely decisions.

This was not an accident. The Senate's power rested substantially on its ability to deliberate, and deliberation is structurally incompatible with urgency. A senator who wanted to block a measure didn't need to defeat it in a vote. He could simply keep talking. The filibuster—a word we borrowed directly from Roman practice through Latin—was a feature of the system, not a bug.

Cicero's letters and speeches document dozens of Senate sessions convened to address genuine crises—military threats, food shortages, public unrest—that concluded with the appointment of committees, the scheduling of further deliberation, or simply the adjournment of the session. The crisis remained. The Senate had met about it. These were treated as related accomplishments.

The historian Sallust, writing in the first century BCE, was already complaining that the Senate had become more concerned with the appearance of deliberation than with its outcomes. He was writing about a body that was, at that point, several centuries old. The dysfunction wasn't new when Sallust noticed it. He was just the one who wrote it down in a way that survived.

Medieval Councils: Bringing the Whole Kingdom Together to Agree on Nothing

The great councils of medieval Europe—predecessors to modern parliaments—operated on a principle that sounds democratic and functioned as theater. The king would summon nobles, bishops, and occasionally representatives of towns to discuss matters of pressing importance: taxation, war, succession, legal reform.

These gatherings were genuinely important as political rituals. They created consensus through the appearance of consultation, even when the outcome was predetermined. A king who wanted to raise taxes found it useful to convene a council not because the council might say no—it usually didn't—but because a council that had been consulted could not later claim it had been ignored. The meeting created buy-in. Or at least it created the documented appearance of buy-in, which served almost as well.

The problems discussed in these councils recur across centuries of records. Land disputes. Church-state jurisdiction conflicts. The rights of towns versus the rights of lords. Generation after generation of medieval rulers convened meetings about these exact issues. Generation after generation of scribes wrote down what was discussed. The issues persisted.

Why Meetings Work Even When They Don't Work

Here's where the psychology gets interesting, and where five thousand years of data tells a consistent story.

Meetings are not primarily information-sharing mechanisms. They're status rituals. Who gets invited signals who matters. Where people sit signals hierarchy. Who speaks first, who gets interrupted, who gets the last word—all of this communicates organizational reality far more clearly than any org chart.

This is why meetings persist even when everyone in them knows nothing will be decided. The meeting isn't for deciding. The meeting is for enacting the social structure of the group. It's for reminding everyone of their place in the order, for allowing leaders to perform leadership, and for giving participants the experience of having been consulted—whether or not their input will influence anything.

Psychologists call this procedural fairness: people are more willing to accept outcomes they don't like if they feel the process that produced those outcomes was legitimate. A meeting is a legitimacy machine. It makes decisions feel considered even when they were made before anyone walked in the room.

Pharaonic councils, Roman Senate sessions, medieval great councils, and your company's all-hands meeting are all running the same software. The hardware looks different. The function is identical.

The Meeting That Produces the Next Meeting

There's one more element of meeting culture that appears consistently across the historical record, and it may be the most honest expression of what meetings are actually for.

The meeting that ends by scheduling another meeting.

Egyptian administrative records show follow-up councils convened to review the outcomes of previous councils. Roman senatorial procedure included provisions for continuing deliberation across multiple sessions. Medieval councils routinely adjourned with the understanding that the same issues would be taken up at the next convening.

Modern organizations have formalized this into standing meetings—the weekly check-in, the monthly review, the quarterly business update—that exist on the calendar regardless of whether there is anything to check in about, review, or update. The meeting is the deliverable. Holding it is the accomplishment.

This isn't purely cynical. Recurring gatherings do maintain relationships, distribute information, and create shared context. Those are real functions. But they are not the functions that get cited when someone schedules the meeting. The stated purpose is always the problem to be solved. The actual purpose is something older and more durable: the demonstration that the people in charge are paying attention.

Five thousand years of paying attention. Remarkably little of it in writing.