Skip to content

All best practices

BP-067Grade B19 supporting cases (19 counted), 0 counter-examples

Decide what litigation or a dispute is for, and settle against its full cost and duration

The practice

Before suing or settling with a supplier or counterparty, decide what the dispute is meant to achieve, weigh it against the full cost and duration of litigation or arbitration, and do not settle before the full cost of the failure is known.

Why it works

Disputes after a failed programme or deal can run for years, consume management time and recover only part of the loss. Settling too early can forfeit recovery when the full cost of the failure is not yet known; litigating without a clear purpose can cost more than it recovers. Deciding the objective first (recovery, precedent, reputation or closure) and weighing it against the full cost and duration makes the choice deliberate.

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

  • Quantify the full cost of the failure before negotiating any settlement.
  • Write down the objective of the dispute and the expected recovery range.
  • Estimate the cost, management time and duration of litigation or arbitration.
  • Weigh the reputational cost of public blame before making it.

Warning signs

  • A settlement is agreed while remediation costs are still rising.
  • Litigation continues with no updated expected-recovery estimate.

When it applies

  • Failed IT programmes, broken deals and acquisition disputes.

When it does not

  • Where a legal duty requires action regardless of expected recovery.

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
  • T11 Turnaround
Topic (business problem)
  • Pricing and customer profitability are deteriorating
  • Legacy ERP and fragmented systems block execution
  • Cross-functional processes are slow and broken
  • Data cannot be trusted for critical decisions
  • Technology spending is growing without business returns
  • Regulatory complexity is overwhelming controls
Function
  • Finance & FP&A
  • HR & Workforce
  • IT, ERP & Digital
  • Risk, Compliance & Internal Audit
Starting situation
  • Stalled or failing (turnaround)
Industry
  • B2B SaaS and Subscription Software
  • Chemicals and Process Manufacturing
  • Commercial Banking
  • Commercial Real Estate and REITs
  • Discrete Manufacturing
  • Electric Power Utilities
  • Engineering, Construction and EPC
  • Hospitals and Health Systems
  • Hotels, Lodging and Hospitality
  • IT Services and ERP Systems Integrators
  • Logistics, Warehousing and 3PL
  • Other (cross-industry)
  • Professional Services: Accounting, Law and Advisory
  • 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.