Schedule Slack¶

Planning method — instantiates Slack Capacity Design

Builds buffer into a plan — pooled float, lighter-load periods, deliberate slack days — so ordinary variation is absorbed instead of cascading into missed deadlines.

Schedule Slack puts the reserve inside the timeline. Its defining move is to hold slack as time positioned in a plan — an explicit project buffer, feeding buffers at merge points, deliberately lighter-load weeks — so that when individual tasks run long, the variation is absorbed by the buffer instead of propagating into a chain of missed downstream dates. The critical refinement is that the slack is aggregated and made visible rather than hidden as padding inside each task, and paired with a guardrail that tracks how fast the buffer is being consumed. That visibility is the whole point: task-level padding gets silently eaten and protects nothing, while a pooled, monitored buffer both protects the deadline and warns early when it is in trouble.

Example¶

An engineering project where every task estimate carries private padding still slips its deadline, because the padding is consumed no matter how much is given — work expands to fill the time, and tasks that could start early do not. The team strips the padding from individual tasks and pools it into one explicit project buffer at the end of the critical chain, then tracks buffer consumption against project completion on a simple burn-up chart. When the buffer starts burning faster than the work is progressing, the chart flags it weeks before the deadline is actually at risk, and the team acts while it still can. The same total slack that was invisible and useless as task padding becomes a visible, managed early-warning system. (This is Critical Chain Project Management's project buffer.^[1])

How it works¶

The distinguishing features are that slack is time built into a schedule, deliberately aggregated and positioned (a project or feeding buffer, or a scheduled light period) rather than dispersed as hidden per-task padding, and monitored for consumption so erosion becomes an early signal instead of a late surprise. It absorbs the ordinary variation that would otherwise cascade task-to-task.

Tuning parameters¶

Buffer size — the buffer as a fraction of critical-path duration. Larger protects more but pushes the committed date out.
Placement — one project buffer at the end, feeding buffers where paths merge, or scheduled lighter-load weeks; each protects a different failure point.
Consumption thresholds — the green/amber/red bands at which buffer burn triggers action.
Aggregation versus distribution — how much slack is pooled centrally versus left with tasks; pooling is more efficient and more visible, distribution feels safer to task owners.

When it helps, and when it misleads¶

It helps wherever task-level variation would otherwise cascade into schedule collapse, and where making the buffer explicit turns padding into an early-warning instrument. Its central failure mode is behavioral: slack hidden inside tasks is silently consumed by Parkinson's Law and student syndrome — the deferral of work until the padding is gone — so it never actually protects the deadline. The classic misuse is treating a visible buffer as free schedule to be given away to whoever asks, which quietly returns the plan to no slack at all. The discipline is to aggregate the slack explicitly and track its consumption, so erosion is seen rather than discovered at the deadline.

How it implements the components¶

protected_capacity — the reserved buffer time built into the plan is the reserve itself.
slack_type_catalog — it supplies schedule/time slack positioned in a timeline, distinct from material, budget, or standing-staff reserve.
slack_erosion_guardrail — buffer-consumption tracking is the guardrail that keeps the slack from being silently eaten, converting erosion into a visible signal.

It does not implement the live-load components utilization_ceiling and slack_visibility_metric — those are Utilization Ceiling Dashboard — nor hold the physical stock of Buffer Resources.

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

References¶

[1] Critical Chain Project Management (Goldratt) — padding is removed from individual tasks and aggregated into an explicit project buffer whose consumption is tracked against progress (a "fever chart"), converting hidden, easily-eroded slack into visible, managed slack. ↩