September 8, 2026 · 7 min read
TL;DR: Benchmarking appears in fourteen options in this bank and is keyed four times. One property survives every one of those records and settles most items: the comparison points outward. Benchmarking measures your product, process or schedule against comparable work outside your organisation. The moment an option has you comparing something against your own baseline, your own charter, or your own plan, it is describing variance analysis or a review, and the bank writes exactly those options as distractors.
The word itself is loose in everyday use. People say they are benchmarking when they mean measuring anything against anything, and the exam charges for that looseness.
Outward, and the bank says so in one sentence.
An appliance maker losing market share to rising energy prices asks for a business case of options and specifically wants benchmarking performed. What next? The four options are: find which competitor products have been benchmarked for future production, compare your products against the specifications of leading energy-efficient appliances on the market, write a project charter to use as a benchmark for your management plan, or benchmark your current scope, cost and schedule against baseline values.
Keyed is the market comparison. The explanation opens with a useful reading instruction: the client has named the technique, so the task is to apply it correctly. Then it defines the technique. Benchmarking measures your own product or process against comparable ones outside the organisation to reveal where you stand and what good looks like.
That definition disposes of two distractors immediately. A charter used as a benchmark for your own management plan is internal. Scope, cost and schedule against baseline values is internal, and it already has a name, which is variance analysis. Both sound like measuring. Neither looks outside.
In four places, and they span three different domains.
For schedule estimating, a project manager plans to build a schedule using similar past schedules as a starting point and asks which tool can find that historical information. Keyed is benchmarking, and the explanation ties it to estimating directly: benchmarking compares current data against historical data and can inform analogous estimating. PERT does not rely on historical data at all, and surveys or facilitated workshops would not surface comparable schedule data.
For process improvement, a product owner watches sales and revenue climb while profit falls seventeen per cent. Keyed is benchmarking against a similar but non-competing company and adding the resulting improvements to the product backlog. The diagnosis in the explanation is worth keeping: if profit falls while sales revenue rises, the product is costing more to produce or sell. The phrase similar but non-competing is doing real work there, since a competitor will not show you their process.
For requirements, a multinational expanding into a market it has never operated in must collect requirements. Two answers are keyed: draw on the expert judgement of someone who knows the market, and benchmark the product against the market leaders. The explanation says why the other options fail in a way that generalises well: product analysis and progressive refinement both draw on knowledge the organisation does not yet possess. When you know nothing, you have to look at someone who does.
For external environment questions, the appliance record above.
Wherever the comparison would have to point inward, or answer a question nobody asked.
| Scenario in the bank | Benchmarking option offered | What is actually keyed |
|---|---|---|
| Quality lab would cost half the expected profit | Benchmarking | Cost-benefit analysis |
| Social-media complaints that quality has slipped | Add features benchmarking against competitors | Feed user focus group input into development |
| Client names benchmarking, wants it applied | Benchmark scope, cost and schedule vs baseline | Compare products against market leaders |
| Trustee compares to a trust that went live in eight months | Quietly compress the schedule to match | Find what drives the gap and bring that finding |
| Model tuned to a published word-accuracy benchmark | Ask the sponsor to rule between benchmark and staff | Define what a good subtitle gives a deaf viewer |
| Assuring processes will produce a conforming product | Integrated planning, using benchmarking | The quality assurance reading of the scenario |
The cost-benefit record is the cleanest near miss. A consultancy's quality assurance work would require building a laboratory costing nearly half the expected profit, and management asks the project manager to weigh the strengths and weaknesses of the alternatives. Keyed is cost-benefit analysis, which compares alternatives so the best can be identified and establishes whether a planned quality activity is worth what it costs. Benchmarking loses because it compares this project's practices against others rather than choosing between options.
Common trap: treating benchmarking as a general-purpose quality answer because it appears in quality tool lists. The apparel record is built on it. An owner facing social-media complaints that quality has slipped sets up an agile team told to put quality ahead of everything, and one option adds features benchmarking the product against competitors. Keyed is feeding user focus group input into the development life cycle, because the complaints come from users, so bringing user judgement into development catches problems before customers meet them. The explanation dismisses the benchmarking option in seven words: it answers a competitive question nobody asked. Match the technique to the evidence in the stem, not to the topic heading it usually sits under. This bank names the losing technique and says what question it would have answered.
Then check whether it holds, and if it does, find the cause rather than the excuse.
A hospital trust is replacing its patient-records system under a phased rollout. A trustee compares it to a similar trust that went live in eight months and expects the same. The project manager reviews both projects in detail and finds the scopes are genuinely comparable: same record volume, same shape of work. The plan here says eleven months.
Keyed is identifying what is actually driving the extra three months and bringing the trustee that finding, along with either a plan to close the gap or a case for why it should stand.
The three distractors each dodge in a different direction, and each is tempting. Telling the trustee the comparison does not apply because every project has its own context is the reflex answer, and it is wrong here specifically because the project manager already checked and it does apply. Quietly compressing to eight months absorbs the pressure without examining it. Pointing to the approved eleven-month plan and declining to revisit it uses a past approval to avoid a present question.
The explanation names the standard: when the benchmark genuinely does carry, the honest move is to find out why this project is slower rather than to explain the difference away or absorb the schedule pressure unexamined. The driver might be resourcing, a dependency the other trust did not have, or simply a less efficient plan. Any of those is a finding you can act on.
There is a matching record on the opposite failure, where a benchmark is trusted too much. A model team tuning a subtitling assistant against a published word-accuracy benchmark is at odds with the subtitlers who do the work by hand. Keyed is describing with the subtitlers what a deaf viewer gets from a good subtitle and making that the outcome the assistant is built to serve. The explanation identifies the real defect: because no outcome was ever stated, the accuracy benchmark had quietly become the project's working purpose by default. A benchmark is a comparison, not a goal, and it stops being useful the moment it starts substituting for one.
What does benchmarking actually compare on the PMP exam? Your own product or process against comparable ones outside the organisation. The bank states it directly in its appliance record: benchmarking measures your own product or process against comparable ones outside the organisation to reveal where you stand and what good looks like. Comparing your scope, cost and schedule against your own baseline is variance analysis, and the bank offers that as a distractor.
Is benchmarking a scheduling technique or a quality technique? Both, depending on the question. The bank keys benchmarking as the tool for finding historical schedule information to feed analogous estimating, and separately keys it as the process improvement route for a product owner whose profit is falling while revenue rises. What stays constant is the outward direction of the comparison.
When is benchmarking the wrong answer in a quality question? When the question is about whether an activity is worth its cost, or where the quality signal is coming from. The bank keys cost-benefit analysis over benchmarking when a quality lab would cost half the expected profit, and keys user focus group input over benchmarking against competitors when customer complaints are the evidence, noting that benchmarking answers a competitive question nobody asked.
What should you do when a stakeholder benchmarks your project against another one? Check whether the comparison genuinely holds, then find the driver. In the bank's hospital trust record the scopes are genuinely comparable and the keyed answer is identifying what is actually driving the extra three months and bringing the stakeholder that finding, along with a plan to close the gap or a case for why it should stand.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, and every wrong answer is explained, not just marked wrong, so you find out which question the losing technique would have answered. Start the free 20-question sample — no card, no signup required to try it.
What does benchmarking actually compare on the PMP exam?
Your own product or process against comparable ones outside the organisation. The bank states it directly in its appliance record: benchmarking measures your own product or process against comparable ones outside the organisation to reveal where you stand and what good looks like. Comparing your scope, cost and schedule against your own baseline is variance analysis, and the bank offers that as a distractor.
Is benchmarking a scheduling technique or a quality technique?
Both, depending on the question. The bank keys benchmarking as the tool for finding historical schedule information to feed analogous estimating, and separately keys it as the process improvement route for a product owner whose profit is falling while revenue rises. What stays constant is the outward direction of the comparison.
When is benchmarking the wrong answer in a quality question?
When the question is about whether an activity is worth its cost, or where the quality signal is coming from. The bank keys cost-benefit analysis over benchmarking when a quality lab would cost half the expected profit, and keys user focus group input over benchmarking against competitors when customer complaints are the evidence, noting that benchmarking answers a competitive question nobody asked.
What should you do when a stakeholder benchmarks your project against another one?
Check whether the comparison genuinely holds, then find the driver. In the bank's hospital trust record the scopes are genuinely comparable and the keyed answer is identifying what is actually driving the extra three months and bringing the stakeholder that finding, along with a plan to close the gap or a case for why it should stand.