BP-023Grade B14 supporting cases (14 counted), 0 counter-examples
Design targets and incentives so that missing a target honestly is safer than meeting it falsely
The practice
Test every target and incentive for the behaviour it rewards: measure the integrity of results, not only their level, and remove metrics that drive the wrong behaviour.
Why it works
Targets that staff believe are unachievable, paid through incentives, create pressure to meet them by any means: inflated income, accounts opened without consent, savings booked by the people paid for them. The cases show that this is a control risk, not only a performance problem, and that many individual dismissals for the same misconduct are evidence about the system. Measuring integrity (quality of sales, reversals, complaints) alongside level, separating the people who document savings from those paid on them, and removing metrics that drive harmful behaviour reduce the risk. Customer promises need the same test: simple or unlimited offers must be true in the small print.
KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).
How to apply it
- For each incentive target, define an integrity measure (reversal rate, complaints, audit sampling).
- Survey staff on whether targets are achievable; treat a high 'unachievable' score as a control risk.
- Separate the people who certify a saving or sale from those paid on it.
- Remove or redesign metrics that drive the wrong behaviour, and say why.
- Check that incentives in every channel, including partners and licensees, match the customer promise.
Warning signs
- Rising dismissals for the same misconduct.
- Targets met with unusual consistency at period end.
- Complaints or reversals rising while sales targets are met.
When it applies
- Sales-driven banks, retailers and telecoms; cost programmes with savings-linked pay; accounting-driven targets.
When it does not
- No exception; the practice is a condition on target design rather than a choice.
Evidence grade: Grade B
At least 6 counted supporting cases for every 100 cases in the knowledgebase (6 × cases ÷ 100, rounded to the nearest whole number), whose primary regions span at least 4 regions.
Why this grade
Grade B by schema 4.10 route: >=14 counted cases across >=4 primary regions (the case bar is 6 per 100 cases in the knowledgebase, 235 cases). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
Tesco PLC CS-044
Toshiba Corporation CS-054
Wells Fargo & Company CS-081
The Kraft Heinz Company CS-050
Starbucks Corporation CS-026
T-Mobile US, Inc. CS-073
Dewey & LeBoeuf LLP CS-108
CD PROJEKT S.A. CS-121
Cybozu, Inc., Tokyo-listed maker of groupware and the kintone cloud platform CS-157
Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026
Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.

