The Most Important Software in Your Factory Might Be the Stuff IT Didn’t Buy
Walk through almost any manufacturing company and you’ll eventually find it.
A spreadsheet. And not just any spreadsheet - The spreadsheet.
You know, the one that has been around for years. The one with 14 tabs, mysterious formulas, and color coding that only three people fully understand.
Maybe it tracks production, maybe it schedules jobs, Maybe it calculates quotes, manages inventory, tracks quality issues, or tells the morning meeting what actually happened yesterday.
🚫 It probably wasn't part of a digital transformation roadmap.
🚫 Nobody issued an RFP for it.
🤷♂️ Someone just needed to solve a problem, so they built something.
⚠ And then the company started depending on it.
Every factory has an unofficial technology stack
Manufacturers usually have an official list of systems: ERP. Accounting. Quality. Maintenance. Scheduling. Maybe an MES. Then there's the unofficial list:
Spreadsheets.
Access databases.
Shared folders.
Whiteboards.
Paper travelers.
Email chains.
And, occasionally, the employee who somehow knows how everything connects.
These tools are easy to dismiss as technical debt. But they tell you something important.
They show you where the official systems stopped matching the reality of the operation.
Someone created that production spreadsheet because they couldn't get what they needed from somewhere else.
Someone built that scheduling board because the ERP screen didn't give supervisors the visibility they needed.
Someone created a manual quality log because the existing process was too cumbersome on the floor.
These aren't just workarounds.
🔎They're clues.🔎
Don't delete the spreadsheet. Investigate it.
When companies begin modernization projects, there's often an understandable urge to clean everything up; Ditto when Mr. Manager reads an article like this one. To be clear, the long-term goal can be to:
Get rid of spreadsheets.
Eliminate paper.
Standardize systems.
Automate everything.
But before eliminating a workaround, it's worth understanding why it exists.
Find the person who created it.
Ask what problem they were trying to solve.
Ask who uses it.
Ask what would happen tomorrow if it disappeared.
That last question is especially useful.
If the answer is: "Production would have a serious problem.” You've probably found something worth studying.
Your best process analysts might already be on the floor
Another interesting thing happens when you investigate these unofficial systems: You find people who understand the operation extraordinarily well:
The production planner who built a complicated scheduling workbook.
The quality manager who created a better way to track defects.
The supervisor who redesigned a paper form because operators kept missing information.
They may not call what they're doing "systems design,” but that's essentially what it is. They understand the inputs. They understand the exceptions. They understand what information matters.
And most importantly, they understand what happens when the process meets reality. That knowledge is incredibly valuable when deciding what to automate or modernize.
The goal isn't to eliminate scrappy solutions immediately
The goal is to learn from them. A spreadsheet that has survived for eight years is telling you something.
So is the whiteboard everyone checks before the ERP, and the employee who receives five emails every morning and manually combines them into one report.
Those things mark the places where people have adapted technology to fit the operation.
And those places are often exactly where the next technology project should begin.
So the next time you walk through a manufacturing facility, don't just ask what software the company uses.
Ask a different question:
"What do you use that you're pretty sure you're not supposed to be using?"
The answer might teach you more about the operation than the official system diagram ever will.
