The Five-Cent Screw That Exposed a $20,000 Strategy Gap

A five-cent screw, used in a $20,000 FDA-compliant medical device, gets hard to source. Tariffs, lead times, the supply chain pressure every manufacturer is living with.

Manufacturing does what a good team does. A sourcing engineer finds a near-match from a supplier they’ve used for years, functionally solid, in stock. The part goes around the table at the Tuesday review: quality, engineering, someone from finance. It gets tested against spec and it passes. Everyone in that room has been chasing this shortage for six weeks, and here is a part that works, available now, at a price that holds. Quality signs off. Finance is relieved. The product ships. A note goes out in the next company-wide update, along with everything else that changed that month. Problem solved.

Then a technician shows up at a clinic to install one. The practice has waited months for this device and cleared the morning for it. He gets the panel off, reaches for the driver he’s used on every one of these, and it won’t seat in the head of the new screw. It’s close. It’s not right, and forcing it on an FDA-compliant device isn’t a decision a field tech gets to make.

The change had gone out. A support leader who reads those notices carefully had seen it and updated the knowledge base that week, the only person downstream who did. Nobody in training was watching the feed. Nobody in field service was either.

The screw shipped. The knowledge didn’t.

Every function did its job, and every number said so. Manufacturing solved a sourcing problem under real pressure. Quality validated the part. Support closed every ticket it opened. Nothing turned red, because each measure watches the work inside a group, and the cost of that screw landed in the space between them.

Your strategy didn’t fail. A change got made in one place and never reached the places that needed it. A decision is only as good as the knowledge that travels with it, and that’s the most common way a good operation loses to itself: it ships the decision and strands the knowledge.

I call it coordination debt, the price an operation pays every time work crosses between groups without the knowledge it needs to land. It carries interest, and the interest is easy to miss because it never arrives as one bill. Six technicians hit it the same day, in six different cities, each one discovering it alone. Field service has the pattern by end of day, since six calls to dispatch is something anyone would catch. What they don’t have is the cause, or the scope. Nobody can say how many kits are wrong, or which units in the warehouse have the new screw and which have the old one, so installs get halted until someone can. Customers who had already waited months get pushed out again. Two weeks of scrambling later, after pulling shipment records, opening cartons, and checking build dates, the line lands on a single week in the change log. Manufacturing had swapped a five-cent screw.

Five cents held up a twenty-thousand-dollar device, in every clinic waiting for one, for as long as it took to find out why.

It never went through change control, because nobody saw it as that kind of change. A functionally identical part, validated by quality, approved by engineering. That’s a parts substitution, and parts substitutions get logged. What made it a product change was a driver in a technician’s kit, and nobody in that review was thinking about the kit.

Stopping it took one person in that review asking who else touches this. Finding it took two weeks of good people doing detective work on their own operation.

The screw decision was right. What was missing was one question, asked before it was approved: who else needs to know this, and what do they need to do with it?

That question turns a handoff into a handshake. A handoff sends the change and counts that as done. A handshake carries it to the people downstream and confirms they can act on it. Most handoffs never become handshakes, and that’s where the cost lives.

Asked once, the question saves a single product launch. Asked as a habit, it builds an operation where people leave knowledge clearer than they found it, so the next person facing the same problem doesn’t start from zero.

Someone downstream did read that notice. She updated the knowledge base that week, carefully, on her own initiative. It made no difference. Nothing in what she received told her a screw had changed shape, and nothing asked her whether anyone with a toolkit needed to know.

---

The screw wasn’t unusual. The ServiceDNA™ Diagnostic shows where what one group learns stops reaching the next, in about thirty days.

The conversation is thirty minutes

If decisions made upstream keep landing on your team as surprises, and on your customers as delays, that’s the gap worth talking about. Tell me what you’re seeing, and I’ll show you how teams get that question asked before the decision ships, not after.

Book a call with Phil.