Skip to content

Agenda Exit Gate

Facilitation protocol — instantiates Sufficiency-Bounded Work Containment

Puts a mandatory checkpoint at the end of each agenda item — "good enough to move on?" — and gives the chair standing authority to close it and to refuse unplanned additions.

An Agenda Exit Gate governs the boundary of a meeting: each agenda item ends at an explicit checkpoint where the group must declare the decision good-enough-to-act and move on, and the chair holds standing authority to close the item and to bar topics that weren't on the agenda. Its defining move is that it makes stopping the discussion a legitimate, role-backed act rather than an awkward interruption — and it routes every "while we're here, can we also…" through a gate instead of letting it swell the current item. Where a Timebox with Early Exit Rule bounds discussion by the clock, the exit gate bounds it by decision-sufficiency: the question is not "are we out of time?" but "do we have a decision we can act on?"

Example

A university curriculum committee is debating whether to add a statistics requirement. The discussion loops — the same three positions re-stated in new words — long after the workable answer has appeared. At the item's exit gate the chair calls the question the protocol requires: do we have a decision good enough to act on, or a specific missing input? The group recognises it already has one — adopt the requirement with a one-year review — and is now merely re-litigating preferences, so the chair closes the item. When a member tries to bolt on a sweeping "let's review the whole curriculum" discussion, the chair routes it to the request gate: it isn't on today's agenda, so it's parked for a future meeting rather than swallowing this one. The meeting ends on time with decisions made, not with every topic discussed to exhaustion.

How it works

  • Every item ends at an explicit gate, not an open-ended "anything else?" that invites the discussion to expand into the whole slot.
  • The gate asks a sufficiency question — "is the decision good enough to act on?" — rather than a consensus question, "is everyone fully satisfied?" The first stops short; the second invites expansion.
  • The chair holds delegated authority to close an item over residual discomfort, which is what makes stopping legitimate instead of rude.
  • New topics are routed, not absorbed — anything raised mid-item passes through a request gate (parked for a future agenda) rather than quietly enlarging the current one.

Tuning parameters

  • Gate question — decision-sufficiency ("can we act?") versus consensus ("are we all happy?"). The former closes items; the latter reopens them.
  • Authority strength — the chair's power to close as advisory nudge versus binding call. Stronger authority ends loops faster but can cut off genuine dissent.
  • Parking threshold — how readily a newly raised topic is deferred versus admitted now. Loose parking protects the meeting; too-tight parking buries the occasional urgent item.
  • Override rule — how the group can vote to keep an item open past the gate, so the authority is bounded rather than absolute.

When it helps, and when it misleads

Its strength is that it counters the way discussion expands to fill whatever meeting slot it is given,[1] and it makes "we've decided enough — move on" a legitimate move backed by a role instead of a social risk. Its failure mode is a chair who weaponises the gate to shut down inconvenient dissent under the banner of efficiency, manufacturing a false consensus; and a gate set on the clock rather than on decision-sufficiency closes good and bad discussions alike. The discipline that guards against this is to gate on whether an actionable decision actually exists, keep a visible override path, and never confuse "we have decided" with "we have run out of time."

How it implements the components

  • counter_pressure_authority — the chair's standing mandate to close an item over lingering discomfort is the legitimate counter-pressure to a discussion that would otherwise expand indefinitely.
  • expansion_request_gate — off-agenda topics must pass through the gate and be parked, so the meeting can only grow by explicit request, not by drift.

It bounds discussion, not build: it does not define the sufficiency standard being applied (independent_sufficiency_criterion — Definition of Done), and the equivalent gate for expanding a deliverable's scope — with its drift record — is Scope Change Ticket, not this meeting-side gate.

Notes

The exit gate and a Timebox with Early Exit Rule are easy to conflate but stop on different signals. A timebox stops when the time runs out and lets you leave early if you happen to finish; the exit gate stops when the decision is good enough, whether that comes early or would otherwise run long. Pairing them is common — the timebox caps the worst case, the gate catches the frequent case where a decision is reached well before the clock does.

References

[1] Parkinson's Law — "work expands so as to fill the time available for its completion" (C. Northcote Parkinson, 1955) — applies to discussion as much as to paperwork. A meeting item with no gate but its scheduled end tends to consume the whole slot; the exit gate supplies the earlier boundary. ↩