Post-Implementation: Why ERP Systems Look Good but Feel Broken

Operational Reality: Better Than Before

Walked into a company a few years after their Oracle go-live.

First thing I heard: The BOMs are much better than they used to be.

I’ll be honest — that sounded like good news for about ten minutes.

Then I started asking questions.

Turns out, a sharp cost accountant had been finding BOM errors and bouncing them back to engineering. Engineering launched a cleanup. Hundreds of corrections. Real effort, real results.

The BOMs really were better.

But the process that created the errors? Unchanged.

Paper ECOs. Manual BOM updates. No formal PDM system connecting engineering changes to the ERP. Just a faster, better-organized reaction to the same broken workflow.

They’d gotten good at finding errors.

What they needed was a reason to find fewer of them.

That’s the distinction most operations miss.

Everyone focuses on cleaning up bad data. Fewer people focus on why the bad data exists in the first place.

Better accuracy is a cleanup win. Sustainable accuracy is a process win.

And every BOM error eventually shows up somewhere: inventory, cost, planning, production, customer deliveries. You don’t always know where or when — but it lands.

The goal isn’t to get faster at corrections.

The goal is to need fewer of them.

Learned that one the hard way.

— Lee Stout, Staudt Solutions