III.4 — Remove Impediments and Manage Issues
III.4 · Last updated: 24/08/2026
Where this task sits
III.4 — Remove Impediments and Manage Issues is a task in the Business Environment domain of the 2026 ECO. The domain carries 26% of the exam and holds eight tasks.
In the 2021 ECO, this topic was not here — it was not even in this domain.
The six enablers the ECO attaches to this task trace a loop: evaluate the impact of impediments, prioritize and highlight them, determine and apply an intervention strategy to remove or minimize them, continually reassess to make sure the team's impediments are being addressed, recognize when a risk becomes an issue, and work with relevant stakeholders on an approach to resolve the issues.
The move: from I.7 to III.4
| 2021 | 2026 | |
|---|---|---|
| Number | I.7 | III.4 |
| Domain | People | Business Environment |
| Title | Address and remove impediments, obstacles, and blockers | Remove impediments and manage issues |
This is the longest of the three moves between the 2021 and 2026 outlines: the topic travelled from People all the way to Business Environment, from one end of the domain order to the other.
The title grew, too. The 2021 wording listed only impediments; the 2026 wording adds issue management to it. The task now carries two distinct concepts, and the exam asks how they relate.
What the change of direction means: in 2021, clearing impediments was a leadership behavior that shielded your team. In 2026 the same work is a question of decision authority and organizational mechanisms — who actually has the power to remove which impediment.
Why the domain change matters
III.4's 2026 neighbors are III.1 Define and Establish Project Governance, III.2 Plan and Manage Project Compliance, III.3 Manage and Control Changes, and III.5 Plan and Manage Risk. All four ask one question from different angles: what happens when you hit something beyond the project team's authority.
The PMBOK® Guide draws the same connection. Among the responsibilities of the Governance Performance Domain it explicitly lists monitoring and managing internal and external dependencies, risks, issues, and escalations (PMBOK® 8, Guide p.15). Impediments and issues are a governance heading in PMBOK too.
If you build your study plan around domain weights, this topic moving out of the 33% People domain and into the 26% Business Environment domain changes the hours you give it.
🔴 Do not trust the number
The trap here is the most concrete one in the entire ECO, because the number I.7 belongs to two different topics in the two outlines:
- In 2021, I.7 was removing impediments. In 2026 that topic is III.4.
- In 2026, I.7 is helping ensure knowledge transfer. An entirely different task.
So a question tagged "I.7" is meaningless until you know which outline it was tagged against. The same ambiguity applies to the number III.4 itself: in 2021, III.4 was supporting organizational change, and in 2026 that topic is III.7 — Support Organizational Change.
In short, both this task's old number and its new number are in use for other topics. Match on the title, never the number. For the general shape of this trap and its other instances, see what changed in the 2026 PMP exam.
Impediment, obstacle, blocker: one concept, not three
The ECO title names three words at once, which sends people looking for three separate definitions. The Guide draws no such distinction: an impediment is an obstacle that prevents the team from achieving its objectives, and a blocker is another name for the same thing (PMBOK® 8, Guide p.268). The glossary entry for "blocker" simply points to "impediment" (PMBOK® 8, Guide p.266).
So do not try to build a hierarchy among these three words on the exam. The distinction that matters is not the type of impediment but the authority required to clear it.
The leadership side of the work is still there: the Guide notes that supporting team members through problem-solving and removing impediments builds a supportive culture and leads to a trusting, collaborative environment (PMBOK® 8, Guide p.90).
When a risk becomes an issue
This task's ECO wording says it outright: recognize when a risk becomes an issue. It is one of the distinctions the exam probes most often.
The Guide's definition is precise: an issue is a current condition or situation that may have an impact on one or more project objectives; it has already occurred and may require immediate action or management attention (PMBOK® 8, Guide p.93; glossary at Guide p.268).
The link and the difference sit in the same place: an issue may arise from a poorly managed risk — but an issue has already occurred or is still occurring, whereas a risk is a potential future condition that has not happened yet (PMBOK® 8, Guide p.93).
The practical consequence: if the event in the question stem has happened, you are in the issue log; if it has not, you are in the risk register. For the risk side in full, see III.5 — Plan and Manage Risk.
Two ways to clear an impediment: escalation and self-governance
The Guide splits this by approach, and the split explains most III.4 questions.
In predictive environments, escalation counts as a governance component. It is useful in hierarchical organizations where decision-making authority includes people outside the project team, or where higher-ranking individuals have a greater ability to remove persistent obstacles (PMBOK® 8, Guide p.13).
In adaptive environments, the mechanism is built from below: daily coordination meetings help teams maintain focus and alignment, and serve as a self-governing mechanism toward that end (PMBOK® 8, Guide p.34). The team operates with autonomy, and the impediment first becomes visible inside the team itself.
The Lead the Team process names both together: tracking team member performance, providing feedback, and resolving and escalating issues (PMBOK® 8, Guide p.84).
The exam logic follows: if the impediment is within the team's own authority, escalating is premature; if it exceeds that authority, not escalating is a delay.
Making impediments visible: the impediment list and the issue log
The ECO says "prioritize and highlight impediments," and the Guide's counterpart is a concrete visual tool. An impediment list is a chart showing a description of the impediment to getting work done, its severity, and the actions being taken to resolve it (PMBOK® 8, Guide p.214). All three columns map onto three of the ECO's enablers: evaluate the impact, prioritize, intervene.
On the issue side the artifact is the issue log — a project document where information about issues is recorded and monitored (PMBOK® 8, Guide p.123). The issue log is an input not only to this task but to the stakeholder and communication processes as well; issues do not stay sealed inside it.
The practical consequence: the answer to "what should the project manager do" is often to record it and make it visible first, and intervene second. An impediment nobody can see cannot be prioritized.
About the citations
All page numbers above refer to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."
⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:
- The Standard for Project Management — cited as Standard p.X
- A Guide to the Project Management Body of Knowledge — cited as Guide p.X
Every citation on this page comes from the second part, the Guide. The numbers are the book's printed page numbers.
This page explains the book; it does not replace it.
