PMP Using Relationships and Networks to Unblock the Team

Resolution networks matter because many blockers are not solved by better team effort alone. They are solved through the right combination of influence, ownership, and escalation outside the team.

Blockers Often Sit in Other Parts of the System

When an impediment depends on another function, vendor, sponsor, or governance gate, the project manager has to use relationships well. That can mean:

• engaging the functional manager who owns the scarce resource
• asking the product owner or sponsor to help reset priority
• clarifying facts before escalating to governance
• connecting the blocker to business impact so another group can act on it

The exam usually rewards using the lightest effective path first, not jumping straight to a heavy escalation.

Build the Right Resolution Path

The stronger response usually follows this order:

1. Clarify who really owns the constraint.
2. Contact the person or group with practical authority to help.
3. State the project impact in concrete terms.
4. Escalate only if the issue cannot be resolved at that level.

    flowchart LR
	    A["Blocker identified"] --> B["Find real owner or authority"]
	    B --> C["Use relationship or working-channel to seek resolution"]
	    C --> D{"Resolved at this level?"}
	    D -- "Yes" --> E["Confirm recovery and close follow-up"]
	    D -- "No" --> F["Escalate through governance or sponsor path"]

Example

A shared-services team has not completed firewall access needed for system testing. The weakest response is to tell the delivery team to wait. The stronger response is to confirm impact on the testing milestone, engage the owner in the infrastructure group, explain the consequence to release readiness, and use sponsor or governance escalation only if normal coordination stalls.

Common Pitfalls

• Escalating before identifying the actual owner.
• Treating escalation as punishment instead of a decision path.
• Using vague language instead of concrete project impact.
• Overusing senior stakeholders when the issue can still be resolved through normal working channels.

Check Your Understanding

Sample Exam Question

Scenario: A project team cannot begin integration testing because network access is still pending from another department. The issue is now threatening a committed milestone. The project manager knows the team cannot authorize the access directly.

Question: Which action is most appropriate at this point?

• A. Wait until the next steering committee before raising the issue
• B. Engage the department that owns the access, explain the milestone impact, and escalate only if that path stalls
• C. Escalate directly to executives before contacting the owner
• D. Ask the team to test around the missing access even if that invalidates the result

Best answer: B

Explanation: The strongest answer is B because the blocker sits outside the team’s authority, so the project manager should use the right relationship path first and escalate only if needed. PMP questions in this area reward effective cross-functional coordination, not reflexive escalation or unsafe workarounds.

Why the other options are weaker:

• A: Waiting allows the milestone risk to grow.
• C: Escalating before engaging the real owner skips the lighter effective path.
• D: A workaround that compromises valid testing is not a strong PMP answer.

Key Terms

• Resolution network: The set of people, roles, and channels the project manager can use to remove blockers outside direct team control.
• Functional owner: The person or group with actual authority over the blocked resource or decision.
• Escalation path: The agreed route for raising unresolved issues to a higher authority.
• Impact statement: A concise explanation of how the blocker affects delivery, quality, or acceptance.