Recognition and Rewards: 8 Keyed, 16 Distractors, and Rewarding Early Adopters Is Keyed Zero Times

TL;DR: Options that recognise, reward or praise are keyed 8 times and wrong 16 times across the bank. The eight that work acknowledge performance that already happened, in a form the recipient values. The sixteen that fail use recognition as a lever to change behaviour: to buy adoption of a tool, to motivate a team nobody has diagnosed, or to make one team look like another. Rewarding early adopters appears four times and is keyed never.

Recognition sounds like the safe People-domain answer. It is offered as the wrong one twice as often as the right one, and the wrong ones share a single shape: the reward is doing work a conversation should have done.

When is recognition keyed?

When someone has performed, and the recognition is aimed at them.

A customer praises the project manager personally for consistent on-time delivery. At the team meeting later that day, the keyed answer passes the praise on to the team. The performance was theirs, and recognition only motivates when it reaches the people who earned it. Filing the comment in the minutes buries it. Treating praise as a cue to pull dates forward punishes good work.

One developer's innovative solutions have visibly improved a large project. The keyed answer is not a newsletter feature, a team lunch or an industry award nomination. It is to identify a form of recognition that matches what the developer values most. All three distractors choose a form on the project manager's assumption, and the explanation adds that public recognition in particular can single someone out in a way that damages their standing with the team.

That principle carries the two closest calls in the set. A team member feels their work is undervalued next to their colleagues'. The keyed answer meets them privately to understand what recognition they feel is missing, then makes their contribution visible in a way they value. A peer recognition programme is offered and loses, because it takes time to establish and still leaves this person's specific grievance unaddressed. After a successful close, a support-team member complains they were left out of the recognition. The keyed answer finds out what recognition would mean something to them and arranges it through HR. Sending them to their functional manager passes off a problem the project created.

Under sustained pressure, recognition also keys as part of a pair. A cross-functional medical-devices team is weeks from a regulatory submission, and the keyed answer sets clear, achievable goals and recognises the team's achievements as they are reached. Stretch goals take too long inside a tight deadline. Mandating hours spends the goodwill the push is running on.

When is a reward the trap?

When it is used to change behaviour instead of to acknowledge performance: to buy adoption, to fix a drop nobody has diagnosed, or to reward the wrong thing.

Rewarding early adopters: 0 keyed in 4. Four scenarios have a team reluctant to adopt something new, and each offers a reward for the people who adopt it first. A monitoring instrument nobody knows how to calibrate: keyed is a hands-on workshop, because the gap is capability. A monitoring system the team says the project does not need: keyed is short sessions connecting it to the project's goals, because the gap is understanding. Project management software the team calls overcomplicated: keyed is training that demonstrates what it does for their work. Lean techniques stakeholders are wary of: keyed is meeting them to work through their concerns. The explanation for the first case states the objection to all four: rewarding early adopters pays a few people for overcoming an obstacle that all of them face.

Rewarding before diagnosing. A geothermal survey team's output has fallen away and the project manager judges them demotivated. Implementing a reward system is offered first and loses to a team meeting that identifies the underlying issues. Flat motivation has many causes, and a reward pays people to push through a problem nobody has named. A team member is unsure which testing belongs to them and which to the vendor. A recognition scheme for picking up unclaimed work is offered, and it papers over a gap that a working session on responsibilities would close.

Rewarding the wrong thing. Supervisors complain that Team A's velocity is lower than Team B's. A reward scheme for Team A is offered and loses to explaining that velocity cannot compare teams, because the scheme would reward point inflation. A team is producing artefacts instead of deliverables, and recognising their documentation effort incentivises exactly the wrong thing. A servant leader is asked how to embody the approach, and a competitive reward system is offered, which undermines the cooperation the question asks for.

Common trap: assuming recognition is the answer whenever morale appears in the stem. It is the answer when the stem describes performance that has happened. When the stem describes reluctance, confusion or a drop nobody has explained, recognition is offered as the wrong answer, and the keyed answer is a workshop, a training session, a conversation or a diagnosis. The bank makes the distinction explicit in every one of the sixteen explanations rather than leaving the option marked wrong without a reason.

What does the exam expect you to know about the form a reward takes?

That the form has to fit the person, and that money is the weakest form.

The cash-award item is the one candidates argue with. The sponsor has put money on the table, and the keyed answer still spends it on development rather than distributing it, because recognition works when it is fair, transparent and valued, and an off-site consumes the award while leaving nothing with any individual once it ends. The retention item makes the same point from the other side: pay sits among the hygiene factors, so a rise does not hold someone who has other options, while investing in their development makes staying the more attractive choice.

FAQ

When is recognition the keyed answer on the PMP exam? When real performance is being acknowledged and the recognition fits the recipient: passing a customer's praise to the team that earned it, finding out what form of recognition a specific person values, or pairing achievable goals with recognition as each is reached under sustained pressure.

Why is rewarding early adopters a wrong answer? Because it pays a few people for overcoming an obstacle everybody faces. The bank offers it four times, in scenarios about adopting a new tool or method, and keys it zero times. The keyed answers close the capability gap or answer the objection instead.

Is a cash bonus a form of recognition on the exam? Money is an extrinsic motivator and the bank treats it as the weakest form. When a sponsor sets aside a cash award, the keyed answer spends it on professional development the team retains, not on whoever logged the most overtime.

When should a reward system be set up? As early as possible, before the work begins. People can only work towards something they know about from the start, and waiting for the full team never arrives on a project that onboards throughout.

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: Offering a Bonus: Why Money Is the Wrong Answer to a Morale Question and When Training Is the Wrong Answer on the PMP Exam. People tasks are mapped on the People domain study page.

Sources: PMI, 2026 PMP Examination Content Outline.

FAQ