The Smith and the Tailor
Field notes for the CEO: why many deployments are cut before anyone measures the floor, and two rules you can set before kickoff.
The symptom shows in one department. The cause usually sits in another. I measure the whole chain before I cut.
Tell me what you’re seeing See a sample audit
Supply Chain & Operations × Deployment Strategy
Stock the books show and the floor does not hold. Write-offs nobody can explain. Orders shipped wrong, and the overtime to put them right.
Each number says where it comes from: a study, a company filing, my own analysis, or my own field work.
Count what the floor holds against what the record says.
Take out the loss the count exposes, at its cause.
Stay through go-live until the new way of working holds.
For technology teams, the same work runs in five steps, from the first audit to the handback. How a deployment runs
Rarely the algorithm. Usually one of three things that were there before the system arrived.
The number people quote, 95%, comes from a 2025 MIT NANDA report, The GenAI Divide: 95% of organisations saw no measurable P&L impact from generative-AI pilots. It is a preliminary industry report, and it covers AI pilots, not ERP or WMS projects. The cause it names is older than AI: brittle workflows and missing context.
I walk the floor first, the 02:30 shift included, and ask what happened rather than what people think. Then I put the record and the floor on one timeline and write the working down, so finance, the floor and engineering can check it. Captures of screens, labels and racks run in plain sight with notice, never faces; an operator is recorded only if they say yes. How I diagnose
A three-week field audit, cutover leadership, a fractional operations or deployment lead, and advisory by the hour. Engagements and fees
A 50,000-SKU distribution-centre cutover in Melbourne, a USD 30M cross-border P&L, a re-runnable triage of 2,708 marketplace claims, and tools I build in Python, SQL and TypeScript, among them an inventory and replenishment engine with 10,756 passing tests that stages every decision in draft before write-back.
Open to full-time or embedded Deployment Strategist roles with technology vendors and enterprise teams, and to fixed-scope audits and cutovers invoiced in USD from Chile. On a site visit I observe and count using the blade you issue; I do not operate your machinery or fill a post. Working terms or if you are hiring
Field notes for the CEO: why many deployments are cut before anyone measures the floor, and two rules you can set before kickoff.
A bestiary of the go-live: why obeying the system and dodging it answer the same rule, and what a rule looks like when nobody has to carry it.
Field notes for the COO: why dented units ship, and three questions to ask where the record is written.
Field notes for the CFO: why the fastest driver on the report can be the most expensive one in the ledger, and how to trace the damage to a name.
Field notes for the COO: why exceptions the desk cannot clear leave the procedure, and four numbers to watch each week before the record drifts.
Field notes for the CEO: why the person who sees a rule fail after go-live may not be the one who can stop it, and how to measure the gap.
Field notes for the COO: why minutes the time standard has no category for are charged to the operator, and five steps to let the floor contest them.
Field notes for the CFO: why a human approval can get weaker as the system it checks gets better, and how to test the control, not the signature.
Field notes for the CEO: why a budget that expires on a fixed date pays for a rush in its last week, who carries the bill, and the rule you can change.
Field notes for the COO: where a step on a shift screen protects you, where it buys workarounds, and four questions for the next screen you approve.
Field notes for the COO: why a quality record built for the auditor teaches the floor to fill it rather than use it, and four questions to ask of it.
An executive on your side, named in writing before kickoff, who is not the deployer. Without one, the change after go-live belongs to nobody. Full answer
Because knowing a tool shapes what you see, even for experts. The safeguard is a rule set before kickoff, not the deployer’s open mind. Full answer
Neither by default. Measure the misfit first, sort what the system lacks from what it imposes, and weigh each customization against its upkeep. Full answer
No. The ERP keeps the books, the new piece works beside it in signed drafts, and an old module retires only after its replacement wins in parallel. Full answer
Log twenty system recommendations a month against what the operator would do and what doing nothing costs. If neither ever wins, audit the deployer. Full answer
Because obeying costs them nothing today and questioning has a price. What reduces the error is making people answer for the decision. Full answer
Sometimes: large adjustments tend to help and small ones often hurt. Without a name and a reason, a company cannot learn which overrides paid off. Full answer
Before, and for a reviewer whose view the operator does not know. A reason written after the fact is a defence; one written to please is an echo. Full answer
In one retailer’s audit, 65% of nearly 370,000 records did not match the shelf. A model trained on them is wrong exactly where the record is. Full answer
Often neither. In a public marketplace dataset, 57% of “not received” reviews on delivered orders were written on or before the delivery day. Full answer
About the author · The Deployment Chasm, a manuscript
Based in Santiago, Chile. I take on work in English and in USD in the United States, Australia, Canada, the United Kingdom and Europe.