MARKHAM
← EngagementsCase file — Manufacturing · 2025MKM-E-2025-124 · Client-approved · Anonymised

Throughput recovery in a two-plant industrial group

ClientTwo-plant industrial group
Duration9 months
CapabilitiesOperational excellence
Systems delivery
+19%Throughput against the month-0 baseline, both plants
$0Capital expenditure required to deliver it
−38%Rework hours at the bottleneck work centres
+3.1ptGross margin at month 9

Audited under the Markham Verification Standard at month 9; run-rate re-tested at month 12. Full audit trail available under NDA.

01

The situation

A two-plant industrial group had order books it could not ship. Lead times had stretched from three weeks to seven; overtime was structural; and the board was reviewing a $14M capacity expansion as the obvious answer. The capex case was internally persuasive and externally unexamined.

The group asked for a second opinion on the expansion. The more useful question was where the existing capacity was going — because at nameplate, the two plants already had 26% more capacity than the order book required.

02

What the diagnostic found

Four weeks of measurement at the line located the loss with some precision: two bottleneck work centres were being starved by upstream sequencing decisions made daily, informally, and differently on each shift. Rework at those centres consumed 19% of their hours, and priority orders — expedited by whoever escalated loudest — reset the schedule a median of six times a week.

None of this was a capacity problem. It was a decision problem wearing a capacity costume: no agreed sequencing rule, no fixed forum to hold it, and no baseline anyone trusted.

03

How Markham helped

The work ran in three phases over nine months, with no capital request. First, the constraint map: losses located and priced line by line, and a frozen month-0 baseline signed by both plant directors. Second, cadence redesign: one sequencing rule for the bottleneck centres, a daily fifteen-minute schedule forum with the authority to hold it, and a weekly operating review of run-rate against baseline.

Third, the hold: three months of the new rhythm under oversight, with expedite requests routed through the forum and priced openly. The loudest-voice escalation channel closed because it stopped working.

04

Impact in detail

MeasureMonth 0Month 9Change
Throughput, both plants100 (index)119+19%
Order lead time, median7.2 wks3.9 wks−46%
Rework at bottleneck centres19% of hrs11.8% of hrs−38%
Schedule resets per week61−83%

Baselines frozen and audited before phase one; month-9 readings verified under MKM-F-003 and re-tested at month 12.

05

What we took from it

a

The capex case was real arithmetic on top of a false premise. Mapping the constraint before pricing the expansion saved $14M.

b

The binding constraint was a daily decision, not a machine. Fixing who sequences the bottleneck outperformed adding capacity to it.

c

A run-rate that is not reviewed weekly decays. The hold phase — the least glamorous third of the work — is where the result became permanent.

Discuss a similar situationThe operating model used