Coarse-to-Detailed Planning¶
Planning method — instantiates Progressive Fidelity Increase
Starts with rough plans, estimates, or schedules and adds task detail, dependencies, resource constraints, and contingencies as commitment approaches.
A plan does not need to be detailed everywhere at once — it needs to be detailed where a decision is about to be made. Coarse-to-Detailed Planning phases the fidelity of a plan against time-to-commitment: the near horizon is elaborated down to tasks, dependencies, resource loading, and contingencies, while the far horizon is left as deliberately coarse summary blocks, and detail is pulled forward only as work packages approach the point where they will actually be executed and money committed. Its organizing axis is not evidence or realism-of-representation but proximity to commitment: the closer a chunk of work gets to happening, the more its plan is filled in, because that is when the estimate can be made credibly and when precision starts to pay. Detailing the far future is not just wasted effort — it manufactures false precision that will be re-torn-up when reality intervenes.
Example¶
A transit authority is planning a four-year light-rail extension. The temptation is to produce, on day one, a Gantt chart with every task through ribbon-cutting. Coarse-to-Detailed Planning refuses that. Year one — utility relocation, land acquisition, preliminary engineering — is planned to the week: named tasks, crew assignments, permit dependencies, a two-week weather-contingency buffer on the river crossing. Years three and four — station fit-out, systems commissioning, operational testing — exist as a handful of coarse summary bars with rough duration and budget envelopes and nothing more.
As the program runs, a rolling look-ahead window (roughly the next quarter) is the thing that gets detailed each month. When station fit-out crosses into that window — about twelve weeks out — the planning team breaks it down: platform finishes, fare-gate installation, the dependency on the signaling contractor finishing first, a contingency for the elevator lead-time that always slips. The far horizon is refreshed, not fabricated. The payoff shows up when the signaling contractor announces a delay: because station fit-out was only just being detailed, the reshuffle costs an afternoon of re-planning rather than the invalidation of a two-year task network that had been lovingly built on sand.
How it works¶
The method is a discipline about when detail is added, not merely that it is:
- A look-ahead window defines the commitment frontier. Work inside the window is planned at execution fidelity; work beyond it stays as rolled-up summary. The window moves forward with calendar time.
- Detail is pulled, not pushed. A work package earns its breakdown by entering the window (or by a funding gate committing it), not because the planner has spare time or a stakeholder wants a fuller-looking chart.
- Far work is held as placeholders on purpose. Coarse blocks carry an envelope estimate and an explicit "to be detailed later" flag, so nobody mistakes the absence of tasks for the absence of work.
- Re-planning is expected. Because far detail was never committed, adjusting it is cheap; the plan is designed to absorb change at the frontier rather than to resist it everywhere.
Tuning parameters¶
- Look-ahead window width — how far ahead the plan is detailed. A wider window buys more coordination lead-time but detailing volatile work that will change; a narrower window stays cheap and accurate but can under-warn on long-lead dependencies.
- Detailing granularity — how finely near-term work is broken down (summary tasks vs. sub-daily activities). Finer granularity improves control but raises the planning burden and the re-work when things move.
- Refresh cadence — how often the window rolls and far blocks are revisited. Frequent refresh keeps the plan live; infrequent refresh saves effort but lets the frontier go stale.
- Contingency depth — how much buffer and how many named fallbacks are attached to near-term tasks. More depth absorbs shocks but pads the schedule and can hide slack-hoarding.
- Commitment trigger — what event promotes a coarse block to detailed status: entering the window, a gate approval, or a long-lead procurement deadline.
When it helps, and when it misleads¶
Its strength is that it aligns planning effort with the moment planning is most accurate and most consequential, and it keeps a long program legible without pretending to a precision it cannot have. This is the discipline of rolling-wave planning[n1]: elaborate imminent work, keep distant work coarse, and let the wave advance.
It misleads when the coarse far-horizon blocks are treated as reliable rather than as placeholders — a summary bar with a confident-looking budget invites stakeholders to commit to a number that was never engineered, and a long-lead dependency buried in an undetailed block can ambush the program precisely because it was never surfaced. The classic misuse is the inverse failure: detailing everything up front to satisfy a demand for a "complete plan," then defending the fictional task network long after events have overtaken it — sunk-cost planning. The guarding discipline is to keep an explicit register of which blocks are still coarse and to scan the far horizon specifically for long-lead items that must be pulled forward early even though the rest of their block stays rough.
How it implements the components¶
Coarse-to-Detailed Planning fills the when-to-add-detail components of the archetype, tuned to a plan's commitment timeline:
detail_addition_rule— governs which details enter the next wave (task breakdown, dependencies, resource loading, contingencies) and which stay suppressed as summary bars.escalation_criterion— the promotion trigger: a work package is detailed when it crosses into the look-ahead window or a funding gate commits it, not on preference.fidelity_cost_budget— caps the planning labor itself, so the team does not burn hours engineering work that will be re-torn-up before it is executed.stop_or_defer_rule— holds far-horizon work as coarse placeholders, deferring its elaboration until it is near enough to plan credibly.
It does not carry a core_reference or produce a handoff_artifact — those belong to Design Mockup to Production Path, which ramps a specific artifact toward a deliverable — and it maintains no comparability_baseline across stages, which Staged Research Model uses to keep findings commensurable.
Related¶
- Instantiates: Progressive Fidelity Increase — raises the fidelity of a plan in time-phased waves rather than all at once.
- Sibling mechanisms: Design Mockup to Production Path · Engineering Review Gate · Model Calibration Increment · Progressive Policy Pilot · Staged Research Model
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Starts with rough plans, estimates, or schedules and adds task detail, dependencies, resource constraints, and contingencies as commitment approaches, making its operative form a non-executable information artifact that externalizes static or prospective structure.
Independent corroboration: The frozen evidence defines Coarse-to-Detailed Planning as 'Starts with rough plans, estimates, or schedules and adds task detail, dependencies, resource constraints, and contingencies as commitment approaches', so its operative form is Representation, Specification & Plan.
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: Project management established rolling-wave planning: detailed near-term work and deliberately coarse far-horizon packages elaborated near commitment.
Related originating lineages:
- Operations Research — Scheduling and resource planning supply dependencies and capacity constraints.
Review resolution: Both reviewers agree on organizational_management as primary. Reading the mechanism confirms that its defining operation belongs to that lineage; the final record retains operations_research only as materially formative origin and keeps present-day application breadth separate from provenance.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Rolling-wave planning — a project-management technique (formalized in the PMI/PMBOK body of knowledge) in which imminent work is planned in fine detail while work further out is left at a coarse, progressively-elaborated level. It is the direct ancestor of this mechanism's commitment-phased detailing. ↩