Projects rarely run exactly to plan. This principle is about designing for that reality: adaptability — the ability to respond to changing conditions — and resiliency — the ability to absorb an impact and recover quickly from a setback or failure. Together they help a project accommodate change and keep advancing.
A focus on outcomes rather than outputs makes both easier: when the team is anchored to the result rather than a fixed plan, it can change route without losing direction. Building in slack, options, and the capacity to learn turns disruptions into recoverable bumps rather than derailments.
Common misunderstanding. Adaptability and resiliency are not about abandoning the plan at the first sign of trouble. They are deliberate capabilities, built in advance, that let a team flex and bounce back without chaos.
Where This Principle Shows Up
The domains and knowledge areas where this principle does its heaviest lifting:
In the Eighth Edition
This principle describes the framework as set out in the Sixth and Seventh Editions. The Eighth Edition reorganized it into 6 principles, 7 performance domains and 40 processes.