PMP · Question #643
During the execution stage. the project manager discovered that one team member is not able to complete their work on time and is running later than expected. This delay may potentially impact a…
The correct answer is B. Discuss with the team and assess the reasons that led to the delay. When a team member's delay threatens a milestone, the project manager should first engage the team to understand the root causes of the delay.
Question
During the execution stage. the project manager discovered that one team member is not able to complete their work on time and is running later than expected. This delay may potentially impact a project milestone. What should the project manager do first?
Options
- ADiscuss with senior management and seek their guidance.
- BDiscuss with the team and assess the reasons that led to the delay.
- CRequest the team member's manager to find a solution.
- DAssign more resources from other teams on the late work.
How the community answered
(14 responses)- A7% (1)
- B71% (10)
- C14% (2)
- D7% (1)
Why each option
When a team member's delay threatens a milestone, the project manager should first engage the team to understand the root causes of the delay.
Discussing with senior management is an escalation that should occur after the project manager has investigated the issue and explored potential solutions with the team, not as a first step.
The project manager's primary role is to manage the project and its team. When a delay occurs, the most effective first step is to engage directly with the team, and specifically the individual, to understand the reasons behind the delay, such as roadblocks, skill gaps, workload issues, or external dependencies. This allows for informed decision-making regarding potential solutions and avoids premature escalation or misallocation of resources.
Requesting the team member's functional manager to find a solution passes responsibility rather than actively managing the project and understanding the issue firsthand, which is the PM's role.
Assigning more resources without understanding the root cause of the delay might be ineffective if the issue isn't a lack of resources, potentially wasting resources.
Concept tested: Problem-solving and root cause analysis for project delays
Source: https://www.pmi.org/learning/library/conflict-resolution-project-management-6523
Topics
Community Discussion
5
Prof. SaraJun 6, 2026Confirmed B on exam last week. B is the correct answer because the PM must first understand the root cause of the delay before taking any corrective action. Discussing with the team aligns with the People domain focus on servant leadership and collaborative problem solving. A and C jump the chain of command prematurely, while D throws resources at a symptom without diagnosing the actual issue. Remember the mnemonic CRAB for execution issues: Communicate, Research root cause, Assess impact, then Buffer or fix.
Yusuf A.Jun 18, 2026Going with B here. One of the senior PMs at my company always says before you escalate or throw resources at a problem, talk to the team and figure out the root cause first.
Viktor S.Jun 19, 2026Agreed, but the exam expects you to distinguish between "talk to the team to understand what happened" and a formal root cause analysis, so read the stem carefully before you lock in B.
Imani T.Jun 30, 2026B is the right call here because in PMP land you always go to root cause before you escalate or throw bodies at the problem. A and C are jumping the gun by involving people outside the team, and D is classic crash-and-burn thinking that ignores why the delay happened in the first place. The PM's job is to understand the situation with the team, then figure out the appropriate response based on actual facts. Does anyone know if the exam consistently treats "discuss with the team" as the default first step for execution-phase issues, or are there scenarios where going straight to the resource
Viktor S.Jun 10, 2026B is the right call here. PMI wants you to figure out the root cause before you escalate or start throwing bodies at the problem. You cannot fix what you do not understand, and the delay could be anything from a technical blocker to unclear requirements. Discussing it with the team first keeps the issue at the lowest possible level and gives you the information you need to decide on an actual fix.