Skip to content

Slack Release Review

Release-gate review — instantiates Slack Capacity Design

A gate that vets each request to draw down protected capacity, confirming the use matches the slack's stated purpose and carries a replenishment plan before the reserve is released.

Slack Release Review is the control that makes "protected" mean something. Its defining move is to insert a decision at the moment of release: before anyone draws on the reserve, a reviewer checks that the use genuinely matches the slack's stated purpose and comes with a plan to put the capacity back, and records the draw. This is what separates legitimate activation from the quiet erosion that turns a reserve into a fiction — not a big raid, but a hundred individually-reasonable "just this once" borrowings that no one added up. The review holds no reserve and displays no metric; it is purely the gate the reserve passes through on its way to being used.

Example

A newsroom protects roughly two reporters' time for long-lead investigative work. But every big news day, an editor asks to "borrow" them for breaking coverage, and if borrowing is frictionless the investigative reserve silently disappears into the daily grind. The paper institutes a quick release review: any draw on the protected time needs a senior editor's sign-off that checks two things — is this genuinely a story worth the reserve's purpose, and what is the plan to give the time back or backfill it. Every approved draw is logged. A quarter later the log tells the real story: the reserve was borrowed fourteen times (illustratively) and replenished none of them — evidence that the "protected" investigative capacity had become imaginary, and grounds to fix the pattern. The review did not hold the reserve; it re-priced each casual draw and created the record that exposed the leak.

How it works

The distinguishing move is a decision gate at the point of release. It applies the release condition (is this an authorized use, by an authorized person, for the stated purpose?), it requires a replenishment commitment as a condition of approval (not just intent to use, but a plan to restore), and it logs each event so that erosion becomes visible in aggregate. It is a per-request control, not a standing plan or a passive display.

Tuning parameters

  • Approval threshold — how large a draw must be before it needs review. A low threshold controls tightly but adds friction to small legitimate uses.
  • Authorizing role — steward, line manager, or committee. Higher authority resists capture better but slows response.
  • Replenishment strictness — whether an approved draw must carry a concrete payback plan or merely an intent to restore.
  • Logging depth — how much each draw records, which sets how well later erosion analysis can work.

When it helps, and when it misleads

It helps most where slack erodes through many small, individually-reasonable borrowings rather than one visible raid — the commons dynamic that quietly empties a shared reserve.[1] Its failure modes are the two ends of the dial: too heavy, and people route around it or leave the reserve unused when it is genuinely needed; too light, and it becomes a rubber stamp that logs every draw and denies none, which is erosion with paperwork. The classic misuse is exactly that rubber stamp — a review that exists to bless decisions already made. The discipline is to track approval-versus-denial rates and replenishment-completion, so the gate is shown to actually gate.

How it implements the components

  • release_condition — it operationalizes when protected capacity may be used and who authorizes it, distinguishing activation from erosion.
  • replenishment_rule — it requires and records a replenishment commitment as a condition of releasing the reserve.
  • slack_use_log — every approved draw is logged, creating the record that later erosion analysis depends on.

It does not implement protected_capacity or the slack_steward and opportunity_cost_review that hold and govern the reserve — that's Capacity Pool — nor the slack_visibility_metric and utilization_ceiling display of Utilization Ceiling Dashboard.

  • Instantiates: Slack Capacity Design — Slack Release Review is the release-gate control within the broader slack system.
  • Sibling mechanisms: Utilization Ceiling Dashboard · Capacity Pool · Innovation Time · Maintenance Window · Buffer Resources · Learning Time · Reserve Staffing · Schedule Slack · Surge Roster · Unallocated Budget · Emergency Reserve

References

[1] Slack behaves like a commons: each draw is small and individually reasonable, but unreviewed they aggregate until the shared reserve is gone — Hardin's tragedy of the commons. The release gate is what re-prices each draw so the aggregate cost becomes visible. ↩