Skip to content

All best practices

BP-068Grade B16 supporting cases (16 counted), 0 counter-examples

Protect the integrity of procurement and appointments, and test feasibility before signing long contracts

The practice

Protect procurement and executive appointments from conflicts of interest, build sale and purchase processes that will survive audit and court scrutiny, and test feasibility before committing to long contracts.

Why it works

A flawed procurement locks in a flawed programme: once a long contract is signed, its design and its supplier are hard to change. Speed of procurement is not speed of delivery, and contracts signed before feasibility is tested transfer risk on paper only. Protecting the process from conflicts, separating roles that create them, and building processes that will survive later audit or court review protects both the programme and the people in it. The risk rises when the organisation is under strain and controls weaken.

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

  • Separate roles that could create conflicts in procurement and appointments.
  • Document every procurement decision as if it will be reviewed in court.
  • Run a feasibility test or proof of concept before signing multi-year contracts.
  • Strengthen procurement oversight when the organisation is under strain.

Warning signs

  • Contract awards are accelerated to meet political or budget deadlines.
  • The same people define requirements and evaluate bids with outside contacts.
  • Long contracts are signed before a working prototype exists.

When it applies

  • Public-sector programmes, state-owned enterprises, megaprojects and asset sales.

When it does not

  • Small, reversible purchases.

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
  • T07 Supply chain
Topic (business problem)
  • Legacy ERP and fragmented systems block execution
  • Cross-functional processes are slow and broken
  • Technology spending is growing without business returns
  • Supplier inflation and procurement leakage are unsustainable
  • Regulatory complexity is overwhelming controls
  • Energy, resource or climate exposure undermines economics
Function
  • Procurement & Strategic Sourcing
  • Data, Analytics & AI
  • Risk, Compliance & Internal Audit
Starting situation
  • Stalled or failing (turnaround)
Industry
  • Chemicals and Process Manufacturing
  • Commercial Real Estate and REITs
  • Electric Power Utilities
  • Hospitals and Health Systems
  • Logistics, Warehousing and 3PL
  • Other (cross-industry)
Region
  • Africa
  • Central and Eastern Europe
  • East Asia
  • Latin America
  • Middle East
  • North America
  • Oceania
  • 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.