THE LEDGER
MKM-R-2026-014New edition: The State of Mid-Market Transformation 2026
01 / 04
MARKHAMConsultation
← EngagementsCase file — Logistics · 2023–2024MKM-E-2023-071 · Client-approved · Anonymised

Rescuing a stalled network consolidation

ClientLogistics operator
Duration12 months (rescue)
CapabilitiesImplementation oversight
Systems deliveryHolisticAutomation
84%Of the original value case recovered, verified at month 26
14 → 4Workstreams after re-sequencing to one drawn phase
6 wksFrom arrival to an honest baseline the board accepted
12 moRescue duration, arrival to verified delivery

Recovered value verified against the original month-0 case under the Markham Verification Standard at month 26.

01

The situation

A logistics operator was fourteen months into a network consolidation that reported green and shipped nothing. There were fourteen workstreams, three steering committees and a programme office of twenty, and the depot network still ran exactly as it had on day one, which was the one fact no status report contained. The integrator’s dashboard showed 71% complete. Neither a customer nor a cost line could detect any change at all.

The board did not ask us to run the programme. It asked for the truth about it first, and then for a way to keep whatever value was still alive, which are two different pieces of work and were scoped and priced as two.

02

What the diagnostic found

Six weeks of forensic baseline work established what 71% complete meant. It meant 71% of activities started and 9% of outcomes delivered. The original value case had never been baselined, so benefits were being claimed against a forecast that moved every quarter, which let the programme report progress against a target that had quietly followed it downwards. Of the fourteen workstreams, four carried 90% of the recoverable value. The other ten existed because stopping them had no owner.

We re-priced the recoverable case at 84% of the original. That was less than the promise and more than the board had feared, and it was the first number anyone connected to the programme had produced with hard evidence underneath it rather than a forecast.

03

How Markham helped

The rescue was a re-sequencing, not a restart. Ten workstreams stopped in a single board decision. The four that mattered were re-drawn as one phase with frozen baselines, named owners and a weekly outcome cadence, and none of that was new thinking, which is the uncomfortable part of most rescues. HolisticAutomation took over the systems integration under a re-cut contract with outcome milestones, and we held oversight, contracted to the board.

Delivery ran twelve months from arrival. Verification at month 26 confirmed 84% recovered, measured against the original case and not against the re-forecast that had replaced it, because a rescue measured against its own revised promise has not really been measured. The remaining 16% was written off in public, in the board minutes, which is where write-offs belong.

04

Impact in detail

MeasureMonth 0Month 26Change
Original value case recovered9% delivered84%Verified
Active workstreams144−10
Depots consolidated0 of 99 of 9Complete
Programme run-rate cost$1.1M/mo$0.4M/mo−64%

All readings verified against the original month-0 case under MKM-F-003. Nothing here is measured against a re-forecast.

05

What we took from it

a

Activity percentages are not progress. The gap between 71% of tasks and 9% of outcomes is where stalled programmes hide.

b

An honest baseline was the rescue. Once the board had a true number, every subsequent decision took days instead of months.

c

Writing off the unrecoverable 16% openly bought the credibility that delivered the 84%. Rescues fail when they keep promising the original number.

Discuss a similar situationThe operating model used