The $5 Part That Stopped the Production Line

It was a bracket.

Small. Stamped. The kind of part that goes through a sub-supplier's heat treatment furnace in under a day and costs about five dollars to produce. Nobody on the programme was worried about it. It had never been a problem before.

The sub-supplier had quietly taken on two additional customers that month. Their furnace — the only one they had capable of this specific treatment — was suddenly running at over ninety percent capacity. Our batch queued behind two other urgent jobs. Nobody told us. The sub-supplier didn't think it was worth mentioning — they assumed they'd catch up.

They didn't.

The delay was four days at the sub-supplier. Four days became seven once it hit the supplier's machining schedule, because the operation after heat treatment was already booked and couldn't be moved quickly. Seven days became twelve once it reached us, because our final test sequence had no float left to absorb it.

Twelve days. Production line stopped. Airfreight. Emergency planning calls. A customer relationship that took months to repair. All of it traceable to a four-day delay on a five-dollar part, at a sub-supplier nobody was watching — because the part was small, cheap, and had never caused trouble before.

The Question I Ask Every New Programme Manager

I ask them: what's the most dangerous task in your programme right now?

Almost everyone points to the same place. The critical-path machining operation. The big assembly sequence. The validation run. The expensive things. The things that take the longest and involve the most people.

I tell them to look at the sub-supplier tasks instead. The small ones. The cheap ones. The ones early in the process that nobody is watching because they've never been a problem.

They're always surprised. And they're always right to be — because most project tracking systems were never built to tell them otherwise.

Three Very Different Hands on the Wheel

Not all delays are equal, even when they look identical on a Gantt chart. A two-day slip on an internal quality check gets recorded the same way as a two-day slip on the only casting supplier in your supply chain. They are not the same risk. Not even close.

A sub-supplier task that slips is the most dangerous of all — not because the part matters more, but because the problem is harder to detect and far harder to recover from once it surfaces. Your supplier may have every incentive not to tell you the sub-supplier is behind, because admitting it makes them look bad.

The Formula — Why Multiply, Not Add

This is the logic behind the Risk Number:

Take the same five-day delay and run it through all three control types:

The formula multiplies rather than adds for a reason. A two-day delay that's happened six times is not the same risk as a twelve-day delay that's happened once. Multiplication lets the factors compound the way risk actually compounds in a real supply chain. Addition would flatten that difference and miss the pattern entirely.

Familiarity Is the Risk

Here's the part that catches most programme managers off guard: the tasks most likely to blindside you are the ones that have never given you trouble before.

A supplier who's slipped three times this quarter gets watched. A sub-supplier who's never slipped, ever, on a part that costs five dollars, gets ignored — right up until the month they quietly take on two new customers and your batch queues behind work you'll never see on any dashboard.

This is why a Consequence Number can't be something a programme manager assigns by feel. It has to be structural — built into how every task is weighted, automatically, from day one, regardless of how unremarkable that task has been so far. The moment a sub-supplier task starts to drift, the Risk Number needs to escalate fast — not because the delay is large, but because the consequence of that delay, compounded through two more tiers of supply chain, is enormous.

Watching the Right Things

A one-day slip on an internal task might cost you a day. A one-day slip at a sub-supplier, with two more handoffs downstream, might cost you twelve — the same math that turned a five-dollar bracket into a stopped production line.

This is the same idea behind the three-week recovery window and the same philosophy behind reading OPV instead of task count: the danger was never about size. It was always about visibility, and how much runway you have left once you finally see it.