Why Most Meetings Fail (and How to Redesign Them)

Everyone has left a meeting knowing it didn't accomplish anything, and yet we keep calling them the same way. The problem isn't how many meetings there are or how long they run: it's that most of them are designed to exchange information, not to coordinate action. Making them shorter or fewer doesn't fix anything if the underlying design stays the same — it just repeats the problem in a briefer format.

Most work meetings get called with an implicit goal: for everyone to report where they're at. That functions as an information exchange, not as coordinated action. The result is predictable: everyone reports their own piece, nobody takes on anything new, and the meeting ends with a sense that it "went fine" without anything actually moving in practice. The question almost nobody asks before calling a meeting is what needs to be agreed by the end that isn't agreed now. Without that question, any meeting — long or short, weekly or monthly — tends to repeat the same pattern.

In the Ontology of Language, coordination between people rests on one concrete unit: the request and the promise. A well-formed request has someone making it, someone it's made to, conditions of satisfaction that define what counts as fulfilled, and a deadline. A promise is the acceptance of those conditions. Most meetings produce neither: people voice intentions ("we should move forward on this"), mention problems, share status updates — but nobody makes an explicit request, and so nobody makes an explicit promise. No request, no possible promise; no promise, no real coordination, however "good" the meeting felt.

A meeting that ends without an explicit request already ended without producing anything.

The redesign starts before the meeting happens: define which request or promise needs to close there. During the meeting, every agenda item has to end with an explicit request — who's taking it on, to what standard, and by when — before moving to the next point. And the meeting isn't over until those requests get read out loud, one by one, with a name and a date attached. That last step, which looks like a minor formality, is what turns a conversation into real coordination: what doesn't get said out loud rarely gets done afterward.

When "nobody follows through" on a team, the automatic interpretation is usually that people lack commitment or discipline. Almost always the problem is one step earlier: in how the original request was framed. A request without clear conditions of satisfaction or a concrete date isn't really a request, it's an implicit expectation — and implicit expectations get missed far more easily than explicit requests, because it was never clear what fulfilling them actually meant. Before treating the missed commitment as an attitude problem, it's worth revisiting the request that gave rise to it.