Meeting Load And Decision Drag

Meetings are not the unit of work

A meeting is rarely just the minutes on the calendar. It creates preparation, interruption, attention residue, emotional load, follow-up, interpretation and re-entry. If the meeting does not produce a decision, owner or next move, the real work continues afterwards in side channels. That is where decision drag begins.

Decision drag is a design failure

Decision drag happens when the organisation keeps circling a choice without clarifying who decides, what evidence matters, what trade-off is acceptable or when enough is enough. Teams may look collaborative while actually using meetings to avoid ownership. The result is more alignment work, slower execution and more hidden load on the people trying to move things forward.

More meetings can reduce clarity

When work is unclear, the reflex is often to meet again. Sometimes that helps. Often it multiplies the load. Each meeting creates more fragments unless the system has a clean decision structure. Good meeting design asks: is this for sense-making, deciding, coordinating, escalating or relationship repair? If the purpose is not clear, the meeting becomes a holding pen for uncertainty.

What useful meetings produce

A useful meeting produces a shared understanding of the issue, a decision, a named owner, a standard for done, a time boundary, a next move or a reason the work is intentionally paused. Without one of those outputs, the meeting may create more theatre than traction. Poko for Work looks at what the meeting does to cognitive load, not only whether it happened.

How to reduce drag

Reduce decision drag by separating discussion from decision, naming decision rights before the meeting, limiting channels for follow-up, making trade-offs explicit and recording the next owner in plain language. The aim is not fewer meetings as a slogan. It is fewer meetings that create invisible work afterwards.

How to use this

• Before one recurring meeting, write its real purpose: decide, coordinate, sense-make, escalate or repair.
• Name the decision owner and next move before the meeting ends.
• Delete or redesign one meeting that creates follow-up without ownership.