|
A weekly briefing for the industrial economy
The Operations Brief
By Bill Murphy, powered by Colony Spark
|
|
|
|
October 9, 2026
|
|
In a budget meeting, a safety repair gets funded because it has a clear deadline: fix this or stop production. Another line is still running but loses good units every week, so its improvement request sounds easier to defer. The second project might save more capacity, but you cannot compare them until the ongoing loss is visible.
This issue is about that gap: how to show the production loss already happening, estimate what another quarter could cost, and propose a small test to confirm the fix works before you ask for the full rollout.
|
This week’s question
What most often stalls an improvement project at your operation?
One click is enough. I’ll share what we hear in a future issue.
|
Bill
|
Show the Loss, Not Just the Promised Return
A projected return on investment can be easy to defer when a repair has a clear deadline. Make the request comparable by showing the current production loss in your own terms.
A safety repair gets urgency because the consequence is immediate. An improvement project sounds optional when you frame it as future capacity. But if your records show that a line loses good units every week, or runs in downtime that could be eliminated, that loss is happening now. The question is whether to act on it this quarter or carry it forward.
Show the loss in your operation’s own terms: downtime hours, good units scrapped or off-specification, or capacity hours displaced by rework. Then calculate what waiting could mean. Over the next comparable period, if the same pattern repeats, what production could be at risk? This does not guarantee approval; it makes the improvement request comparable to an urgent repair.
Brey-Krause lost weeks on its mirror line after equipment failure. Its MEP partner recommended replacing the straightener and notcher first, with later upgrades on a roadmap. NIST reports 15% less downtime and 15% capacity growth for that company. Those are site-specific reported results, not a forecast for your operation or proof of a general budget rule.
|
Show what the loss actually costs before you forecast what a fix would save.
|
|
Why the Improvement Waits
From the second Operations Brief Roundtable: why high-value work keeps losing to urgent work.
Madhur Bedre’s process-optimization projects compete with urgent maintenance and safety work for plant budget. He described what that fight looks like from his side of the table:
His answer is to translate the work into what the plant already tracks, such as production rate, flaring and off-quality material, and put an ROI on it. That shows what doing nothing already costs, not just the upside you hope to gain later.
|
The takeaway
An improvement framed as future upside will keep losing to urgent work. Framed as a loss you can already measure, it gets a fair hearing. The Stack below shows how to put that loss on one page.
|
|
Build a One-Page Case for One Deferred Fix
Work with an operations lead and a finance partner. Pull records from shift, maintenance, quality, and production to build a decision card that fits beside urgent requests at the next budget meeting.
Sample decision card (illustrative numbers, not a reported plant result)
|
Decision Test a changeover-jam fix on one packaging line before a larger rollout.
Owner Production supervisor; finance partner checks the cost assumptions.
Present loss Over 12 weeks, records show 30 stop hours. A supervisor verifies that 12 hours came from the jam this fix addresses; exclude the other 18.
Capacity at risk At 40 good units per staffed hour, 12 × 40 = up to 480 good units of capacity, not 480 guaranteed sales.
Cost of waiting If the same verified pattern repeats over the next comparable 12 weeks, up to another 480 units of capacity could be at risk. Finance checks actual demand, contribution, scrap or overtime overlap, and fix cost before assigning dollars. Do not count the same loss twice.
First phase Run a four-week test on that line. Agree in advance on the improvement threshold and the stop-or-expand decision. If the records show little fixable loss, or the test does not reduce it, do not make the larger claim.
Optional AI step If cause notes are messy, use AI only to suggest which notes mention the jam. A person checks every label against the original records. Skip this when cause codes are already clean; the totals and math come from plant records.
|
This is a hypothetical card, not an observed customer result. It is our own application of the panel’s discussion, not a template from any panelist.
Bring one such page to the next budget discussion. It informs a decision without overruling a safety obligation. Show the cost of doing nothing, propose a test to confirm the fix works, and let the numbers speak for the improvement.
|
|
The Operations Brief
By Bill Murphy, powered by Colony Spark
A weekly briefing on the decisions, people, and systems shaping manufacturing and distribution.
Colony Spark, 170 Mason Street, Greenwich, Connecticut 06830, United States
© 2026 Colony Spark. All rights reserved.
|
| |
|