When to Escalate on the PMP Exam (and Why "The Escalator" Loses Points)
"Escalate to the sponsor" is one of the most tempting answers on the PMP exam. It sounds responsible. It feels safe. And in many questions, it's wrong.
At PM Exam Lab, we call this decision pattern The Escalator: a candidate who hands problems upward before doing the work the project manager is expected to do first.
Why escalating early is usually wrong
The exam expects the project manager to own problems within their authority. Escalating too early tells the examiner you:
Haven't analyzed the problem yet.
Haven't involved the team or the people closest to the issue.
Haven't used the tools you already have, such as the risk register, the issue log or the change process.
The order the exam usually expects
When a problem appears, think in this order:
Understand it. Gather facts and find the root cause.
Check the plan. Is it already covered by the risk register, a response plan or a team agreement?
Collaborate. Talk with the people involved and the team.
Act within your authority. Use the agreed process, such as raising a change request.
Escalate only if it's outside your authority or you can't resolve it.
When escalation IS the right answer
Escalation isn't always wrong. It's right when:
The issue is beyond your authority, such as a change to the overall budget or project objectives.
You've already tried to resolve it at your level and it's still blocked.
There's an ethical, legal or safety concern that must be reported.
The escalation path is already defined in the plan for exactly this situation.
Example
A key stakeholder keeps missing review meetings, and approvals are slipping. What should the project manager do first?
A. Escalate to the sponsor.
B. Meet with the stakeholder to understand the cause and agree on a way forward.
C. Remove the stakeholder from the approval process.
D. Update the schedule to show the delay.
Answer: B. A is The Escalator. C acts alone and ignores the agreed process. D records the symptom without fixing it. B tackles the cause directly and collaboratively.
How to break the habit
Before choosing "escalate," ask: "Have I analyzed the problem and talked to the people involved?" If not, keep looking.
Look for the answer that keeps ownership with the project manager.
Track it. If escalation answers cost you points on every mock, that's your pattern. Practice it on purpose.
Decision Lab tracks six decision patterns, including The Escalator, The Fixer and The Lone Wolf. It shows you which ones are costing you points.
Comments