Adaptive Planning: How to Plan When You Don't Know Everything
The traditional approach to project planning contains a hidden assumption that most project managers never examine: that you know enough at the start of a project to define its full scope, schedule, and budget with meaningful precision. On simple, well-understood projects with stable requirements, this assumption is reasonable. On complex projects — the kind involving new technology, significant organisational change, multiple interdependent workstreams, or domains where requirements emerge over time — the assumption is almost always wrong. The project manager who produces a detailed schedule and budget for a project that is genuinely uncertain has not eliminated the uncertainty; they have hidden it. Adaptive planning is the discipline of making that uncertainty visible and managing it explicitly, rather than pretending it does not exist.
Rolling wave planning
Rolling wave planning is the most widely applicable adaptive planning technique. The core principle is simple: plan the near term in detail and the far term at summary level, then roll the planning horizon forward as the project progresses and you know more. A project manager using rolling wave planning might have a detailed schedule for the next four to six weeks, a milestone-level plan for the next quarter, and a high-level roadmap beyond that. The schedule at each level reflects the actual precision of knowledge at that level — not a false precision imposed to satisfy a reporting requirement. As the project moves through each planning horizon, the next wave of detailed planning takes place when the team has the information needed to plan it credibly.
Planning horizons
Related to rolling wave planning but more structured, the planning horizons technique defines explicit boundaries between what is planned in detail and what is planned at summary level — and commits to replanning at those boundaries. A common implementation divides the project into phases, with detailed planning occurring only for the current phase and gate reviews at the end of each phase that include replanning the next phase with the knowledge gained. This is particularly useful in projects where phase outputs genuinely cannot be determined until the preceding phase is complete — research and development projects, large-scale systems integrations, and transformation programmes where the requirements emerge through doing the work.
Assumption-based planning
Every project plan contains assumptions — about resource availability, technology behaviour, stakeholder decisions that have not yet been made, and external conditions that may or may not hold. Assumption-based planning makes these assumptions explicit, tracks their validity over the course of the project, and triggers replanning when a critical assumption is violated. The practice requires three things: identifying the assumptions that underpin your plan at the time of planning, assigning someone to monitor each critical assumption, and agreeing in advance what will happen to the plan if a given assumption fails. Teams that do this have a mechanism for absorbing the uncertainty that inevitably materialises. Teams that do not document their assumptions are often unable to explain why their plans changed or agree on what the plan should be after it does.
Scenario planning for high-uncertainty projects
When the uncertainty in a project is not just about details but about fundamental direction — when the outcome of an early decision or external event will significantly change the nature of the remaining work — scenario planning provides a framework for planning across multiple futures simultaneously. Rather than a single baseline plan, the project maintains two or three scenarios: a base case, an optimistic case based on favourable assumptions, and a contingency case for adverse outcomes. Resources and timelines are defined for each scenario, and the decision points at which the team commits to one scenario are identified in advance. This is more complex to manage than a single baseline, but for projects where the uncertainty is genuinely scenario-level, it is far more honest and ultimately more manageable than a single plan that will be wrong in unpredictable ways.
Communicating adaptive plans to sponsors
The most common reason adaptive planning fails is not that the techniques do not work — it is that sponsors demand a fixed baseline regardless of whether the project conditions warrant one. Managing this requires an early, explicit conversation about what a plan is being asked to represent. A plan that claims certainty it does not have is not a reliable commitment — it is a prediction that will be wrong in specific and foreseeable ways. A rolling wave plan that is honest about what is known and what is not gives the sponsor something more valuable: early warning when conditions change, and confidence that the near-term commitments are grounded in real knowledge. The conversation is easier when you can show the sponsor that the alternative — a fixed plan built on uncertain assumptions — will produce the replanning events they are trying to avoid, just later in the project when they are more expensive.
When a fixed plan is appropriate
Adaptive planning is not always the right answer. Fixed-baseline planning is appropriate when the scope is genuinely well-understood, the technology is proven, the team has done similar work before, and the external environment is stable. Applying adaptive techniques to a simple, well-bounded project adds overhead without adding value. The skill lies in distinguishing which situation you are in — and being honest enough to choose the planning approach that fits the actual uncertainty of your project, rather than the one that produces the most reassuring presentation.
If your organisation is running complex projects where traditional planning approaches are producing plans that nobody believes, XNM's program and project delivery advisory works with project teams to implement planning practices that are honest about uncertainty and credible enough to build stakeholder confidence.