Skip to content

Commitment Budget

Standing allocation policy — instantiates Overcommitment Prevention

Caps the total promises an actor may hold at once, so a new yes must fit the budget or displace an existing commitment.

Commitment Budget fixes, in advance, how much promised obligation the system may carry — expressed in a chosen unit (active engagements, story points, delivery slots, obligated dollars) — so that accepting a new commitment requires either free budget or the explicit retirement of an existing one. Its distinguishing idea is setting the number before pressure arrives and making "yes" a zero-sum act against a finite pool. It is the limit itself — not the per-item check (Intake Capacity Checklist), not the automated enforcement (Budget Encumbrance Control), and not the display.

Example

A twelve-person design agency keeps saying yes and drowning. It sets a commitment budget: at most six active client engagements at once. The unit is a live engagement; the ceiling of six comes from the honest finding that quality cracks past six. Now when a seventh prospect appears, the rule is explicit — the agency either waits for an engagement to close, or a partner invokes the exception path to run seven by naming which existing client's scope shrinks and setting a review date three weeks out. The budget converts an open-ended "can we squeeze it in?" into a visible trade against a hard pool, and the exception path keeps "just this once" from silently becoming seven-forever.

How it works

The signature is a pre-set cap in an explicit unit, plus a defined overflow path. First choose the commitment unit; then set the ceiling from real evidence of where quality or reliability breaks, not from aspiration; then hold the line so that exceeding it is impossible without invoking a named exception that requires a displacement and a review date. The limit's credibility comes entirely from the exception path having teeth — a cap that can be waived costlessly is not a cap.

Tuning parameters

  • Commitment unit — what one unit of promise is (engagements, points, slots, obligated dollars). Coarse units are simple but blunt; fine units are precise but heavy to track.
  • Ceiling level — where the cap sits. Too high and it never binds; too low and it starves legitimate growth. Set it from observed break points.
  • Rigidity — hard cap versus tiered band (green/amber/red) versus review threshold. Hard caps are unambiguous; bands allow graceful degradation.
  • Exception cost — how painful invoking the exception is: who must approve, what must be displaced. Cheap exceptions dissolve the budget; costly ones keep it real.
  • Reset cadence — per quarter, or a rolling window. Frequent resets adapt to real capacity; rare ones give stability.

When it helps, and when it misleads

Its strength is making the trade-off unavoidable and pre-decided, so the system stops relying on in-the-moment willpower to say no; a finite budget forces prioritization by construction. Its limit is that a budget is only a number — if the unit is mis-chosen or the ceiling wrong, it caps the wrong thing (six equal-sized engagements is fine until one is ten times the others). The classic collapse is an exception path with no teeth: a limit that can always be waived without consequence is not a limit, and every urgent case becomes an exception until the budget is decorative. The discipline is to size the unit to real load variance, set the ceiling from evidence, and require every exception to name a displacement and a review date.

How it implements the components

Commitment Budget realizes the limit-setting side of the archetype:

  • commitment_unit — defines the countable unit of promise the budget is denominated in, so nothing enters the pool without a capacity burden.
  • commitment_limit — the ceiling itself: the maximum promised load allowed before review, as a hard cap or tiered band.
  • exception_and_escalation_path — the named, costly route for exceeding the cap, requiring displacement and a review date so the limit keeps meaning.

It sets the cap but does not verify each request (Intake Capacity Checklist), enforce spending against a fund (Budget Encumbrance Control), or track load over time (Commitment Burndown Review).

  • Instantiates: Overcommitment Prevention — it is the standing limit the whole archetype checks new promises against.
  • Sibling mechanisms: Intake Capacity Checklist · Budget Encumbrance Control · Work-in-Progress Cap · Portfolio Intake Gate · Backlog Commitment Review · Commitment Burndown Review · Capacity Dashboard · Calendar Capacity Audit · Renegotiation Notice Protocol · Sales Capacity Alignment Review

Notes

A commitment budget bounds the count of promises but not their size. Six engagements is a safe ceiling only if engagements are comparable; one giant yes can blow the budget while staying "within" it. Pair it with explicit commitment terms (via Intake Capacity Checklist) so the units being counted are actually commensurate.