PMP Reassessing Blockers Until They Are Truly Resolved

Continuous reassessment matters because a blocker is not truly resolved when someone says it is being handled. It is resolved when delivery risk is actually reduced and the team can move again.

Blockers Change Faster Than Status Reports

PMP questions often test whether the project manager keeps checking the blocker after the initial action. That is important because:

• the impact may grow or shrink
• a workaround may fail
• a supposed owner may not follow through
• a resolved blocker may reveal a deeper dependency problem
• a blocker with low priority yesterday may threaten today’s milestone

This means blocker management is iterative, not one-and-done.

Reassess Four Things Repeatedly

Strong reassessment checks:

• current impact
• actual progress toward removal
• whether the owner and next action are still appropriate
• whether escalation or root-cause work is now needed

    flowchart TD
	    A["Blocker logged"] --> B["Assign owner and next action"]
	    B --> C["Review impact and progress"]
	    C --> D{"Risk reduced?"}
	    D -- "Yes" --> E["Close or monitor lightly"]
	    D -- "No" --> F["Reprioritize, change owner, or escalate"]
	    F --> C

Example

A vendor promises a fix by Friday, so the blocker is marked as under control. On Thursday, the project manager learns the vendor is waiting on an internal approval that has not even started. A strong response is to reassess ownership, urgency, and escalation now rather than wait for Friday to confirm the delay everyone can already see coming.

Common Pitfalls

• Treating “owner assigned” as equivalent to “risk reduced.”
• Leaving blocker priority unchanged when the context changes.
• Forgetting to confirm whether the workaround is still safe.
• Closing an issue because someone reported progress rather than because the team can actually proceed.

Check Your Understanding

Sample Exam Question

Scenario: A blocker owned by another department was logged three days ago and assigned an owner. The owner reports that the issue is “in progress,” but the team is still unable to resume testing and the milestone risk is now increasing.

Question: What is the best near-term action?

• A. Keep the status unchanged because an owner already exists
• B. Close the issue because someone has acknowledged it
• C. Reassess impact, progress, and ownership now, then change the action path or escalate if risk is not actually reducing
• D. Wait until the next formal checkpoint even though the blocker is still stopping work

Best answer: C

Explanation: The strongest answer is C because blocker management requires active reassessment. An assigned owner and generic status update are not enough if the team is still blocked and the milestone risk is increasing. PMP questions in this area reward checking whether the blocker is actually being removed, not whether it merely has an owner.

Why the other options are weaker:

• A: Ownership without progress does not reduce delivery risk.
• B: Acknowledgment is not resolution.
• D: Waiting is weak when the blocker is still actively preventing work.

Key Terms

• Reassessment: Rechecking blocker impact, ownership, and removal progress as conditions change.
• Status illusion: The false sense that a blocker is controlled because someone reported activity.
• Follow-through: Ongoing attention to whether the agreed action is actually restoring delivery.
• Recovery path: The current sequence of actions intended to remove the blocker.