Task 29: Manage Project Issues
No matter how thorough the risk management plan, some risks will materialize. When they do, they become issues — events that have already occurred and are now actively impacting the project. ECO Task 29 — Manage Project Issues — addresses the project manager's responsibility to recognize when a risk has become an issue, attack it with the optimal response, and collaborate with stakeholders to resolve it effectively. This task is the practical counterpart to Task 17 (Assess and Manage Risks): risk management is about what might happen; issue management is about what has happened and demands immediate action.
Issue management is a test of the project manager's composure, judgment, and collaboration skills under pressure. When an issue arises, stakeholders look to the PM for decisive action. Delaying, ignoring, or escalating prematurely are all common mistakes that the PMP exam will test. This study guide covers the full lifecycle of issue management: from recognition through resolution, including the tools, techniques, and mindset that distinguish effective issue managers from reactive firefighters.
ECO Enablers for Task 29
The ECO defines three enablers for managing project issues. Together, they form a complete framework for issue response: recognize, attack, and collaborate:
- Recognize when a risk becomes an issue. The first and most critical step is detection. A risk is a potential future event; an issue is a current reality. The PM must monitor risk triggers and early warning indicators to catch the transition point as early as possible. The earlier an issue is recognized, the more response options are available.
- Attack the issue with the optimal action. Once recognized, the issue demands a response. The PM must evaluate response options quickly, select the most appropriate action given the circumstances, and implement it. Optimal action balances speed (the issue is already causing damage) with thoroughness (a hasty wrong response can make things worse).
- Collaborate with relevant stakeholders on the approach to resolve the issue. Issues rarely affect only the project manager. They ripple through the team, the sponsor, the customer, and other stakeholders. Effective resolution requires involving the right people — those with expertise, authority, or a stake in the outcome — to develop and execute the solution collaboratively.
These enablers align with PMBOK 7's Navigate Uncertainty principle and the Uncertainty performance domain. Issue management is where uncertainty becomes certainty — and where the PM's preparation meets reality.
The PMP exam tests this distinction relentlessly. A risk is an uncertain event that may occur in the future. It is documented in the risk register, assigned a probability and impact, and managed proactively through risk response strategies. An issue is an event that has already occurred and is now affecting the project. It is documented in the issue log, assigned an owner, and managed reactively through corrective action. When an exam scenario says "a key supplier might go bankrupt" — that's a risk. When it says "a key supplier has gone bankrupt" — that's an issue. The transition from risk to issue is the moment the uncertain event becomes certain. At that point, the risk register entry should be updated, and a new issue log entry created. The contingency plan for that risk becomes the starting point for the issue response.
Recognizing When a Risk Becomes an Issue
The first enabler — recognition — is deceptively simple but practically challenging. Issues don't always announce themselves with a clear signal. They often emerge gradually, and the PM must distinguish between normal variation, a risk trigger firing, and an actual issue materializing. Effective recognition depends on three elements:
1. Monitoring Risk Triggers
Every risk in the risk register should have defined triggers — early warning signs that indicate the risk may be about to materialize. For example, if the risk is "key developer may leave," triggers might include: the developer missing meetings, expressing dissatisfaction in one-on-ones, or updating their LinkedIn profile. When triggers fire, the PM should immediately review the risk, assess whether it has become an issue (or is about to), and prepare to implement the contingency plan.
2. Maintaining Situational Awareness
Not all issues come from identified risks. Some are genuine surprises — the "unknown unknowns." The PM must maintain awareness of the project's operating environment through regular team check-ins, stakeholder conversations, and monitoring of external factors. Daily standups in agile projects, team meetings in predictive projects, and informal communication are all detection mechanisms for emerging issues.
3. Distinguishing Issues from Non-Issues
Not every problem is an issue that requires formal management. A minor delay that the team can absorb within float is a variance, not an issue. An interpersonal disagreement that the team resolves on its own is a team dynamic, not an issue. The PM must apply judgment: does this event actually threaten project objectives? If yes, it's an issue; if no, it's noise. Over-managing minor problems creates unnecessary overhead; under-managing real issues allows them to fester.
Attacking the Issue with Optimal Action
The second enabler — attacking the issue — is where the PM's training and experience are tested. The response must balance speed with quality. The PMP exam expects you to know the structured approach to issue resolution:
| Step | Action | Key Questions |
|---|---|---|
| 1. Log It | Document the issue in the issue log immediately. Include: issue ID, description, date identified, impact assessment, priority, owner, and status. | What exactly happened? When was it detected? What is the immediate impact? |
| 2. Assess It | Evaluate the severity and urgency. Is this a critical issue that threatens project objectives, or a minor issue that can be managed within existing tolerances? Prioritize accordingly. | How badly does this affect scope, schedule, cost, quality, or risk? Can it wait, or does it demand immediate action? |
| 3. Activate Contingency Plan | If the issue corresponds to an identified risk, implement the pre-planned contingency response. This is the fastest path to resolution — the thinking was already done during risk planning. | Was this risk identified? Is there a contingency plan? Is the plan still appropriate given current conditions? |
| 4. Develop a Response | If no contingency plan exists (the issue was unforeseen), analyze the situation, generate response options, evaluate trade-offs, and select the optimal course of action. Involve subject matter experts. | What are the viable options? What are the pros and cons of each? Which option best balances speed, cost, and effectiveness? |
| 5. Implement | Execute the chosen response. Assign clear ownership, set deadlines, and communicate the plan to affected stakeholders. If the response requires a change request (e.g., additional budget or schedule), follow the governance process. | Who is responsible for each action? By when must it be done? Does this require a formal change request? |
| 6. Monitor and Close | Track the response to completion. Verify that the issue is actually resolved — not just temporarily suppressed. Update the issue log status to "closed." Capture lessons learned for future projects. | Is the issue fully resolved? Are there any residual or secondary issues? What can we learn from this? |
The "optimal" action is not always the most aggressive or the fastest. It is the action that best balances the project's constraints and objectives. Sometimes the optimal response to a minor issue is to accept it and adjust expectations rather than spend $50,000 to fix a $5,000 problem. The PM must apply judgment, not just process.
The PMP exam loves to present scenarios where the PM is under pressure to act immediately — and the wrong answer is often the one that skips critical steps. When an issue arises, the PM's first action is almost always to assess and document, not to implement a solution. If the question asks "What should the PM do first?" the correct answer typically involves logging the issue, assessing its impact, or consulting the issue log — not calling an emergency meeting, notifying the sponsor, or implementing a fix. Exceptions exist: if the issue threatens life safety or immediate project failure, action may take priority over documentation. But in most exam scenarios, following the structured process is correct. Rushing to a solution without assessment is a common trap answer.
Collaborating with Stakeholders on Issue Resolution
The third enabler — collaboration — recognizes that issues are rarely solved by the PM alone. Effective issue resolution is a team sport. The PM's role is to orchestrate the response, not to personally solve every problem. This means involving the right stakeholders at the right time:
Who to Involve and When
| Stakeholder | Role in Issue Resolution | When to Involve |
|---|---|---|
| Project Team | Provide technical expertise, implement solutions, identify workaround options. The team often has the deepest understanding of the problem and the best ideas for solving it. | Immediately — the team should be engaged as soon as the issue is logged and assessed |
| Subject Matter Experts (SMEs) | Provide specialized knowledge for complex or novel issues. SMEs may be outside the core project team. | When the team lacks the expertise to fully assess or resolve the issue |
| Sponsor | Provides authority, removes organizational obstacles, approves responses that exceed PM authority, and manages upward communication. | When the issue exceeds the PM's authority (per governance thresholds) or threatens project viability |
| Customer / End Users | Provide input on acceptable trade-offs, validate that the resolution meets their needs, and adjust expectations if necessary. | When the issue affects deliverables, quality, or user experience; when trade-offs must be negotiated |
| Governance Bodies (CCB, Steering Committee) | Approve changes required by the issue response (scope, budget, schedule changes). | When the response requires formal change approval per the governance structure |
| Other Project Managers | Coordinate responses when the issue affects shared resources, dependencies, or organizational-wide systems. | When the issue has cross-project impact or requires coordination across project boundaries |
Collaboration is not just about inviting people to meetings. It requires clear communication of the issue's impact, transparent sharing of response options and trade-offs, and genuine openness to input from those affected. The PM who tries to solve every issue in isolation will eventually face an issue they cannot solve — and by then, they will have alienated the people whose help they need. Collaboration builds trust and ensures that resolutions are robust, accepted, and sustainable.
The Issue Log: Your Central Tool
The issue log is the primary artifact for issue management, just as the risk register is for risk management. Every issue — whether it originated as a risk or emerged unexpectedly — should be logged, tracked, and eventually closed. A well-maintained issue log includes:
- Issue ID — A unique identifier for tracking and reference
- Description — What happened, when, and the immediate impact
- Category — Type of issue (technical, resource, stakeholder, external, etc.)
- Priority — Critical, High, Medium, or Low based on impact and urgency
- Owner — The person responsible for driving resolution
- Response Plan — The chosen course of action with tasks and deadlines
- Status — Open, In Progress, Resolved, or Closed
- Resolution Date — When the issue was fully resolved
- Lessons Learned — What the team learned that could prevent or improve response to similar issues in the future
On the PMP exam, questions about the issue log typically test whether you know to use it (rather than the risk register) when an issue materializes, and whether you update the risk register (to reflect that a risk has occurred) while also creating an issue log entry.
How Issue Management Questions Appear on the PMP Exam
Pattern 1: "A risk has materialized. What should the PM do first?"
Log it as an issue in the issue log, then assess the impact. If a contingency plan exists, implement it. If not, develop a response. The first step is always recognition and documentation — not action.
Pattern 2: "An unforeseen problem is disrupting the project. The team is panicking."
The PM should remain calm, log the issue, assess its impact, and engage the team in developing a response. Emotional composure and structured process are the correct answers. Panic-driven actions are always wrong.
Pattern 3: "The PM discovers an issue but the sponsor says to ignore it."
The PM should log the issue regardless and document the sponsor's direction. If the issue threatens project objectives, the PM has an ethical obligation to escalate through governance channels, even if the sponsor disagrees. The exam rewards integrity and process adherence over obedience to authority when the two conflict.
Pattern 4: "An issue requires a response that exceeds the PM's authority."
Follow the governance escalation path. The PM should present the issue, the recommended response, and the impact assessment to the appropriate governance body (CCB, steering committee, or sponsor) for approval. The PM should not implement an unauthorized response, even if it seems obviously correct.
Study Checklist for Task 29
- ✅ Can you clearly distinguish between a risk (future, uncertain) and an issue (present, certain) in exam scenarios?
- ✅ Do you know the six-step issue management process: Log, Assess, Activate Contingency, Develop Response, Implement, Monitor and Close?
- ✅ Can you identify the correct first action when an issue arises — logging and assessment rather than immediate solutioning?
- ✅ Do you understand when to involve the team, the sponsor, SMEs, customers, and governance bodies in issue resolution?
- ✅ Can you describe what belongs in an issue log and how it differs from a risk register?
- ✅ Are you prepared for exam scenarios where the PM is pressured to bypass process — and know that following process is almost always correct?
- ✅ Do you understand that the optimal action balances speed, cost, and effectiveness — not just whichever is fastest?
Issue management is where project management theory meets real-world pressure. The PMP exam tests not just your knowledge of processes, but your judgment under stress. Mastering Task 29 will serve you on the exam and in every project you lead. Continue to the ECO Study Guide Index to complete your study of the Process domain tasks.
← Back to ECO Study Guide Index | Practice Process Domain Questions →