Mission Intelligence Systems

Glossary · Authority Dimension

Meeting Architecture

The structure of an organization's recurring meetings taken as a system: which exist, who sits in them, and what each one is actually empowered to decide. A diagnostic of authority, not of scheduling.

Definition

Meeting architecture is the shape of an organization's recurring meetings considered as one system: which meetings exist, who sits in each, what each is empowered to decide, and how a decision moves between them.

A term in general use in organizational design. What is particular here is reading it as evidence of Authority rather than as a scheduling problem.

An org chart records who reports to whom. A meeting system records who is in the room when something is settled. Where the two disagree, the meetings are the more reliable witness, because attendance is a decision somebody made every week and a reporting line is a decision somebody made once.

This is why the meeting system is read as evidence of authority rather than as a scheduling nuisance. Almost every organization that has looked at its own calendar has looked at the volume: how many hours, how many recurring invitations, how much of the week is gone. That is a real question, and it has its own name here, calendar density. It is not this one. Architecture asks a different thing about the same hours: what shape do they have, and where inside that shape does a decision actually become final?

The distinction matters because the two have different fixes and only one of them is usually attempted. An organization can cut its meeting load by a third and leave the architecture untouched, in which case the decisions that had nowhere to land still have nowhere to land. They move somewhere less visible: a hallway, a thread, a conversation between two people who happen to have the standing to end an argument. Cancelling meetings is a density intervention. Naming which meeting owns which decision is an architecture one.

The clearest single symptom is a decision that will not stay decided. When a matter settled in one meeting returns in the next, no meeting in the system holds real authority over it, and the organization is paying to make the same decision repeatedly. That pattern is rarely read as an authority problem. It is usually read as a communication problem, which is why it persists.

What the meeting system reveals

Each of these is observable from a calendar and an attendee list, before anyone is interviewed. That is what makes the meeting system a useful early read.

Pattern in the meeting systemWhat it usually meansDimension
Decisions are re-opened in a later meetingNo meeting holds real authority; the decision is made off the calendarAuthority
Every recurring meeting reports, none decidesThe system is built to inform, so decisions accumulate with nowhere to landAuthority
The same few people sit in nearly all of themAuthority is concentrated into a bottleneck that scales no furtherAuthority
Nobody can state why a standing meeting existsThe architecture accreted rather than being designedAlignment
Attendance is by seniority rather than by decisionRooms are populated by rank, so the people with the information are absentAuthority
The real decision happens in a pre-meetingThe visible meeting ratifies; the working authority sits elsewhereAuthority
Most of the week is committed before it startsA density problem rather than an architecture one, and a different fixAttention

Frequently asked questions

What is meeting architecture?

Meeting architecture is the structure of an organization's recurring meetings taken as a single system rather than as a list of separate events: which meetings exist, who sits in each one, what each is actually empowered to decide, and how a decision moves between them. The term is in general use in organizational design. What is particular to the diagnostic used here is reading it as evidence of Authority, the third dimension of the Four A's of Organizational Readiness™, because a meeting system is where decision rights are exercised in practice whatever the org chart says.

How is meeting architecture different from having too many meetings?

Volume and shape are different problems with different fixes. Calendar density asks how much of the working week is committed. Meeting architecture asks what shape that committed time has and where decisions actually get made inside it. An organization can cut its meeting load substantially and keep an architecture in which no meeting is empowered to decide anything, in which case the decisions simply move somewhere less visible. Cancelling meetings is a density intervention. Deciding which meeting owns which decision is an architecture one.

What does a broken meeting architecture look like?

The most reliable signal is that decisions are re-opened. If a matter settled in one meeting returns in the next, no meeting in the system holds real authority over it, and the real decision is being made somewhere off the calendar. Other common signals: every recurring meeting reports and none decides; the same handful of people sit in all of them, which concentrates authority into a bottleneck; and nobody can state the purpose of a long-standing recurring meeting, which means the architecture accreted rather than being designed.

How is meeting architecture related to organizational readiness?

Meeting architecture is one of the most legible diagnostics of Authority, because it is a written record of where an organization believes decisions belong. It touches the other dimensions too: the volume of the system is an Attention question, and what the meetings are for is an Alignment one. Read together with decision paths and approval chains, the meeting system usually reveals the working authority structure faster than an org chart does, because the chart records reporting lines while the calendar records who is actually in the room when something is settled.

Work With Us

Schedule an Executive Strategy Session

Find out whether your decisions have anywhere to land.

Schedule Executive Strategy Call →