When I Realized the Problem Wasn’t the ERP
A journal entry about the moment I stopped seeing industrial software as just code and started understanding real operational company flows.
For years, I thought the main problem inside companies was the software itself.
Slow ERPs. Terrible interfaces. Complicated workflows.
I believed that building something more modern would automatically solve everything.
Then I started working inside a real industrial environment.
And that’s where I realized something important:
the problem wasn’t the ERP.
The real problem was the distance between what was actually happening on the factory floor and what the system was capable of seeing.
Working in warehouse operations and production exposed me to things I would have never noticed as a pure software developer.
Materials physically available but stored in the wrong place. Orders blocked because of components worth a few cents. Production stopped for days. Purchasing teams discovering issues too late. Operators realizing something is wrong long before the system does.
That’s when I started asking myself deeper questions.
Is the real issue that the part is missing?
Or is the issue that the information arrives too late?
Because in most SMEs, the real operational flow does not go through the software.
It goes through people.
Through:
- phone calls
- WhatsApp messages
- Excel sheets
- senior operators’ memory
- shouting between warehouse and production
And this completely changed how I started seeing industrial software.
I realized many companies do not need another massive ERP.
They need lower operational latency.
Meaning: reducing the time between:
- the moment a problem appears
- and the moment someone takes action
Years ago I built a very simple internal dashboard.
No hype. No AI. No overengineered architecture.
Flask. Jinja2. Basic JavaScript.
Operators entered job orders, item codes and quantities. Production and purchasing finally started seeing the same operational data.
And the interesting part was: people actually used it.
It was opened during meetings. Operators relied on it. Teams started trusting the flow.
That’s when I understood something fundamental:
validation is not when a founder says “great idea.”
Validation is when a production manager opens your software on their own while trying to prevent a production stop.
From that moment, I started seeing software differently.
Not as web pages. Not as CRUD applications. Not as modern frontends.
But as systems designed to reduce friction, delays and operational chaos.
And that was probably the moment I stopped thinking like just a web developer.
And started thinking more like a systems engineer.