2.7 Removing Impediments

Project Management Professional PMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Fundamentals

1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam

2 Chapter 2: People Domain Part 1

2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments

3 Chapter 3: People Domain Part 2

3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence

4 Chapter 4: Process Domain - Planning

4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement

5 Chapter 5: Process Domain - Execution & Control

5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure

6 Chapter 6: Business Environment Domain

6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change

7 Chapter 7: Agile & Hybrid Approaches

7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools

8 Chapter 8: Predictive (Waterfall) Approaches

8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control

2.7 Removing Impediments

Key Takeaways Explain This Topic AI

Impediments are anything blocking or significantly slowing team progress, including physical, dependency-related, or skill-related blockers

Servant leaders prioritize removing obstacles that hinder team performance rather than controlling team work

Not all impediments require project manager intervention - teams should be empowered to resolve what they can

Escalation paths should be used for blockers outside the project manager's authority or unresolvable by the team

• Impediments should be prioritized based on their impact on critical path tasks and high-risk activities
• Last updated: October 2026

Addressing and removing impediments, obstacles, and blockers was People Task 7 in the 2021 ECO. The 2026 ECO moves it to Business Environment Task 4, "Remove impediments and manage issues." When team members encounter barriers that slow or stop their progress, the project manager must act swiftly to clear the path. This is servant leadership in action - putting the team's needs first by ensuring they have what they need to succeed.

What Are Impediments?

Impediments (also called obstacles or blockers) are anything that prevents the team from making progress or significantly slows them down.

Types of Impediments

• Type Description Examples
• Physical Tangible barriers Waiting for equipment, unavailable workspace, broken tools
• Dependency-Related Waiting on others Pending approvals, work from other teams, external vendor deliveries
• Skill-Related Competency gaps No one has the required expertise, training needed
• Process-Related Bureaucratic barriers Complex approval workflows, excessive documentation
• Technical Technology issues System outages, integration problems, performance issues
• Resource Insufficient resources Budget constraints, understaffing, competing priorities
• Organizational Company-level barriers Conflicting policies, unclear authority, political resistance
• The Servant Leader Approach

In servant leadership, removing impediments is a primary responsibility. The project manager serves the team by ensuring obstacles are cleared.

Servant Leadership vs. Traditional Management

• Traditional Manager Servant Leader
• Controls team work Facilitates team success
• Directs what to do Asks "what do you need?"
• Team serves manager's goals Manager serves team's needs
• Takes credit for success Gives credit to team
• Blames team for failures Takes accountability
• Key Mindset Shifts
• From "What have you done?" to "What's in your way?"
• From directing work to removing barriers
• From solving problems for the team to enabling the team to solve problems
• Identifying Impediments

Impediments must be identified before they can be addressed. Common discovery methods include:

Proactive Identification

• Method Description
• Daily Stand-ups Team members report blockers each day
• Retrospectives Team reflects on obstacles encountered
• One-on-Ones Individual conversations surface issues
• Observation Notice when work is slowing or stopping
• Impediment Boards Visual tracking of known blockers
• Questions to Uncover Impediments
• "What's preventing you from making progress?"
• "What would help you work more effectively?"
• "Is there anything blocking the team?"
• "What frustrations are you experiencing?"
• "What do you need that you don't have?"
• Prioritizing Impediments

Not all blockers have equal impact. Prioritization ensures the most critical impediments are addressed first.

Prioritization Criteria

Criterion High Priority If...

• Critical Path Impact Blocker affects tasks on the critical path
• Number of People Affected Multiple team members are blocked
• Risk Level Impediment threatens project success
• Duration Blocker has persisted for a long time
• Escalating Consequences Impact worsens if not addressed quickly
• Prioritization Matrix

• Impact Urgency Priority
• High High Immediate action
• High Low Schedule soon
• Low High Address quickly but simply
• Low Low Monitor or defer
• Resolution Approaches

Not every impediment requires the same approach. The servant leader must choose the appropriate intervention level.

Team Self-Resolution

When to empower the team:

• Team has the skills and authority to resolve
• Resolution builds team capability
• Impediment is within team's scope

How to support:

• Provide guidance without taking over
• Offer resources the team needs
• Check in on progress
• Direct Resolution

When the project manager should act:

• Team lacks authority or access
• Speed is critical
• Cross-functional coordination needed
• Organizational barriers require senior intervention

Actions:

• Negotiate with other managers
• Secure resources
• Remove bureaucratic barriers
• Make decisions within authority
• Escalation

When to escalate:

• Blocker is beyond your authority
• Resolution requires executive decision
• Significant budget or scope impact
• Ongoing conflict with other departments

Escalation Best Practices:

• Clearly describe the impediment and its impact
• Explain what has already been tried
• Propose possible solutions
• Specify what decision or action is needed
• Escalation Paths
• Common Escalation Points

• Level When to Use Types of Issues
• Project Sponsor Major decisions, scope changes Budget, scope, strategic direction
• Steering Committee Cross-project issues, governance Priorities, resource conflicts
• Functional Managers Resource availability Team member assignments
• PMO Process issues, methodology Standards, templates, tools
• Executive Leadership Organizational barriers Policy changes, strategic conflicts
• Escalation Is Not Failure

Escalation is a legitimate project management tool, not a sign of weakness. Senior leaders have the authority and influence to remove barriers that project managers cannot. However:

• Don't escalate trivial issues
• Attempt resolution before escalating
• Provide clear information and recommendations
• Follow up on escalated items
• Impediment Management Process
• Ongoing Impediment Tracking

• Step Activity
• 1. Capture Record impediments when identified
• 2. Assess Determine impact and priority
• 3. Assign Identify who will address it
• 4. Act Take resolution actions
• 5. Follow Up Verify resolution and close
• Visual Management

Many teams use impediment boards or blocker logs :

• Impediment Impact Owner Status Next Action
• Server access pending 3 devs blocked PM In progress Follow up with IT today
• Unclear requirements Sprint at risk PO Escalated Meeting with stakeholder
• Missing test data Testing delayed QA Lead Open Request from data team
• Common Impediment Patterns

• Pattern Description Solution Approach
• Approval Bottlenecks Waiting on slow approvers Pre-negotiate authority, escalate
• Resource Conflicts Multiple projects need same people Work with PMO, prioritize
• Technical Debt Legacy issues slowing work Allocate time for remediation
• Knowledge Silos Only one person has the skills Cross-training, documentation
• Environmental Issues Tools, systems, workspace problems IT support, workspace improvements
• Key Points for the PMP Exam
• Impediments block or slow team progress - they must be actively managed
• Servant leadership focuses on removing obstacles for the team
• Not all impediments require PM intervention - empower teams when appropriate
• Prioritize based on impact - address critical path and high-risk blockers first
• Escalate when necessary - use sponsors and executives for barriers beyond your authority
• Track and follow up - ensure impediments are actually resolved

Loading diagram... Impediment Resolution Decision Flow