Rolling-Wave Schedule¶
Planning — instantiates Temporal Orchestration Design
Plans the imminent wave in firm, committed detail and leaves the far horizon deliberately coarse, then re-elaborates each wave as uncertainty resolves — matching plan resolution to what is actually knowable.
Planning a long, uncertain effort in full detail up front is a waste: the far-out detail is fiction that will be rewritten anyway. Rolling-Wave Schedule matches the resolution of the plan to the resolution of what is known. The near wave — the next few weeks or months — is elaborated into firm, committed tasks; the middle distance is roughed in; the far horizon is held as coarse placeholders and forecast dates. As each wave completes, the next is elaborated into detail using what execution just taught. Its defining move is separating commitment hardness by distance: near-term dates are promises, far-term dates are explicitly labeled forecasts, and nobody is asked to commit to what cannot yet be known. It governs how a single plan's detail and commitment mature over its horizon — not the recurring rhythm of operations, and not reactive re-solving on disturbance.
Example¶
A space-systems team is building a new Earth-observation satellite on a multi-year program. Fixing a day-by-day schedule for integration and test three years out would be pure invention — the instrument design that drives those tasks is not frozen yet. Instead they run rolling waves. The current wave — subsystem design and the first engineering models — is planned in committed detail with hard near-term milestones the whole program coordinates against. Integration, environmental testing, and launch-campaign activities exist only as coarse phase blocks with forecast windows, flagged as such. When the design review passes and the instrument is frozen, the next wave — build and subsystem qualification — is elaborated into real tasks and durations, informed by what the design phase actually revealed about effort and long-lead parts.
The plan is never fully detailed and never pretends to be. What the program commits to is always the wave it can actually see; the far end stays a labeled forecast until it comes near enough to elaborate honestly, which keeps coordination anchored on promises that hold instead of dates that will certainly change.
How it works¶
- Set the wave horizon. Choose how far ahead is planned in detail versus left coarse, keyed to how fast uncertainty resolves in this domain.
- Elaborate the near wave. Decompose imminent work into committed tasks with real durations and hard milestones others can coordinate against.
- Placeholder the far wave. Keep distant work as coarse blocks with forecast dates explicitly labeled as forecasts, not commitments.
- Re-elaborate at the boundary. As each wave closes, detail the next using the durations and lessons execution just produced, rolling the detailed horizon forward.
Tuning parameters¶
- Wave length — how much is committed in detail at a time. Longer waves give more coordination stability but commit further into uncertainty; shorter waves stay honest but re-plan more often.
- Detail gradient — how sharply resolution drops from near to far. A steep gradient saves planning effort but leaves the middle distance thin; a gentle one plans more speculatively.
- Commitment labeling — how strictly near-term promises are distinguished from far-term forecasts. Blurring the two either over-commits to fiction or under-commits the near work others depend on.
- Re-elaboration trigger — whether the next wave is detailed on a schedule or on a readiness event (design freeze, phase gate passed).
- Freeze depth — how much of the near wave is locked against change, protecting imminent coordination from churn.
When it helps, and when it misleads¶
Its strength is refusing false precision: it spends planning effort only where it buys something, keeps commitments honest by distance, and lets each wave learn from the last — the discipline of progressive elaboration, planning in increasing detail as information becomes available.[n1] It fits long, uncertain efforts where a fully-detailed up-front plan would be fiction.
Its failure mode is a far horizon that is coarse and forgotten — placeholders that never get elaborated, so a long-lead item buried in a "phase block" is discovered too late to order. The classic misuse is treating far-term forecast dates as if they were commitments, so stakeholders bank on numbers the method explicitly labeled provisional. A quieter trap is letting waves slip without re-elaborating, so the plan is perpetually detailed only for work already underway. The guarding discipline is to keep the commitment labels honest (forecast versus promise), scan far-wave placeholders for long-lead dependencies that must be acted on early despite the coarse plan, and elaborate the next wave before the current one ends so the detailed horizon never collapses to the present.
How it implements the components¶
deadline_milestone_and_commitment_structure— its core: near-term milestones are firm commitments while far-term dates are explicitly labeled forecasts, making commitment hardness a function of distance.duration_effort_and_elapsed_time_model— each wave's detailed durations are estimated from what execution has revealed, so estimates sharpen as uncertainty resolves rather than being guessed up front.temporal_objective_and_outcome_horizon— the plan is organized around the outcome horizon, with detail decaying across it in step with knowability.
It does not implement adaptive_rescheduling_and_exception_policy — reactively re-solving the schedule when a disturbance fires is Event-Triggered Rescheduling Controller, its nearest twin; rolling-wave re-plans on planned wave boundaries as uncertainty resolves, not reactively on exceptions.
Related¶
- Instantiates: Temporal Orchestration Design — supplies the progressive-planning layer that matches commitment to knowability over the horizon.
- Consumes: Dependency Network and Critical-Path Map supplies the dependency structure each wave is elaborated against.
- Sibling mechanisms: Event-Triggered Rescheduling Controller · Cadence Calendar with Adaptation Rule · Dependency Network and Critical-Path Map · Buffer and Float Allocation Model · Phase-Alignment and Staggering Plan · Time-Window and Readiness Gate · Timebox and Timeout Rule · Temporal Scenario and Stress Test · Cycle-Time and Lag Retrospective
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Rolling-Wave Schedule operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it plans the imminent wave in firm, committed detail and leaves the far horizon deliberately coarse, then re-elaborates each wave as uncertainty resolves — matching plan resolution to what is actually knowable.
Independent corroboration: The frozen evidence defines Rolling-Wave Schedule as 'Plans the imminent wave in firm, committed detail and leaves the far horizon deliberately coarse, then re-elaborates each wave as uncertainty resolves — matching plan resolution to what is actually knowable', so its operative form is Representation, Specification & Plan.
Nearest alternative: Protocol, Workflow & Routine — Rolling-Wave Schedule includes features of a repeatable ordered procedure or handoff sequence that coordinates action, but its defining operation is a static representation, map, specification, schema, or prospective plan that externalizes information.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Rolling-wave planning with detailed near-term and coarse long-term work is a canonical project-management method.
Related originating lineages:
- Futurism & Strategic Foresight — Uncertainty-sensitive horizon treatment independently motivates coarse distant plans.
- Operations Research — Rolling-horizon scheduling materially formalizes successive plan elaboration.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: plans the imminent wave in firm, committed detail and leaves the far horizon deliberately coarse, then re-elaborates each wave as uncertainty resolves — matching plan resolution to….
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of alternate origin disagreement, domain reach disagreement starts from reviewer_a’s mechanism-specific evidence: Rolling-wave planning with detailed near-term and coarse long-term work is a canonical project-management method. Reviewer A proposed alternates=futurism_foresight, operations_research, origin_mode=convergent, domain_reach=multi_domain, and encyclopedia_synthesis=false; reviewer B proposed alternates=operations_research, systems_cybernetics, origin_mode=convergent, domain_reach=universal, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (futurism_foresight, operations_research, systems_cybernetics) without an arbitrary cap, selects origin_mode=convergent to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=false from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Progressive elaboration is the project-management practice of planning work in increasing detail as more information becomes available, so imminent activities are specified precisely while distant ones remain intentionally coarse until they come near enough to plan credibly. ↩