BP-028Grade B23 supporting cases (17 counted), 0 counter-examples
State one short plan, repeat it, and run it through one small forum on a fixed cadence
The practice
Express the transformation as one short, named plan that everyone can repeat, and run it through a small, aligned forum that reviews a short list of measures and unit results weekly or monthly.
Why it works
Organisations under strain cannot follow many priorities; a plan stated in a few lines, with named parts, repeated the same way for years, becomes the shared reference for every decision. A small forum reviewing the same measures on a fixed cadence keeps the plan alive, makes slippage visible within days and replaces the slow approval cycles of project governance. Visible unit results, reviewed monthly or faster, make accountability concrete. The plan's architecture should survive leadership changes. Kotter's framework names under-communicating the vision as a common error [R5]; it is a framework drawn from observation, 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
- Write the plan in no more than five lines with named parts, and use the same words in every communication.
- Keep the executive forum small (eight or fewer) and meet weekly on one plan.
- Review a short, fixed list of measures and unit-level results at every meeting.
- Replace multi-layer project governance with a short, open quarterly business review.
- Number the programme's moves publicly so progress is easy to follow.
Warning signs
- The strategy deck changes structure every quarter.
- Many committees review the same programme.
- Unit results are available only at month-end close plus several weeks.
When it applies
- Turnarounds, agile operating models and post-merger integration.
When it does not
- Highly diversified groups where one plan cannot describe very different businesses; use one short plan per business instead.
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. 6 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
Ford Motor Company CS-011
ING Group (ING Netherlands) CS-012
The LEGO Group CS-007
Japan Airlines Co., Ltd. (Japan Airlines Corporation and Japan Airlines International until 2011) CS-016
Lenovo Group CS-049
Qantas Airways Limited CS-064
Continental Airlines, Inc. CS-088
T-Mobile US, Inc. CS-073
Shoprite Holdings Ltd CS-115
Thai Airways International Public Company Limited (THAI) CS-131
HCL Technologies Limited (Noida, India), IT services company listed on the Indian exchanges CS-212
Research
Kotter's framework lists under-communicating the vision and lacking a powerful guiding coalition 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.

