The Leadership Blind Spot in Manufacturing: Why Finance Got ERP, But the Plant Floor Got Excel

Manufacturing leadership has normalized an operating model it would consider irresponsible almost everywhere else in the enterprise.

Imagine a new CEO walking into a multi-million- or multi-billion-dollar company and discovering that the entire Finance organization runs on Excel spreadsheets, paper ledgers, and emailed reconciliations. What would happen?

Nobody would call that normal. Nobody would say, “Well, that’s just how finance works here.”

The CEO would immediately start asking questions. How is this controlled? How do we trust the numbers? How much risk are we carrying? Why are people manually reconciling information that should already be connected?

And sooner or later, there would be an ERP modernization project. In 2026, running a serious company without a formal enterprise finance system is almost unimaginable.

And yet, day after day, manufacturers accept essentially the same operating model on the factory floor.

And somewhere in the middle of it are experienced supervisors, operators, planners, engineers, and technicians doing heroic work to ensure the company keeps shipping product.

Then everyone says: “That’s just how we do it here.”

How is that acceptable? More importantly, why do so many manufacturing executives not even question it?

Here is the uncomfortable truth: most companies would never tolerate this level of informality in Finance, Sales, or Product Development. Yet they routinely tolerate it in the very operation that creates the product, generates revenue, creates the cost, introduces the defects, consumes the labor, and ultimately determines whether the company keeps its promises to customers.

That’s not just a technology gap. It’s a leadership blind spot.

The plant is working because people are covering for the system

This is probably the biggest reason the problem remains hidden.

A plant manager who has successfully run factories for 20 years may genuinely think, “I have always used spreadsheets, supervisors, whiteboards, and daily meetings. We hit our numbers. Why do I need another system?”

Excel is deceptive because it works — until the business confuses survival with excellence.

A strong plant manager can make almost anything function with experienced supervisors, skilled operators, morning meetings, whiteboards, emails, spreadsheets, and a huge amount of effort. But that’s not a scalable operating model. It’s organizational muscle memory compensating for the absence of a digital system of execution.

The people are doing heroic work. And because they’re doing it so well, leadership concludes the system works.

“In too many plants, humans have become the integration layer.”

The supervisor knows which machine is unreliable. The experienced operator knows how to work around the bad process. The scheduler knows the spreadsheet is wrong but mentally corrects it. The quality engineer knows which paperwork not to trust. The maintenance technician knows the asset history is not complete.

And they do such a good job hiding the gaps that, at the end of the day, the CEO sees only one thing: the product shipped.

What the CEO didn’t see was the hidden operating cost behind the shipment. The product shipped, but it required 37 people, 112 emails, 14 spreadsheets, three undocumented decisions, and four hours of manual reconciliation to make it happen.

The cost didn’t disappear. It was buried in labor, overtime, schedule risk, quality risk, and institutional inefficiency.

The plant is functioning, so leaders assume it’s fine. What they rarely ask is how much invisible effort, delay, rework, and risk are required just to keep it functioning.

We have confused ERP with manufacturing operations

ERP vendors didn’t make this easier. For decades, manufacturers have been told, “Your ERP can do that. It has a module.”

But there is a massive difference between having a transaction screen and having a system designed to run manufacturing operations in real time. A screen that records an event after the fact is not the same as an operating system that orchestrates work as it happens.

ERP is fundamentally oriented around business planning and transactions. Manufacturing operations require managing the dynamic execution of work: coordinating people, equipment, materials, quality, maintenance, inventory, and production activities across minutes, hours, shifts, and days.

ISA-95 distinguishes Level 4 business planning and logistics, where ERP typically operates, from Level 3 manufacturing operations management, where the work of running the factory gets done.

That distinction is not academic. It’s architectural. Trying to force ERP to become the plant operating system is like trying to use the general ledger as the accounting department’s workflow system. You can force-fit it to kind of work, but it’s clearly not the right architecture for the job.

The systems are different — and that matters

Here is what most manufacturing executives were never told, and what most IT organizations got wrong when they tried to help. These systems are not interchangeable products. They answer fundamentally different operational questions:

These capabilities do not all have to be one giant piece of software. But they must work together as a coherent operating architecture.

The mistake is viewing each one as a disconnected software purchase — another budget request, another project, another point solution — instead of recognizing that together they form the digital infrastructure required to run a modern factory.

A company doesn’t buy ERP because it likes finance software. It buys ERP because it accepts that financial control requires a formal system of record. Manufacturing deserves the same level of architectural discipline.

Nobody actually owns the digital operating model of the factory

Here may be the real problem: Nobody owns the digital architecture of the money-making machine.

Finance has a CFO. IT has a CIO. Product development often has a PLM organization. Sales has clear executive ownership.

Who owns the end-to-end digital operating model of the factory?

Ask that question inside a large manufacturing company and watch the answers scatter across the VP of Operations, the CIO, the plant manager, engineering, automation, continuous improvement, digital transformation, and corporate manufacturing.

