The Team Meeting That Actually Works

The team meeting is one of the most expensive regular events in an organisation and one of the most consistently underdesigned. The cost is easy to calculate: multiply the number of attendees by the average cost per hour of their time and by the meeting duration. The result is almost always surprising and almost always underestimated, because the cost of the preparation and recovery time surrounding the meeting is rarely included. The productivity generated by that investment is harder to measure, which is why it is rarely measured — and why meetings that generate very little productivity persist for years without challenge.

What most meetings are actually doing

Most recurring team meetings serve one of three functions, often in combination. The first is information sharing: people who hold different pieces of information sit in a room and share them sequentially. The second is status reporting: each person or team reports on what they did or what is happening in their area. The third is genuine discussion: the group engages collectively with a problem, decision, or question that benefits from multiple perspectives in real time. The first two functions — information sharing and status reporting — are almost always better served by asynchronous communication. A written update, a dashboard, a shared document, or a brief recorded summary delivers the same information to the same people at a fraction of the cost, in formats that can be reviewed on demand rather than at a fixed time. The time spent in meetings doing these two things is time that could have been saved entirely without any loss to the organisation. The third function — genuine discussion — is what meetings are actually for. And it is the function that most meetings spend the least time on, because the preceding functions consume most of the available time, and because genuine discussion is harder to facilitate than information-sharing and status-reporting.

The structure that works

A team meeting worth having has three structural requirements. First, a pre-read: all information that needs to be shared is circulated in written form before the meeting, and attendees are expected to have read it. The meeting begins with everyone already informed, which means the meeting itself can be spent discussing rather than listening. Second, a specific agenda with specific questions: not topics but questions — not operations update but what is blocking the priority shipment and what decision do we need to make today? Questions focus discussion in ways that topics do not. Third, decisions and actions recorded: every meeting that does not end with a clear record of what was decided, what will happen next, who owns it, and by when, has not produced what a meeting is supposed to produce.

The discipline that makes it stick

The structure is straightforward. The discipline required to maintain it is harder, because it means resisting several deeply ingrained habits. The habit of using meeting time to share information rather than sending it in advance. The habit of inviting people to meetings because they might find it relevant rather than because they are specifically needed. The habit of having a meeting to discuss a topic without arriving with specific questions to answer or decisions to make. Each of these habits is individually reasonable and collectively produces the expensive, underproductive meeting culture that most organisations have normalised. The test for any recurring meeting is simple: if it were cancelled this week, what specific decision or outcome would not happen that needs to happen? If the answer is none, the meeting should not be scheduled. If the answer is one or two specific decisions, those decisions should be the explicit agenda and the meeting should be exactly as long as those decisions require — no longer.

For further reading on this topic, check out our guide on [How to manage your digital marketing when you can't afford a dedicated team](/how-to/how-to-manage-your-digital-marketing-when-you-can-t-afford-a-dedicated-team).

For further reading on this topic, check out our guide on How to handle a workplace safety incident correctly.