Bringing In an Expert: 5 Keyed, 9 Distractors, and the Test Is Whether Anyone Actually Lacks the Knowledge

September 7, 2026 · 6 min read

TL;DR: Subject matter experts and external consultants appear in 14 of the bank's answer options: 5 keyed, 9 wrong. The discriminator is unusually clean. Ask what the project is missing. If it is specific technical knowledge nobody on the team has, the expert is keyed. If it is capacity, motivation, ownership, or a decision, the expert is the distractor.

Expert judgment is a real technique, and candidates know it is a real technique, which is exactly what makes this option easy to over-pick. The bank tests whether you noticed what the scenario is short of.

What do the keyed instances have in common?

Each one contains a specific technical question the project cannot answer from inside, and the expert's judgment is what lets the project manager then decide.

A vendor supplying specialised equipment proposes substituting a similar part for the one in the project specifications, to protect the delivery date. The keyed answer consults a subject matter expert on whether the substitution is acceptable. The explanation states the test outright: whether the substitute part is fit for purpose is a technical question, and the project manager is not the person qualified to answer it. Accepting or refusing the substitution first would make a quality decision on schedule grounds.

A change control board approves a change nobody on the team knows how to implement. Two answers are correct: bring in a subject matter expert, and have the team research the implementation. The change is already approved, so the only open question is how, and the gap is capability. One option buys the knowledge from outside and the other builds it inside.

A project is behind, three extra remote members have been added, and a week later there is almost no progress on their work packages. Keyed: record the lack of progress in the issue log and bring in a subject matter expert. Adding two more people repeats what already failed. Hiring more experienced people assumes a cause nobody has established. Costing the delay is worth knowing but does not get the work moving.

Three different domains, one shape: a specific technical question the project cannot answer from inside.

When is the expert the distractor?

Whenever the project is short of something other than knowledge: capacity, ownership, motivation, or a decision that is the project manager's to make.

StemExpert option offeredWhy it loses
Team says it has no time to update lessons learnedBring in a consultant to gather themAn outsider cannot capture what the team itself learned
New PM appointed to an experienced agile teamBring in more SMEs so the team produces better resultsImplies a capability gap the scenario does not describe
Client with little domain knowledge asking for bare requirementsAdvise the client to engage an SMENamed in the explanation as a fallback; involve them in every iteration first
Non-conformances need unbiased reviewExternal consultants to oversee all critical testingOutsources a quality response the project should be making

The lessons-learned item is the sharpest. Team members say they have no time to update the repository because other responsibilities have grown. A consultant would "take the load off the team," which sounds like it solves the stated problem. It does not, because the thing being collected is the team's own experience, and the keyed answer folds the discussion into meetings that are already happening.

Common trap: reaching for an expert when the project is behind schedule. Two separate items offer hiring experienced people or outsourcing critical tasks to a specialist firm as schedule recovery, and both are distractors. A schedule problem is a capacity and sequencing problem. The bank flags these options by name in its explanations as assuming a cause nobody has established, which is the same failure the exam punishes everywhere else: acting before diagnosing.

Does this overlap with expert judgment as a technique?

Partly, and the distinction is worth holding. Expert judgment as a technique often means using expertise you already have access to, including your own team's and the organisation's. The answer options in this vein are usually about acquiring someone new, which carries cost, time, and the implication that the current team is not enough.

That implication is what several distractors trip over. Bringing in more experts to an experienced agile team is not neutral in the bank's reading; it is a statement about that team, and the keyed answer in that item is to express trust in their ability to deliver.

FAQ

When does the PMP exam key bringing in a subject matter expert? When the scenario contains a specific technical question the project team is not qualified to answer, such as whether a substituted component meets the specification, and the expert's judgment is what lets the project manager decide.

Why is hiring a consultant usually the wrong answer? Because in most stems the missing thing is not knowledge. The bank rejects consultants brought in to capture the team's own lessons learned, to oversee testing, or to compensate for a schedule problem, because none of those is a knowledge gap.

Does adding experienced people fix a late project? No. In one item three extra remote members are added and progress stalls anyway, and hiring more experienced people is rejected as assuming a cause nobody has established. The keyed answer logs the issue and brings in an expert to find out why.

Is it wrong to bring in an expert alongside another action? Not necessarily, and one item keys exactly that: bringing in an expert and having the team research the implementation are both correct on a multiple-response question. Watch for "choose two" framing, where the acquire-knowledge and build-knowledge options can both be right.

Try it yourself

PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.

Related reading: Adding People to a Late Project: 6 Keyed, 24 Distractors and Knowledge Transfer: Tacit vs Explicit, and Why 'Write It Down' Is Usually Wrong. The relevant tasks are on the People domain study page.

Sources: PMI, 2026 PMP Examination Content Outline.

FAQ

When does the PMP exam key bringing in a subject matter expert?

When the scenario contains a specific technical question the project team is not qualified to answer, such as whether a substituted component meets the specification, and the expert's judgment is what lets the project manager decide.

Why is hiring a consultant usually the wrong answer?

Because in most stems the missing thing is not knowledge. The bank rejects consultants brought in to capture the team's own lessons learned, to oversee testing, or to compensate for a schedule problem, because none of those is a knowledge gap.

Does adding experienced people fix a late project?

No. In one item three extra remote members are added and progress stalls anyway, and hiring more experienced people is rejected as assuming a cause nobody has established. The keyed answer logs the issue and brings in an expert to find out why.