Executing: coordinate work, engage stakeholders
What you'll be able to do
Execution is when the team builds. The PM clears the path and runs change requests through the proper channel.
- Execution = coordinate + engage + produce. PM facilitates, doesn't build.
- Change requests must go through integrated change control. No exceptions.
- Adaptive vs predictive execution differs in cadence and visibility, not in goal.
Executing performs the work defined in the plan: coordinating resources, managing stakeholder engagement, and producing deliverables. It is also where the choice of approach (predictive, adaptive, or hybrid) becomes most visible — predictive execution is plan-driven and milestone-paced; adaptive execution iterates around feedback loops and demos.
The PM's job in execution is largely facilitation and integration, not building. The PM enables the team to do the work: removes blockers, integrates outputs, handles change requests, and keeps stakeholders aligned. In an adaptive context this looks like servant leadership; in a predictive context it looks like classical project coordination — but the underlying activity is the same.
Change requests are the most-tested artefact in Execution scenarios. PMI's pattern is rigid: any change goes through the integrated change control process. The PM evaluates impact (Holistic View!), the appropriate authority (Change Control Board, sponsor, or PM depending on threshold) decides, and the plan + baselines are updated only after approval.
Key points
- Execution = coordinate + engage + produce. PM facilitates, doesn't build.
- Change requests must go through integrated change control. No exceptions.
- Adaptive vs predictive execution differs in cadence and visibility, not in goal.
Ask a PMBOK tutor
Paste this lesson plus your question into a fresh chat. Claude is a strong PMP study coach — try asking for additional worked examples, a comparison across PMBOK editions (6e vs 7e vs 8e), or a tougher scenario.