The Failure Cost Iceberg#
When ERP implementations fail, the visible costs—consulting fees, licence costs, abandoned software—are just the tip of the iceberg. Below the surface are hidden costs that can exceed the visible costs by 2-3x.
Category 1: The Workaround Economy#
When the ERP does not meet business requirements, workarounds emerge. These are not free.
Spreadsheet proliferation: Critical business processes run in Excel with manual data entry from ERP.
Shadow systems: Departments build or buy their own systems to fill ERP gaps.
Manual processes: Tasks that should be automated remain manual.
Quantifying Workaround Costs#
For each workaround: - Time spent on manual data entry and reconciliation - Error rate and error correction cost - Audit and compliance risk - Opportunity cost of staff time
Category 2: Data Quality Debt#
Failed implementations often leave data quality issues that persist for years.
Incomplete migration: Historical data was not fully migrated.
Data corruption: Migration introduced errors that were never corrected.
Inconsistent coding: Master data was not properly cleansed before migration.
Quantifying Data Quality Costs#
- Time spent investigating and correcting data issues
- Decisions made on incorrect data
- External audit findings and remediation
Category 3: User Productivity Loss#
Even successful implementations cause productivity loss during transition. Failed implementations extend this indefinitely.
Training overhead: Users require more training than planned.
Support burden: IT and power users spend time helping others.
Process friction: Users struggle with processes that don't match their needs.
Quantifying Productivity Loss#
For each affected user group: - Number of users - Hours per week lost to ERP friction - Fully loaded cost per hour - Duration of productivity loss
Category 4: Integration Fragmentation#
When ERP implementation fails to deliver expected functionality, integration strategy often fragments.
Point solutions: Departments implement their own systems with their own integrations.
Manual bridges: Data moves between systems through manual exports and imports.
Synchronisation failures: Data gets out of sync between systems.
Category 5: Opportunity Cost#
The most hidden cost is what the organisation cannot do because of ERP problems.
Delayed initiatives: Other projects are delayed or cancelled to fund ERP remediation.
Management distraction: Senior leadership time consumed by ERP issues.
Competitive disadvantage: Competitors move ahead while you struggle with ERP.
Category 6: Relationship Costs#
Vendor relationships: Failed implementations damage relationships with ERP vendors.
Partner relationships: Implementation partners may be less responsive after a difficult project.
Staff morale: Repeated ERP problems erode confidence in IT and leadership.
Recovery Cost Framework#
When evaluating whether to continue with a struggling implementation or restart:
| Continue | Restart |
|---|---|
| Remaining implementation cost | New implementation cost |
| Remediation of current issues | Data re-migration |
| Ongoing workaround costs | Re-training users |
| Delayed benefits | Delayed benefits |
| Risk of continued failure | Risk of new failure |
NZ/AU Considerations#
Limited partner options: Smaller market means fewer alternative implementation partners.
Distance costs: Bringing in international expertise is expensive.
Local references: Fewer local reference customers for validation.
Conclusion: Prevent Before Cure#
The cheapest way to address hidden failure costs is to prevent failure in the first place. Realistic planning, adequate budget, experienced oversight, and manageable scope are far less expensive than recovery.