Meeting Budget¶
Policy — instantiates Coordination Scaffold Load Control
Caps the coordination capacity a team may spend — meeting-hours, standing forums, recurring syncs — as a hard budget, so adding one coordination event requires retiring another.
A Meeting Budget is a policy that sets a hard ceiling on the coordination capacity a team may spend — recurring meeting-hours, standing forums, weekly syncs — and enforces it as a fixed budget: to add a new coordination event, an existing one must be retired. Its defining idea is that scarcity is imposed at the aggregate, not the item. It passes no judgment on whether any single meeting is worthwhile; it simply refuses to let the total grow, forcing the team to trade its least valuable coordination for whatever new coordination it wants. It is a ceiling, not a measurement engine and not a value verdict on any particular meeting.
Example¶
At a video-game studio, the engineers on one team have drifted down to about two uninterrupted hours a day. The rest is standups, sprint syncs, playtest reviews, cross-discipline check-ins, and planning — each individually defensible, collectively suffocating. Leadership sets a budget rather than adjudicating meeting by meeting: no more than eight hours a week of recurring meetings per engineer, protected no-meeting Wednesdays, and a rule that any new standing meeting must displace an existing one of equal length.
What follows is a market. Teams horse-trade their weakest syncs to fund the meetings they actually value; a low-signal cross-discipline check-in gets sacrificed so a genuinely useful design review can be added. The total coordination time stops climbing because the budget will not let it, and maker-time roughly doubles — not because any one meeting was banned, but because adding coordination now costs something the team must pay from a fixed account.
How it works¶
The policy defines the budgeted unit (usually recurring meeting-hours, sometimes attendee-hours), sets a ceiling per team or per person, and enforces an add-one-remove-one trade so the layer cannot grow silently. It protects blocks of maker-time as first-class budget items, and it accounts current coordination spend against the cap so the ceiling is real rather than aspirational. The distinguishing move against its siblings is that it imposes an aggregate cap with a forced trade-off — a zero-sum discipline on coordination as a whole — rather than measuring load, removing a specific artifact, or mapping who decides.
Tuning parameters¶
- Ceiling level — how tight the cap is set. A tight ceiling reclaims maker-time aggressively but risks starving needed coordination; a slack one is safer but bites less.
- Budget unit — meeting-hours, meeting count, or attendee-hours. Attendee-hours punish over-inviting; simple meeting-hours are easier to track but ignore room size.
- Protected blocks — how much time is fenced off as uninterruptible. Larger protected blocks guarantee focus but leave less room for legitimate synchronous work.
- Trade-rule strictness — hard displacement (must remove to add) versus soft guidance. Hard rules hold the line; soft ones flex under pressure and tend to erode.
- Scope — team, individual, or org-level budget. Team budgets encourage local prioritization; individual budgets protect personal focus but can fragment shared coordination.
When it helps, and when it misleads¶
Its strength is manufacturing scarcity where none existed. Coordination that no single stakeholder is willing to cut will nonetheless get cut when the team must fund additions from a fixed account — the budget forces the prioritization that goodwill never produces.
Its failure mode is displacement rather than reduction: capped meetings reappear as async pings, ballooning documents, or shadow syncs held off the official calendar, so the load migrates instead of shrinking. The mechanism is zero-based budgeting applied to attention, and it shares that method's gaming risk — the budget is only as honest as the accounting behind it.[1] The classic misuse is setting the cap so low that genuinely necessary coordination is starved and downstream rework explodes, trading visible meeting-time for invisible error. The guarding discipline is to budget total coordination load rather than meetings alone, and to watch for load leaking into unbudgeted channels.
How it implements the components¶
coordination_capacity_budget— its core: the explicit aggregate ceiling on coordination spend, enforced by a forced trade.metawork_load_measure— accounts current coordination-hours against the cap, which is what makes the ceiling enforceable rather than nominal.
It caps capacity but neither computes value nor scopes to the activity served: the support_value_ratio that says whether the coordination is *worth it, and the supported_activity_boundary it is judged against, belong to the work_before_metawork_ratio_dashboard — its nearest twin, which measures and reports where this simply imposes a limit regardless of value.*
Related¶
- Instantiates: Coordination Scaffold Load Control — supplies the hard aggregate ceiling that keeps coordination from growing without a trade.
- Consumes: work_before_metawork_ratio_dashboard — the dashboard's load figures set the budget's level and show whether the cap is holding.
- Sibling mechanisms: async_decision_log · coordination_artifact_kill_switch · coordination_load_audit · delegation_authority_matrix · exception_based_oversight · governance_forum_consolidation · handoff_path_pruning · support_layer_sunset_review · work_before_metawork_ratio_dashboard
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Meeting Budget operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it caps the coordination capacity a team may spend — meeting-hours, standing forums, recurring syncs — as a hard budget, so adding one coordination event requires retiring another.
Independent corroboration: The frozen evidence defines Meeting Budget as 'Caps the coordination capacity a team may spend — meeting-hours, standing forums, recurring syncs — as a hard budget, so adding one coordination event requires retiring another', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Treating meeting time as scarce coordination capacity belongs to organizational design and management.
Related originating lineages:
- Economics & Finance — Opportunity-cost reasoning supplies the hard-budget tradeoff.
Review resolution: Both independent reviews place the primary provenance in organizational_management. The queued differences (alternate_origin_disagreement, origin_mode_disagreement) concern secondary metadata, not primary lineage. The final retains economics_finance only where a reviewer supplied a formative-lineage rationale; downstream use or broad applicability by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis because the supplied rationales identify formative contributions that are composed in the mechanism's present form. domain_reach=multi_domain records established application breadth separately from provenance. confidence=high preserves the more cautious evidence assessment. encyclopedia_synthesis=true records whether either reviewer identified deliberate corpus-level composition.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Zero-based budgeting — Peter Pyhrr's method (developed at Texas Instruments around 1970) in which every line item must be justified from zero each cycle rather than inheriting the prior period's allocation. A meeting budget applies the same forced re-justification to coordination time, and inherits the same vulnerability to gamed accounting. withdrawn registry ↩