BP-031Grade C15 supporting cases (13 counted), 0 counter-examples
Change what people are paid for before asking for a new culture
The practice
Align pay and performance measures with the behaviour the new strategy needs, ideally one external measure the front line can move, before launching culture programmes.
Why it works
People follow incentives more reliably than exhortation. A culture campaign that leaves old incentives in place teaches staff that the culture is rhetoric. Changing what people are paid for (external customer value, team results, a single measure such as on-time performance) gives the new culture immediate meaning. A simple language for the new culture helps, but it works once the incentives agree with it. Kotter's framework treats anchoring change in the culture as the last step [R5]; it is a framework, not a measured study.
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
- Identify the two or three behaviours the strategy requires and the incentives that currently work against them.
- Redesign variable pay around value created for external customers or one front-line measure.
- Measure unit performance independently and link it to the plan's goals.
- Give the culture a short, plain vocabulary once the incentives match it.
Warning signs
- Culture values are launched while bonus metrics are unchanged.
- Pay rewards internal targets the customer never sees.
- Staff cannot name the measure they are paid on.
When it applies
- Culture change, service turnarounds and operating-model redesigns.
When it does not
- Where intrinsic professional norms dominate (clinical, research) and narrow incentives can crowd them out.
Evidence grade: Grade C
Anything below B. Plausible, but not yet tested in the KB at the B bar.
Why this grade
Grade C by schema 4.10 route: below the B bar of 14 counted cases across 4 primary regions (6 per 100 cases in the knowledgebase, 235 cases). B needs at least 14 counted supporting cases across at least 4 primary regions; this practice has 13 counted case(s) across 6 region(s). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does. 2 supporting case(s) rest only on company-reported claims and are not counted toward the grade.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
Microsoft Corporation CS-013
Continental Airlines, Inc. CS-088
CD PROJEKT S.A. CS-121
Virgin Australia Holdings (Virgin Australia Group), owned by Bain Capital from November 2020 CS-134
Cybozu, Inc., Tokyo-listed maker of groupware and the kintone cloud platform CS-157
HCL Technologies Limited (Noida, India), IT services company listed on the Indian exchanges CS-212
Research
Kotter's framework names not anchoring changes in the corporation's culture among eight common errors.
Practitioner framework built from case observation; no systematic method disclosed; cannot raise a grade above C on its own.
Leading change: why transformation efforts fail (HBR 73(2):59-67, 1995), as abstracted by AHRQ PSNet · Kotter, AHRQ PSNet, 1995
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.

