PMP common mistakes
PMP · Understand the traps and how to avoid them.
On People scenarios, selects the option where the project manager acts alone - reassigning a team member, overriding the team's estimate, or dictating how the work gets done - instead of the option where the PM facilitates, coaches, or lets the team decide.
Most candidates work in command-and-control organizations, so a decisive, unilateral PM feels like the 'strong leader' answer; the exam instead rewards influence, coaching, and team empowerment.
What to do instead
Before answering a People item, identify who acts in each option. Eliminate any choice where the PM imposes a decision that belongs to the team or a functional owner. Prefer the option where the PM asks, coaches, facilitates a session, or attempts a team-level resolution first.
Escalates to the sponsor or HR as the first action when a team member misses deadlines, has a performance problem, or two team members are in conflict.
Escalation feels safe and looks like 'following process,' and candidates fear being blamed for under-handling a problem that later grows.
What to do instead
Apply the escalation ladder: private conversation and coaching with the individual → team ground rules or conflict approach → functional manager → sponsor, and only for issues genuinely outside the PM's authority (policy, funding, organizational priorities). Escalation is the last option unless the stem signals a compliance or safety violation.
Answers a stakeholder problem by adding communications - 'send weekly status reports,' 'add them to the distribution list' - when the stem describes resistance, skepticism, or low buy-in.
Communications management and stakeholder engagement sound interchangeable, and 'more communication' feels like a universally safe answer.
What to do instead
Scan the stem for attitude words (resistant, uncooperative, not attending, blocking, opposing). If the issue is attitude or buy-in, the correct answer is engagement: meet with them, understand their concerns, involve them in decisions, negotiate. Reserve inform/communicate options for information-gap stems.
Selects 'submit a change request to the CCB' for a small verbal scope addition from the customer, or the reverse - implements the change immediately because it is small or obviously beneficial.
Intuition says a trivial or clearly good change should not need paperwork, and most candidates have seen small changes absorbed informally at work.
What to do instead
For any change to approved scope, schedule, cost, or quality standards, the expected sequence is: understand and assess the impact → document it → route through integrated change control → implement only after approval. In adaptive contexts the equivalent is to add the item to the backlog and let the product owner prioritize it.
When the question asks what the PM should do FIRST or NEXT, picks the option that fixes the problem rather than the option that assesses, verifies, or gathers information.
Candidates read for the desired end state and stop at the first plausible remedy; they also skim the final sentence, which is where the FIRST/NEXT qualifier lives.
What to do instead
Mark FIRST/NEXT/BEFORE in the stem before reading the options, then delete any option that solves the issue before the PM has facts. Valid first steps are typically review the plan or contract, analyze, assess impact, meet with the person, or confirm with the team.
Applies 'mitigate' to every risk, or picks a response that does not match the risk type - accepting a high-impact threat with no contingency, or 'avoiding' a risk the project cannot drop.
Mitigate is the strategy most candidates can recall under time pressure, and the threat and opportunity strategy lists blur together.
What to do instead
Memorize the pairings as two columns: threat → escalate, avoid, transfer, mitigate, accept; opportunity → exploit, share, enhance, accept. Eliminate any option naming a strategy from the other column, then use the stem's cues - if the project must proceed, avoid is wrong; if a third party can bear the impact, transfer fits.
Answers a quality question with inspection, testing, or rework when the stem is about preventing defects, or recommends updating the process when the stem is about a defective deliverable.
Quality assurance and quality control both contain the word 'quality,' so candidates answer from the keyword rather than from what the stem actually describes.
What to do instead
Sort by object: if the stem concerns processes, audits, standards, or preventing defects, look for manage quality/QA options. If it concerns a deliverable, a defect found in testing, or verification against requirements, look for control quality/QC options. Confirm the chosen option is prevention-oriented or inspection-oriented as the stem requires.
Recommends moving to the next phase or releasing deliverables without confirming required approvals, regulatory sign-off, or audit compliance, because scope and schedule are on track.
Candidates optimize for delivery momentum and treat governance and regulatory requirements as administrative overhead rather than hard constraints.
What to do instead
Any stem mentioning a regulated industry, audits, safety, contracts, or a formal phase gate should be checked for compliance and required approvals before any delivery-oriented option. Legal and compliance obligations outrank schedule pressure, and 'proceed and document later' is never the correct choice.
Treats 'deliverables completed and accepted' as the finish line, choosing closure options that stop at lessons learned and resource release without addressing benefits realization, transition to operations, or value delivery.
The working definition of project success for most PMs is on-time, on-budget delivery; benefits tracking usually sits outside their daily experience.
What to do instead
For closure and value questions, prefer answers that measure whether the intended business outcome was achieved, hand over to operations with readiness and support, and assign a named benefits owner. If an option only confirms deliverables were accepted, it is usually the weaker choice.
Ignores organizational change impact - recommends launching a new system or process to end users with training scheduled after go-live, or without assessing readiness, sponsorship, or likely resistance.
Candidates equate implementation with adoption and assume organizational change management is someone else's responsibility.
What to do instead
When a stem involves changing how people work, look for the option that builds visible sponsorship, assesses stakeholder readiness, involves end users early, and plans transition and adoption support before or alongside go-live rather than after it.