Skip to content

All best practices

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
  • T05 ERP and core systems
  • T08 Culture and change
Topic (business problem)
  • Cross-functional processes are slow and broken
  • Data cannot be trusted for critical decisions
  • Technology spending is growing without business returns
  • Bureaucracy and slow decisions prevent agility
  • Service delivery is too slow, unreliable or expensive
  • Regulatory complexity is overwhelming controls
Function
  • Procurement & Strategic Sourcing
  • Risk, Compliance & Internal Audit
Starting situation
  • Stalled or failing (turnaround)
Industry
  • Chemicals and Process Manufacturing
  • Commercial Banking
  • Discrete Manufacturing
  • Electric Power Utilities
  • Grocery and Food Retail
  • Hospitals and Health Systems
  • Hotels, Lodging and Hospitality
  • IT Services and ERP Systems Integrators
  • Logistics, Warehousing and 3PL
  • Other (cross-industry)
  • Restaurants and Quick Service
  • Telecommunications, Broadband and Fiber
Region
  • Africa
  • Central and Eastern Europe
  • East Asia
  • Global
  • Latin America
  • Middle East
  • North America
  • Oceania
  • South Asia
  • Southeast Asia
  • Western Europe

Supporting and counter cases

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.