BP-066Grade B25 supporting cases (23 counted), 0 counter-examples
When a failure hits customers, tell them early, fix it completely, and compensate consistently
The practice
When a failure reaches customers, disclose it early with a plan and a date, fix it in full rather than in part, compensate consistently across markets, and use every channel to reach affected customers.
Why it works
Customers and investors forgive failures more readily than concealment. Early disclosure with a plan and date limits speculation and lets customers adapt. Partial fixes invite a second failure, which costs more trust than the first; admitting a fault in public and changing the thing completely, sometimes backed by a guarantee, turns a weakness into credibility. Consistent compensation across markets avoids a second controversy. In a recall, measuring participation and using every channel, including the product itself, reaches the last owners. Explaining cost-driven price changes before customers feel them applies the same logic to commercial changes.
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
- Disclose customer-affecting failures early, with a remediation plan and date.
- Fix the root cause completely; avoid partial or staged remedies for safety issues.
- Set a compensation policy that applies consistently across markets.
- Measure recall or remediation participation and use every channel to reach customers.
- Explain price changes before customers experience them.
Warning signs
- Communications are delayed pending legal review.
- Remedies differ by market without a stated reason.
- Recall participation is not measured.
When it applies
- Product recalls, failed go-lives, safety issues, emissions and conduct cases, and price changes.
When it does not
- No exception for safety matters; for minor service issues the scale of response should be proportionate.
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. 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
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.

