Question
What is meeting productivity?
Quick Answer
Every meeting needs a purpose, an agenda, a time limit, and clear outputs — and most meetings fail not because they exist but because they lack these structural elements.
Example: A product team holds a weekly 60-minute status meeting. Twelve people attend. Nobody prepares. The first twenty minutes are spent figuring out what to discuss. The next thirty become a meandering conversation between two engineers about a bug that affects only their subsystem. The final ten are a rushed attempt to assign action items that nobody writes down. The meeting cost the organization twelve person-hours and produced nothing that couldn't have been captured in a five-minute async update. The problem wasn't that the meeting existed — it was that the meeting had no structural hygiene: no stated purpose, no agenda, no time constraint on individual topics, and no mechanism for capturing outputs.
This concept is part of Time Systems in the How to Think curriculum.
Learn more in these lessons