Implement Risk Responses is where planned responses get carried out. It exists because many projects analyze and plan risk thoroughly, then fail to act — the register looks healthy while nothing actually changes. This process closes that gap by ensuring response owners do what was agreed.
It runs throughout the project as risks evolve. The PM relies on influencing skills to get risk owners to follow through, since responses often sit with people the PM does not directly manage.
Common pitfalls. A well-maintained register with responses no one executes; responses without committed owners; reacting only when a risk has already become an issue; and failing to track whether responses are actually working.
Inputs, Tools & Techniques, and Outputs
Inputs
- Project management plan
- Project documents
- Organizational process assets
Tools & Techniques
- Expert judgment
- Interpersonal and team skills
- Project management information system
Outputs
- Change requests
- Project documents updates
How This Process Connects
Every process hands artifacts to other processes. Follow the flow of this one:
Where its inputs come from
- Develop Project Management Planproduces: Project management plan
Where its outputs go
- Perform Integrated Change Controluses: Change requests
More in Project Risk Management
In the Domains & Principles View
The PMBOK® Guide frames this work through performance domains and principles:
In the Eighth Edition
This process 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.