Address and Remove Impediments, Obstacles, and Blockers for the Team
Introduction: Why This Matters
Even the strongest teams will face barriers. These can be organizational, technical, or interpersonal. A project manager’s leadership is measured not just by planning, but by the ability to clear the path so that the team can focus on delivery. Removing impediments is a cornerstone of servant leadership, and it is central to Agile, hybrid, and traditional projects alike.
On the PMP exam, this task is often tested in scenarios where progress is delayed by a blocker. The correct choice is usually the one where the project manager proactively removes or mitigates the barrier rather than ignoring, escalating too early, or pressuring the team.
Purpose and Objectives
Primary Purpose: Build skill in recognizing and addressing barriers to progress so projects maintain momentum.
Key Objectives:
- Identify common types of impediments, obstacles, and blockers.
- Apply structured approaches to remove or mitigate them.
- Use servant leadership to support the team’s ability to deliver.
- Know when to escalate versus when to resolve at your level.
- Build resilience by fostering a culture of proactive problem-solving.
Overview
Impediments can come from inside the organization, the technology, the people, or outside forces. The project manager’s job is to detect blockers early, remove what they can quickly, and escalate only when authority or access is limited.
- Four common sources: Organizational, technical, interpersonal, and external blockers.
- Three response modes: Direct action, facilitation, or escalation through defined pathways.
- Servant leadership lens: Clear the path so the team can deliver with focus.
Characteristics
- Proactive identification: Blockers are surfaced early through daily check-ins, standups, or feedback channels.
- Rapid response: The project manager removes friction quickly to protect delivery flow.
- Appropriate escalation: Escalation is used when the barrier is outside the project manager’s authority.
- Psychological safety: The team can raise blockers without fear of blame.
- Visible tracking: Impediments are logged and monitored to prevent repeat delays.
Practical Example
Context: A construction project faces delays because procurement has not approved critical equipment purchases.
Activities:
- Direct action: The project manager holds a direct meeting with procurement leadership to fast-track approvals.
- Escalation (if needed): The project manager partners with the sponsor to escalate systemic delays in the procurement process.
- Team reinforcement: The team sees obstacles are handled quickly, increasing confidence and morale.
Outcome: The project avoids costly downtime because the project manager proactively removes blockers and protects momentum.
Common Pitfalls
Blocker Handling Mistakes
- Pitfall: Ignoring small blockers until they become major delays. Prevention: Use frequent check-ins and address friction immediately.
- Pitfall: Blaming the team for delays driven by external constraints. Prevention: Own external barriers and remove them with urgency.
- Pitfall: Escalating too quickly, signaling low ownership and weak facilitation. Prevention: Resolve what you can first, then escalate through defined pathways.
- Pitfall: Failing to track impediments, leading to repeat problems and weak learning. Prevention: Log blockers in the issue log and review trends.
- Pitfall: Micromanaging blockers instead of enabling the team to surface and help solve them. Prevention: Create safety, clarify escalation rules, and empower reporting.
Sensei Tip : Treat blockers like fires. You do not wait for the weekly meeting to handle a fire. You clear it fast, then you document it so it does not happen again.
Exam Alert : If the option says “work overtime,” “wait until later,” or “just document it,” it is usually wrong. The exam favors immediate action to remove the blocker, and escalation only when authority is limited.
Exam Lens
Patterns on the PMP Exam:
- When work stalls, the project manager removes or mitigates the blocker quickly.
- Use servant leadership. Support the team rather than pressure or blame them.
- Escalate only when the blocker is outside your authority or access.
Sample Question
Question: During a sprint, the development team reports that a critical testing environment is unavailable, delaying progress. What should the project manager do first?
- Ask the team to work overtime to make up for lost time.
- Document the issue in the risk register and move on.
- Work with IT to resolve the environment issue quickly, escalating if needed.
- Wait until the next sprint to address the problem.
Correct Answer: C. Remove the blocker immediately by working with IT, and escalate only if it is outside the project manager’s authority.
Quick Recap Table
| Impediment Type | Example | PM Response | Exam Watch Point |
|---|---|---|---|
| Organizational | Approval delays | Facilitate or escalate | Avoid bureaucracy traps |
| Technical | System defects | Support resolution | Enable progress, do not delay |
| Interpersonal | Team conflict | Facilitate resolution | Do not ignore “soft” blockers |
| External | Vendor delay | Negotiate, escalate | Escalation is appropriate if beyond authority |
Key Takeaways
- Removing impediments is one of the project manager’s most critical responsibilities.
- Barriers can be organizational, technical, interpersonal, or external.
- Proactive identification and fast resolution maintain momentum.
- Servant leadership means clearing the path so the team can deliver.
- Exam answers favor action-oriented, enabling responses, with escalation only when needed.
Next Step
We will now move to Task 8: Negotiate Project Agreements, where you will learn how to secure alignment, set expectations, and create win-win outcomes with stakeholders, vendors, and partners.
Bibliography
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.