Meeting Architecture

Why It Matters

The average knowledge worker attends 8 to 12 meetings per week, and research consistently shows that most are perceived as unproductive. The problem is not meetings themselves. It is that most teams have never deliberately designed their meeting portfolio. Meetings accumulate organically, overlap in purpose, and persist long after the need that created them has passed.

How to Design It

Meeting architecture starts with an audit: list every recurring meeting, identify its stated purpose, and assess whether that purpose is being achieved. Then categorize: which meetings are for decisions, which for coordination, which for information sharing, and which for relationship building? Each category has different requirements for format, frequency, and attendance. Information-sharing meetings can almost always be replaced with async updates.

Principles of Good Meeting Architecture

Every meeting should pass three tests. First, it has a clear purpose that cannot be accomplished async. Second, only the people who are necessary for that purpose attend. Third, it has a defined output (a decision, an action list, a shared understanding) that the team can point to afterward. Meetings that fail these tests should be eliminated, restructured, or converted to async formats.

• Every recurring meeting has a documented purpose and expected output
• The meeting portfolio is reviewed quarterly and pruned
• Default meeting length is 25 or 50 minutes, not 30 or 60
• Information-sharing meetings are replaced with written updates