Identify Risks Process: Tools, Inputs, and Outputs
PMBOK v8 Definition
The Identify Risks process is the process of identifying individual project risks and sources of overall project risk, and documenting their characteristics. It belongs to the Planning Process Group and the Project Risk Management Knowledge Area. The purpose is to identify suitable ways to address overall project risk and individual project risks.
Why It Matters for the Exam
This process appears frequently in PMI exam questions testing your ability to distinguish between risk identification inputs, tools, and outputs. Expect scenario-based questions where you must select the correct tool (e.g., brainstorming vs. checklists) or identify which document is updated during this process. Approximately 5-7% of risk management questions focus specifically on Identify Risks.
Key Points to Remember (for the exam)
- Main Inputs: Project management plan (requirements management plan, schedule management plan, financial management plan), risk register, risk report
- Main Tools & Techniques: Expert judgment, data gathering (brainstorming, checklists, interviews), data analysis
- Main Outputs: Risk register updates, risk report updates, project document updates (assumption log, issue log, lessons learned register)
- Common Confusion: Confusing the risk register (output of Identify Risks) with the risk report (separate document tracking overall project risk exposure)
- Critical Distinction: Brainstorming is a data gathering technique, not a data analysis technique
- Exam Trap: The risk register is an input to later risk processes but is first created as an output of Identify Risks
- Key Document Updates: Assumption log, issue log, and lessons learned register are all updated during this process
Typical PMI Exam Example
A project manager is leading a new office building construction project. During a team meeting, she asks team members to generate as many potential risks as possible without criticism. Which tool and technique is being used?
Answer: Data gathering – Brainstorming (as shown in Section 5 – Tools and Techniques of PMBOK v8)
PMI Exam Traps
-
Trap: Thinking checklists are part of data analysis Reality: Checklists belong to data gathering, not data analysis
-
Trap: Confusing risk register with risk report Reality: The risk register documents individual risks; the risk report documents overall project risk exposure
-
Trap: Assuming the risk register is only an output Reality: The risk register is an output of Identify Risks but becomes an input to subsequent risk processes
-
Trap: Believing all project documents are updated Reality: Only specific documents are updated: assumption log, issue log, and lessons learned register
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Risk Register | Primary Output | Created in Identify Risks; used as input in Perform Qualitative Risk Analysis |
| Risk Report | Output/Input | Updated in this process; documents overall project risk exposure |
| Assumption Log | Project Document Update | Assumptions identified as risks are documented here |
| Lessons Learned Register | Project Document Update | Records lessons from risk identification for future projects |
Quick Review Questions
-
Which data gathering technique involves generating ideas without criticism during risk identification?
-
What are the three main categories of tools and techniques used in the Identify Risks process?
-
Which project management plan components are listed as inputs to Identify Risks?
-
What is the difference between the risk register and the risk report?
-
Which three project documents are updated as outputs of the Identify Risks process?
PMBOK v8 Reference
Section 5 – Tools and Techniques (Page 179) – Identify Risks process inputs, tools and techniques, and outputs as shown in the PMBOK v8 framework diagram