BP-022Grade B29 supporting cases (29 counted), 0 counter-examples
Make bad news safe and fast to reach the top, and act on it
The practice
Build reporting so that problems, internal warnings and employee concerns reach the executive team quickly and safely, and record what was done about each.
Why it works
In the KB's failing programmes the warnings existed (Phoenix, IBM Watson Health, GM) but were filtered, reclassified or treated as communication problems on the way up. Slips are described as immaterial, and early internal memos go unanswered. A culture and a reporting route in which bad news is rewarded rather than punished shortens the time between a problem appearing and management acting on it. Recording the response to each warning creates accountability. Restructurings are a chance to change how risk information reaches the top; if not changed, the old culture resurfaces later.
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
- Review open risks and slips weekly against one plan, in a forum where reporting a problem is expected.
- Create a route for employees to raise concerns directly to the top, and respond within a week.
- Treat internal warnings as data to investigate, not as messages to manage.
- Track how often metrics are achieved by overriding systems or processes.
- Stop describing slips as immaterial without evidence.
Warning signs
- Status reports are green until the month before failure.
- Staff override system controls to hit targets.
- Internal warnings are handled by communications or legal staff.
When it applies
- All large programmes, and especially safety, clinical, aerospace and financial-control contexts.
When it does not
- No exception; the boundary is that speed of escalation must be matched by capacity to act, or alert fatigue follows.
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
Government of Canada (Public Services and Procurement Canada) CS-038
The Boeing Company CS-040
Tesco PLC CS-044
Starbucks Corporation CS-026
General Motors CS-041
County of Marin, California CS-105
Yes Bank Limited CS-119
CD PROJEKT S.A. CS-121
Mizuho Financial Group, Inc. and its banking subsidiary Mizuho Bank, Ltd. (Japan) CS-156
HCL Technologies Limited (Noida, India), IT services company listed on the Indian exchanges CS-212
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.

