Key Concepts
Issues and impediments are the day-to-day friction that can turn a smooth-running project into a crawling one. An issue is a problem that has already happened and needs action; an impediment is anything blocking the team’s progress. This task covers keeping them straight and dealing with them before they compound.
Throughout the life cycle of a project, we will face problems, shortcomings, and conflicts that arrive unexpectedly. These are issues, and they require action so they do not affect project performance. Impediments are a related but distinct category: anything that is blocking the team from making progress, or significantly slowing them down. Together, issues and impediments are the day-to-day friction that turns a smooth-running project into a crawling one if we ignore them.
Three terms get used loosely and are worth keeping straight:
- Risk – an uncertain future event that may or may not happen.
- Issue – a problem that has happened and needs action now.
- Impediment – something blocking or slowing the team. May be an issue, may be a structural problem in the way work flows.
Scrum Master or PM Is Not a Team Mom
There is a misconception that the project manager or Scrum Master should rush to remove every impediment as soon as possible. That behavior works against team empowerment, autonomy, and growth. The project manager is not a team mom, always rushing to help or to do unpleasant tasks. Servant leaders empower teams to remove their own impediments where possible and step in only on those the team genuinely cannot resolve. To optimize value delivery, we want to be building capabilities in teams. That may mean doing the work the first time if they are stuck, but encouraging them to do it themselves next time.
3.4.1 Evaluate the Impact of Impediments
Impediments large and small lurk in many places. Once we get accustomed to looking for them, we begin to see them everywhere. The trick is knowing which to address now and which can be tackled later. Some are very significant and act like boat anchors, pulling us down. Others are more like barnacles, individually small but significant when they accumulate. The first step is finding them; the second is evaluating which are critical.
Daily Stand-up
Agile teams often answer three questions during stand-up: what they have been working on, what they plan to work on next, and whether there are any blockers or impediments slowing progress. The third question is an open invitation to report impediments. Good team members look for ways to help. Project managers and Scrum Masters need to pay attention so they can assist when other team members cannot solve the problem. Answers to the first question can also reveal hidden impediments. If someone is on day three of a one-day task, maybe they are blocked by something. Consider following up after stand-up if you suspect more than just slow progress.
Observation
Are team members struggling? Does anyone seem extra frustrated, agitated, or upset? Maybe they are blocked by something. Changes in behavior or repeated failure to complete tasks can be signs of impediments. The skill in diagnosing lies in knowing when to enquire and when to hold back and just make a mental note. Micro-management is a powerful demotivator, so we do not want to intervene unnecessarily; neglect when people need help is just as bad. Common sense and experience working with team members help us tell a temporary setback from a real problem.
Value Stream Analysis
Value Stream Analysis is a method for analyzing a system’s current state and designing a better future state. It examines the steps to take a product or service from the start of a process until it reaches the customer. We can use value stream analysis to find queues, delays, and flow problems with our own development process. One recommended practice for lowering work in progress (WIP) is sometimes likened to lowering a river’s water level: it exposes the rocks and obstacles to flow. Once exposed, we can work on removing them. Reducing WIP can be achieved using Kanban boards with WIP limits on activities to control how many tasks can enter a step at once.
Backlog Assessment
Impediments are sometimes expressed as dependencies in the backlog. If “Filming the TV commercial” depends on “Approval of the marketing budget,” then the marketing-budget approval may soon become an impediment that blocks progress. We can reduce that risk by giving it plenty of lead time and chasing approvals early.
Task Age Analysis
Using Kanban boards or work-tracking applications, look for old or stuck items. These are items that have not changed state for a while, suggesting they may be blocked. Lean systems that track when work enters the system and when it changes state generate a wealth of data that helps find blocked work. Even without software, simply adding a tick mark to items on the taskboard at every stand-up will quickly identify old or stuck items. Anything stuck for longer than its estimated work time is probably blocked, or the team has too much WIP.
3.4.2 Prioritize and Highlight Impediments
Once we start looking for impediments, we will see them everywhere. Some will be minor, some will be significant. We need a way to prioritize impediments so we know which to focus our limited time and effort on.
Cost of Delay
Assigning financial values to impediments allows for an apples-to-apples comparison of impacts. Most impediments contain a time component: for every day this item is blocked, it costs the project or organization $X. Organizational costs are usually much higher than team burn rates. Projects are often undertaken to create a return on investment via a product or service or to satisfy a legal or regulatory requirement. The full cost of a delay might be a small project cost plus a large organizational cost because a competitor product gained traction or our organization was found in noncompliance.
Ask the Business
Just as we engage the business in defining scope and prioritizing the backlog, it is appropriate to discuss with them the relative priorities for impediment removal. I am not suggesting taking every small team issue to the business; they have their own problems and will reasonably wonder why we hired a project manager if we cannot solve any of them ourselves. For impediments that have a business outcome impact, it is worth getting their view on priority. They may already know that “Joe in Accounting is slow at providing information” and have plans to address it. They may prefer us to remove a different impediment first.
Ask the Team
Most impediments are raised by team members, so we should ask them which are the most critical to solve. Maybe the issue is temporary, and while “waiting for legal review has taken an extra week,” it is a one-off; the more significant concern is the “shortage of testing capacity.” Teams are usually closer to the work than project managers are, so engage team members in determining priority.
Impediments and problems should be discussed at the retrospectives that occur at the end of every sprint or iteration. At the retrospective, ask the team which issues they want to tackle in the next iteration. It is common for teams to use dot voting or other group decision-making approaches. “If you each get three votes to distribute across these impediments, where would you like us to focus?” is a good way to prioritize.
3.4.3 Determine and Apply an Intervention Strategy to Remove/Minimize Impediments
Once we have found the impediments and gained insights into their significance and priority, it is time to solve or at least reduce them. Where possible, encourage and empower the team to remove their own impediments first. Ask the team how they might solve the issue. If their solution is legal, morally responsible, and not against company policy, ask if anyone thinks they could do it. If we get a volunteer, empower them to do it and follow up on the result. Praise success in public and review failures privately. Building team capabilities is a core role of a servant leader.
Go See (Gemba Walk)
Assuming the team cannot fix the issue, it is up to us as a servant leader to try to remove the roadblock. The first step is to make sure we truly understand the issue. The lean approach “Gemba walk” means “Go see,” or more fully, “Go see, ask why, show respect.” It is a reminder for us to go to the place of the impediment and experience it. Only then will we fully understand what is happening, and we may realize we did not appreciate it initially.
There is a second benefit. The act of paying attention and taking the time to care about team-member issues helps people come to terms with them. Once we see how slow a machine is or how poor a vendor’s customer service has become, people feel heard and are no longer suffering alone. It does not solve the problem, but the first step in resolution is often admitting there is one.
Remove Obstacles
Now that we have seen the problem, the next step is to resolve it. Many problems are people problems. Maybe accounting is hard to deal with because nobody gives them notice of all these unplanned project requests. Use empathy and emotional intelligence to diagnose the problem and offer to do what you can to help. Often when people see you are interested in their perspective and willing to help, they will meet you halfway. Some impediments are physical: maybe Joe’s knob-coupler machine truly is bent and he needs a new one. Maybe an extra forklift driver or a faster production server is worth the expenditure given the full cost of delay. Maybe the problem is our process, and two levels of approval is overkill for business-requested features.
Any process changes need appropriate approval. In safety-critical environments such as nuclear waste handling or air traffic control, there will be rigorous processes in place. In most organizations, leadership will be glad people are taking the initiative, solving problems, and optimizing value delivery.
Escalate
Some things will be outside our circle of influence and will require escalation. If your organization has a project management office, that is a good place to start. They may know who to talk to and may know of other projects that have solved the same or similar problems. If your project is part of a large program, the program manager can help. If the project reports into a steering committee or sponsor group, those are appropriate escalation points. The executives and senior people in those roles usually got there by getting things done; they have the seniority and influence to remove obstacles team leads and project managers cannot.
We cannot take every little complaint to the executive, since they will reasonably wonder why they have employed a project manager. For blockers we cannot budge, executives may be the right answer. In agile environments, the Product Owner often has influence beyond the team and Scrum Master. They typically have legitimate business knowledge and connections, and a request from the business often gets a different response than the same request from the IT group.
3.4.4 Reassess Continually to Help Ensure Impediments, Obstacles, and Blockers for the Team are being Addressed
Minimizing the impact of impediments is the critical first step. Once we have put out the worst of the fires, we have to be on the lookout for the next flare-up.
Verify the Impediment Is Minimized
Ideally we want to avoid or eliminate roadblocks, but sometimes the best we can do is get through as quickly as possible with the fewest casualties. As with anything unpleasant, it is tempting to assume the problem has passed and move on. We should investigate and verify. Check back with whoever reported the impediment and see if it is fixed, better, or manageable. Some things need a second go-around. Do not assume the problem has gone away.
Visualize Impediments
Tracking impediments via big visible charts, flip charts, or shared web pages keeps them in mind. The taskboard with blocked items and days-stuck markers we discussed earlier is an example of an information radiator: a big visible chart that keeps important information in front of stakeholders. Other examples include a backlog of blockers, a Top-5 Impediments chart, a Help-Wanted list, or Solution Bounty posters.
Do not be afraid to show the things slowing your team down. Personnel issues should not be displayed publicly, but for technical and process problems, transparency works in our favor. The best leaders learn out loud: they admit what they do not know, ask for help, and are gracious enough to appreciate solutions from anyone trying to assist.
Single Point of Contact (SPOC)
We can reduce the number of potential delays by shielding the team from unnecessary interruptions. One way is to act as a single point of contact externally for the team. By asking that requests come through the project manager, we can shield the team from superfluous requests and forward along the genuine ones. This lets team members focus on the work and maintain some concentration and flow.
Monitor Impediments and Progress
Check the impediment backlog, task age, and blocked stories regularly. Check in with the team and ask how things are going. Listen for what people say and what they do not say. Ask if you can help with anything. Open questions at reviews and retrospectives such as, “If you had a magic wand to help us go faster, what would you wish for?” or “Where do we need the most help?” can surface the next set of impediments. Run more rounds of value stream mapping. Learn what your process efficiency is (the ratio of value-adding to total activity time) and ask how we can remove waste, queues, and excess work in progress. Do not become complacent. The theory of constraints teaches us that when we eliminate one constraint, we expose the next. We are never done improving the flow of value.
3.4.5 Recognize When a Risk Becomes an Issue
While risks are focused on the future and can be positive or negative, issues are focused on the present and are always negative. Risks are documented in the risk register and addressed via risk responses; issues are documented in the issue log and addressed via action plans and workarounds. So an issue is a current condition or situation that may affect the project objectives, and it is a problem the team has to address now.
Issues come from a variety of sources. Common areas include:
- Scope change control – we now need to deal with a change.
- Schedule control – something is running late.
- Cost control – something ended up costing more than we budgeted for.
- Project variance analysis – some project process or variable is outside tolerances.
- Quality – something needs redoing because of poor quality.
- Risk – “You know that thing we were concerned about? Well, it just happened.”
- Procurement – problems with a purchase or vendor.
- Communications – a communications breakdown leading to a problem.
Issue Log
The issue log is the document used to record and monitor project issues. It is used to track problems, inconsistencies, and conflicts that occur during the life of the project.
Data on issues typically includes:
- Issue type
- Who raised the issue and when
- Description
- Priority
- Who is assigned to the issue
- Target resolution date
- Status
- Final solution
The issue log is updated as a result of the monitoring and control activities that occur throughout the project’s life cycle.
3.4.6 Collaborate with Relevant Stakeholders on an Approach to Resolve the Issues
Asking for help is not a sign of weakness; it is a sign of respect and trust. New project managers sometimes think it is their job to solve all the problems and issues on a project. More accurately, it is the project manager’s responsibility to confirm issues get resolved. Often it is team members or other stakeholders who are best equipped to solve issues or create workarounds.
We should reserve asking the team for issues that go beyond basic PM tasks. When used appropriately, asking for help shows we respect people’s judgment and trust their recommendations. It is also a good way to empower team members. We do not need to implement every suggestion; we can thank people for their ideas and only act on the most promising ones.
Tips for Resolving Issues
- Encourage team members to promptly report potential issues to the project manager, who decides whether they belong in the issue log.
- Enter the issue into the issue log and assign an owner, priority, and due date.
- Monitor progress and discuss each open issue at status meetings.
- Develop a response (also called a workaround) and implement it.
- Assess the impact and effectiveness of the response.
- Close resolved issues and escalate issues that cannot be addressed within the project team.
Impediments Board
Agile teams may or may not use formal issue log documents. If not using an issues log or spreadsheet, an impediments list information radiator or impediments board is usually in place. The team adds issues as they occur to the leftmost “Issues Backlog” column. Based on factors such as priority, impact, and ease of implementation, issue cards move to “To Work on Next” and “In Progress.” When issues are addressed, they move to “Resolved.” Any issues that cannot be addressed by the team are escalated by the team lead, Scrum Master, or Product Owner, and the card moves to the “Escalated” column.
Maintaining a board of impediments raises visibility and awareness, which helps generate solution ideas. In a positive, supportive environment, having people aware of issues can influence behavior toward solutions. In hostile environments or those with poor worker relations, publicizing some issues could make things worse. Personnel issues, such as a team member handing in their resignation, should not be posted publicly.
Using an impediments board, the team keeps track of issues as they occur by adding them to the leftmost “Issues Backlog” column. Then, based on factors such as priority, impact, and ease of implementation, moves issue cards to the “To Work on Next” column or “In Progress” column. When issues are addressed, they are moved into the “Resolved” column. Any issues that cannot be addressed by the team are escalated by the team lead / Scrum master or Product Owner and the card moved to the “Escalated” column.
Maintaining a board of impediments raises visibility and awareness of current issues, which helps generate solution ideas.
(In a positive, supportive work environment having people aware of the issues might help influence behavior towards a solution or mitigating behavior. In hostile environments or those with poor worker relations publicizing issues could lead to behavior that makes things worse. Some personnel issues (such as Fred handing in his resignation) should not be posted publicly for privacy reasons.)
Daily Stand-ups and Retrospectives
The daily stand-up where people describe issues, impediments, or blockers is a great source for learning about potential problems. Pay attention to items that are slowing or preventing work. If they persist for more than a day or two, consider adding them to the issue log or board. Likewise, review open issues at retrospectives. Ask the team if there are activities or experiments we could undertake in the next iteration to resolve or lessen any of them. For issues closed this iteration, report and thank the relevant stakeholders for their efforts.
Deliverables and Tools
- Issue Log – The document used to record and monitor problems, inconsistencies, and conflicts during the project. Captures issue type, who raised it and when, description, priority, owner, target date, status, and final resolution.
- Impediments Board / Impediments List – An information radiator showing impediments by status, typically with columns for Backlog, To Work on Next, In Progress, Resolved, and Escalated.
- Top-5 Impediments Chart – A visible list of the most significant impediments currently affecting the team, used to focus attention and help generate solution ideas.
- Daily Stand-up – A short team meeting where work in progress, planned work, and blockers are reviewed. A primary source for surfacing impediments early.
- Retrospectives – End-of-iteration sessions where the team reflects on impediments and selects which to tackle in the next iteration, often using dot-voting to prioritize.
- Value Stream Analysis / Value Stream Map – A method for examining the steps from start to customer delivery to find queues, delays, and flow problems.
- Kanban Board with WIP Limits – A board showing work flowing through defined steps, with limits on the number of items allowed in each step. Surfaces blocked work and reduces work in progress.
- Task Age Analysis – Examination of how long work items have been in their current state. Items stuck longer than their estimated work time are likely blocked.
- Cost of Delay – A financial value placed on each day an impediment goes unresolved. Used to prioritize impediment removal on the same basis as project work.
- Gemba Walk – A lean technique meaning “go see, ask why, show respect.” The project manager goes to the place of the impediment to understand it before acting.
- Single Point of Contact (SPOC) – A pattern where the project manager acts as the external interface for the team, shielding members from unnecessary interruptions and forwarding genuine requests.
- Theory of Constraints – A management approach holding that every system has a constraint limiting performance; eliminating one constraint exposes the next.
- Process Efficiency – The ratio of value-adding time to total elapsed time. A useful measure for identifying waste, queues, and excess work in progress.
- Dot-voting – A group decision technique where team members distribute votes across options to surface collective priorities, often used in retrospectives.
- Risk Register – Where many impediments started life as risks that have now become issues.
Related Topics
- 1.2 Manage Conflicts
- 1.3 Lead the project team
- 1.4 Engage stakeholders
- 2.4 Plan and manage resources
- 2.8 Plan and manage schedule
- 2.9 Evaluate project status
- 3.1 Define and establish project governance
- 3.3 Manage and control changes
- 3.5 Plan and manage risk
- 3.6 Apply continuous improvement to processes
- PMP Mind Map
FAQ
What is the difference between an issue and an impediment?
An issue is a problem that has happened and needs action; an impediment is anything blocking or significantly slowing the team’s progress.
What is the difference between a risk and an issue?
A risk is an uncertain future event that may or may not happen; an issue is a problem that has already occurred.
Why do issues need fast action?
Left alone, they compound and drag down project performance.
How does this task fit into the 2026 PMP exam?
Task 3.4 sits in the Business Environment domain of the 2026 Exam Content Outline. The 2026 PMP Exam page has the domain and task breakdown and what changed in the new exam.