When nobody owns the manufacturing operating architecture, decisions get made locally, tactically, and in silos:

• Maintenance buys one system
• Quality buys another
• Automation installs SCADA and tries to stretch it into MES
• IT expands ERP
• Production keeps Excel alive
• Engineering builds Access databases
• Corporate launches Power BI
• Someone adds an IIoT or industrial data platform

Then every plant and division evolves differently until the company has a patchwork of point solutions connected by spreadsheets, tribal knowledge, and people who “just know how it is supposed to work.”

That may get product out the door, but it’s not a scalable foundation for growth or resilience.

MES did not get a bad reputation because execution is unnecessary

The reputation problem is real. Early MES implementations were often large, expensive, highly customized, and difficult to integrate. Many involved multi-year projects, complex validation, consultants who didn’t understand the actual plant, and IT-driven designs disconnected from operator needs.

The result was predictable: systems that looked good in a project plan but were hated on the floor. And many operations leaders walked away thinking, “MES projects are expensive and painful.”

We shouldn’t mistake a poor implementation for a lack of business need.

Nobody concludes that Finance doesn’t need an ERP system because the company had a bad ERP implementation 15 years ago. We have all heard the stories: long, expensive, painful ERP programs that went over budget and over schedule. Nobody disputes the need for ERP because of them.

Yet manufacturing organizations routinely use a bad MES project from the past as evidence that the factory doesn’t need a digital system of execution.

The software gets blamed for bad architecture, bad ownership, excessive customization, poor implementation discipline, and a failure to involve the people who actually have to use it.

Those challenges are real. But they are not an argument for running a complex manufacturing operation on paper and spreadsheets. They’re an argument for doing it better.

The question isn’t whether to build a digital operating foundation for your factory. The question is how to reduce implementation risk — and that problem is very solvable. The manufacturers who figured that out are pulling ahead. The ones still citing a failed project from 2009 are falling behind.

The wrong ROI question

The ROI question is another reason this problem persists. A manufacturing operations platform creates value everywhere: less scrap, better labor productivity, reduced downtime, faster investigations, stronger genealogy, fewer quality escapes, less WIP, faster changeovers, less expediting, better schedule adherence, lower inventory, faster training, less tribal knowledge, and better first-pass yield.

The problem is that no single department always “owns” all that value. A $2 million or $5 million price tag for a global MES/MOM project naturally triggers tough questions — and rightfully so.

But there’s another question that rarely gets asked, because it is harder to put in a spreadsheet:

The cost of the problem is spread across the organization, which makes it easy to ignore. But the cost is still there. Look back at your ERP or CRM implementations; what did those cost? Leaders funded them without a second thought because they were deemed essential. MES/MOM should be viewed through the exact same lens.

AI is about to expose the problem

This may be where the status quo finally starts to break.

Every manufacturer is talking about AI: manufacturing AI, predictive maintenance, copilots, autonomous scheduling, digital twins, and intelligent agents. Great ideas.

But where is the data?

Too often, it is still in Joe’s spreadsheet, on the operator’s traveler, in a monthly Excel report, or in someone’s memory. Manufacturers are asking AI to optimize operations that have never been properly documented — and then wondering why it doesn’t work.

“You cannot build an intelligent factory on undocumented human memory.”

If the real production schedule is in an Excel file, the actual process is in an operator’s head, the work instructions are on paper, the downtime reason is written on a clipboard, and the quality history is split across filing cabinets and spreadsheets, what exactly do you expect AI to learn from?

MES/MOM is not just software for digitizing paper. It creates operational context — and operational context is the raw material AI needs.

The question every manufacturing executive should be asking

The core problem in 2026 is not that MES is immature or that manufacturing operations cannot be digitized. The bigger problem is that too many CEOs, COOs, CFOs, and plant leaders still do not recognize manufacturing operations management as a fundamental enterprise capability.

They understand that a company needs ERP to manage money and resources, CRM to manage customers, and PLM to manage products. But they do not automatically ask: What is our digital system-of-record and system-of-execution for running the actual factory?

That is a problem; not for software suppliers and system integrators, but for manufacturing organizations.

Too many factories don’t have a coherent manufacturing operating architecture. They have spreadsheets, paper, and point solutions. And experienced people compensate for everything the systems don’t do.

That may have been good enough in 1996. It should not be good enough in 2026. Especially for a company that believes it is preparing for AI.

The “islands of information” problem manufacturers have discussed for decades is no longer just an efficiency issue. It is a competitiveness issue, an AI readiness issue, and an operating model issue.

Buying MES somewhere is not the same as building a coherent manufacturing operating architecture everywhere.

So here is the question every manufacturing executive should ask:

Questions?

Talk to an expert about your factory’s operating model

If you have any questions or would like to learn more about modernizing manufacturing operations, our team can help you look at where your plant still runs on spreadsheets and paper, and what a connected system of execution could look like.

Talk to an Expert