Navigate Complexity

PMBOK note: This was a standalone principle in PMBOK 7 — “Navigate Complexity.” In PMBOK 8 it was consolidated into Adopt a Holistic View (systems thinking across interconnected domains). The concept is fully tested; the label changed.

Definition

Navigating complexity means recognizing and addressing sources of project complexity — human behavior, system behavior, ambiguity, and technical/organizational interdependencies — and adjusting the approach accordingly. Complexity is not the same as complication: complicated problems have knowable solutions; complex problems require ongoing adaptation as understanding evolves.

Related concepts

• Adopt a Holistic View
• Tailoring
• Business Environment Domain
• Risk Domain

Exam angle

• Complexity is a driver for choosing adaptive or hybrid approaches — high complexity + unclear requirements = adaptive
• Complex projects require more frequent stakeholder engagement and tighter feedback loops, not more detailed upfront plans
• Complexity sources: many stakeholders, unclear requirements, regulatory environment, novel technology, cultural/geographic spread — recognizing these in scenarios is the first step to the right answer

My notes