1.2.6: Planning or the Plan?

Progressive Elaboration and Real-World Adaptation 

There is an old military saying worth keeping close in portfolio work. No plan of operations survives with any certainty past the first encounter with the enemy. Only a layman believes a campaign unfolds exactly as it was drawn up in advance. In plain terms, no plan survives contact with real life. This principle, often attributed to the German field marshal Helmuth von Moltke, is not an excuse for sloppy planning. It's a warning against treating any plan as sacred, a distinction worth holding onto carefully, since the two get confused more often than they should.

Important Concept: Moltke's Principle

No plan survives contact with real life. This doesn't mean planning is wasted effort, it means planning has to be paired with a genuine willingness to adapt once reality starts producing information the original plan couldn't have accounted for. Adaptive portfolio management and continuous strategic feedback loops exist precisely because Moltke's observation about military campaigns turns out to be just as true about a portfolio's roadmap.

There's a related insight buried inside the military analogy that's easy to miss on a first read. The value was never really in the specific plan of operations itself, since that plan was expected to unravel the moment real conditions intruded. The value was in the planning, the process of thinking through objectives, resources, contingencies, and dependencies carefully enough that the people involved understood the situation deeply and could think clearly once circumstances shifted. A commander who has planned rigorously can improvise intelligently when the battlefield changes, precisely because the planning process built the judgment needed to adapt, even though the specific plan it produced is now obsolete. A portfolio manager is in the same position. The roadmap itself may need rewriting by month six, but the rigor that went into building it, the strategic clarity, the resourcing logic, the assumptions surfaced and tested, is what actually equips the portfolio manager to adapt well when those assumptions inevitably prove incomplete. Planning is more important than the plan precisely because planning builds the capability to respond, while the plan itself is only ever a snapshot of what that capability produced at one particular moment in time.

That same tension between disciplined upfront planning and the near certainty that reality will diverge from it has a formal name in portfolio management, and understanding it changes how a portfolio manager should think about every roadmap they ever build.

What Progressive Elaboration Actually Means

Progressive elaboration is the formal name for how portfolio managers deal with this reality. It refers to the continuous refinement and deepening of project understanding as more information becomes available over time, rather than treating an early-stage plan as a fixed and final description of how work will unfold. A project or a portfolio component is usually only fully understood once it's close to finished, or after it has actually finished, which is a genuinely uncomfortable truth for anyone who wants certainty at the outset of a major investment decision.

Early plans are necessarily rough. As work proceeds, the team learns more, and that new knowledge should feed back into the plan, refining it rather than being discarded because it doesn't match what was originally assumed. It's worth acknowledging plainly that a component's true nature, its real risks, its actual challenges, are often only fully understood near or after completion, not at the moment funding was approved. A portfolio manager who expects full clarity at Selection, the phase covered earlier in this book where components are chosen and aligned to strategy, is expecting something that the nature of complex work simply doesn't provide.

What Month One Couldn't Have Known

A portfolio manager approves a market expansion component in month one, built on the best available data about regional demand, competitor pricing, and regulatory requirements. By month six, the component's team has learned that a local regulatory body is drafting new requirements that weren't public knowledge at approval, that a key competitor has quietly shifted pricing in a way that changes the component's expected margins, and that the local talent pool needed to staff the expansion is thinner than initial research suggested. None of this reflects bad planning in month one. It reflects the simple fact that this information didn't exist, or wasn't accessible, until the team was actually operating in that market. A roadmap built in month one will almost certainly need updates by month six, not because the original planning was flawed, but because new facts have appeared that nobody could have known in advance.

This means portfolio managers have to be comfortable operating with incomplete information early on, treating that incompleteness as a normal condition of the work rather than a failure to be corrected through more upfront analysis. No amount of additional planning time in month one would have surfaced a competitor's pricing decision that hadn't been made yet. That comfort with incomplete information runs directly against a belief that tends to take hold once a governance board has formally signed off on a plan, and it's worth naming that belief directly before it quietly shapes how a portfolio manager behaves under pressure.

Myth: A Governance-Approved Roadmap Is a Locked Blueprint

Once a governance board has formally approved a portfolio roadmap, it's tempting to treat that approval as final, a contract that shouldn't be reopened without an extraordinary justification. A roadmap that never gets revisited after approval isn't evidence of a good plan, it's evidence that nobody has been checking it against reality, or that legitimate updates are being avoided out of a mistaken belief that revision itself signals failure. Progressive elaboration assumes the opposite: that a roadmap needing updates by month six is a sign the organization is learning as it should, not a sign the original planning process broke down.

That myth is worth dismantling directly, because a portfolio manager who internalizes it will hesitate to bring legitimate new information back to governance, worried that proposing a change looks like an admission of poor planning rather than what it actually is, evidence that progressive elaboration is working as intended. This same acceptance of continuous refinement, it turns out, isn't just a practical habit adopted informally by experienced portfolio managers. It's written directly into the major global standards that govern the discipline.

How Global Standards Handle Emergent Change

A portfolio manager should be able to align internal portfolio processes with globally recognized standards such as the PMI Standard for Portfolio Management and ISO 21504, and part of what makes that alignment meaningful is that these standards were built with exactly this reality in mind rather than in spite of it. The PMI Standard for Portfolio Management, ISO 21504, and IPMA guidance all build in mechanisms for continuous feedback and adjustment rather than treating a governance-approved roadmap as untouchable.

Cross-Framework Convergence on Adaptive Management

• PMI Standard for Portfolio Management: builds continuous monitoring and periodic realignment directly into its portfolio management processes, rather than treating governance approval as a final step.
• ISO 21504: frames portfolio management as an ongoing organizational capability requiring regular review, not a one-time planning exercise followed by pure execution.
• IPMA guidance: emphasizes competency-based adaptation, expecting portfolio leaders to actively adjust their approach as project and environmental conditions evolve.

Different frameworks use different language, but they all point at the same underlying truth about how real projects behave. That convergence across three independently developed standards is itself meaningful. When organizations working from different traditions and different regions all arrive at the same conclusion, that a portfolio's plan has to remain genuinely alive rather than locked at approval, it's a strong signal that this isn't a stylistic preference of any one methodology, but a structural feature of how complex, multi-component work actually unfolds in practice.

The takeaway is simple but easy to forget under pressure, especially the pressure of a governance meeting where stakeholders want confident, stable answers rather than an admission that the roadmap has shifted since last quarter. Rigorous upfront planning still matters. It gives the organization a starting point and a shared language, a baseline against which progress and deviation can actually be measured. But the plan has to stay alive. Portfolio leaders must balance rigorous upfront planning with the agility to pivot and reallocate resources as real-world constraints emerge, and portfolio leaders who treat their roadmap as a living document, rather than a locked contract, are the ones who actually deliver value when the real world inevitably shows up with surprises no amount of month-one planning could have anticipated.