Getting Accurate Reporting When You Need It and Before Opportunities Pass By.

BAM!!!! There was a door between our main plant and the offices that slammed into a skid of material every time someone opened it too far. The sound was so common it blended into the rhythm of the shop, like the shear cycling or a forklift beeping in reverse. Everyone heard it. No one questioned it.

Why the material sat there was unclear. It wasn’t staged for production. It wasn’t marked for shipment. It didn’t seem urgent enough to move, and like most annoyances in manufacturing, by the time it bothered you enough to act, something more important stole your attention.

Until one day, it didn’t.

After slamming into that skid yet again, I asked a simple question that turned out to be anything but simple:

What is this material, where did we buy it, who was it bought for, how long has it been here, and why can’t we either sell it or turn it into something else?

The expectation was a quick answer. The reality was silence.

A day later, someone poked their head into my office to say they were “still working on it.” At that point, I didn’t even care anymore. But the fact that nobody could answer such a basic question had my attention again. When it surfaced two days later in a production meeting that multiple managers were now involved in tracking this thing down, my curiosity turned into concern.

This wasn’t incompetence. It was something worse. This was a systems problem hiding in plain sight.

The Archaeological Dig Behind a Simple Question

The skid didn’t have a tag, but it did have line markings. That meant the heat number existed somewhere. Heat numbers lived in Excel. Excel lived in a shared folder. That folder also contained scanned PDFs of mill certs. Find the heat number and you could find the purchase order.

Once you had the PO, you moved into the ERP to look for open quantities tied to that order. That told you which work orders had been created. Each work order had an internal number, which led you to another file that mapped internal numbers to customer POs.

If the job was old enough, those customer POs weren’t digital. They were scanned and archived offline. Somewhere. Eventually, after enough clicking, digging, and guesswork, you found the original customer. Patient zero.

But that only answered one question.

Who else could use this material?

That meant querying a different system to see which newer orders might nest from that same plate. Then came the specs. Just because another customer used similar material didn’t mean the specs aligned. Those details lived in the CRM, but not fully. Character limits meant critical notes were truncated. Some context lived in emails. Some lived in people’s heads.

Four systems. Two file drawers. One dusty box of PDFs from the mid-2000s. Three people pulled away from real work. All to answer a question that should have taken minutes.

This wasn’t about data cleanliness. It was about context.

The Real Cost Isn’t the Material. It’s the Delay.

Most small to mid-sized manufacturers don’t think in terms of data architecture. They think in terms of throughput, margin, and cash tied up on the floor. That’s the right instinct.

But here’s the uncomfortable truth: the skid by the door wasn’t costing money because it existed. It was costing money because nobody could make a decision about it quickly.

Could we scrap it? Sell it? Reassign it? Run it on a different job? The longer it took to answer those questions, the longer capital sat frozen, blocking space, blocking decisions, and quietly eroding efficiency.

Multiply that by every orphaned pallet, every “we’ll deal with it later” purchase, every exception that never got closed out, and you start to see the hidden tax many manufacturers live with every day.

This Isn’t an ERP Problem. It’s an Information Flow Problem.

The instinctive reaction is to say, “We need better systems.” Maybe. But more often, the issue isn’t the tools. It’s how information flows between them.

Each system in our story did its job. ERP tracked orders. CRM tracked customers. Excel tracked certs. None of them were wrong. They just weren’t connected in a way that preserved meaning as information moved from one step to the next.

Manufacturers often underestimate how much tribal knowledge props this up. People fill in gaps mentally. They remember why something was bought. They know which customers are flexible. Until they don’t. Until someone retires, moves roles, or just isn’t in the room.

Then a simple question becomes a scavenger hunt.

Practical Lessons Small and Mid-Sized Manufacturers Can Apply

You don’t need to buy an enterprise data platform to fix this. But you do need discipline in a few areas.

First, standardize how exceptions are labeled and stored. Orphaned material should never exist without a reason code and an owner. Even a simple shared log beats silence.

Second, define one place where “source of truth” context lives for materials. Not just specs, but intent. Why was it bought? What flexibility exists? If that context doesn’t survive past the original buyer, it will cost you later.

Third, map decision paths, not systems. Ask yourself: when material is stranded, what questions must be answered to resolve it? Then ensure those answers don’t require heroics to find.

Fourth, stop tolerating “we’ll remember” as a process. Memory is not a control system. It’s a liability.

The Anti-Consultant in Me

Most consultants show up selling software or frameworks. That’s not what small manufacturers need first. What they need is someone to walk the floor, listen to stories like the skid by the door, and translate them into repeatable decision logic.

The opportunity isn’t digitization for its own sake. It’s decision acceleration.

How fast can your team answer basic operational questions without pulling three people into a meeting? How often does inventory sit idle because context is missing? How much working capital is tied up in ambiguity?

Those questions resonate. And they lead naturally to practical improvements that fit the size, budget, and reality of the business.

The Skid Wasn’t the Problem

In the end, the skid did get resolved. It always does. But the lesson stuck with me because it wasn’t about steel, or ERP, or Excel.

It was about how easily manufacturers accept friction as normal.

The noise of the door slamming faded into the background until someone finally stopped and asked why it was happening. That moment of frustration exposed a deeper issue that had been there all along.

Most manufacturing problems don’t announce themselves with a BAM. They sit quietly by the door, waiting for someone to ask the wrong question and uncover the real one.