The ERP That Didn't Fix Anything

New system. Same problems.

01
Situation
A wholesaler implements an ERP to fix reporting and stock problems. A year later, staff still keep spreadsheets alongside it.
02
Evidence
- Parallel spreadsheets
- Inconsistent product codes
- Workarounds for approvals the system enforces
- Reports nobody trusts
03
The decision
Replace the ERP, or fix the processes and data around it?
04
Analysis
The ERP copied undefined processes and bad data. It is a symptom, not the problem.
05
Framework
Fix, improve or transform: is the system broken, the process around it, or the business design?
06
Resolution
Product data is cleaned, three processes are redesigned, and the existing ERP is reconfigured to match.
07
Founder exercise
Apply it to your own business:
- List every spreadsheet kept outside your main system
- Ask why each exists
- Classify each reason: system, process or data

Situation