ERP, Digital Transformation, Business Technology

Confessions of an ERP Consultant: Why I Secretly Hate ERP Software

After 25 years navigating the complex world of ERP, here's the unvarnished truth about its pitfalls and how you can avoid them.

I've spent a quarter-century in the ERP consulting trenches, helping businesses implement these massive systems. But today, I need to share a deep, dark secret: I often hate ERP software. It's not just about venting; it's about revealing the costly, risky, and disruptive realities hidden behind the...…
Confessions of an ERP Consultant: Why I Secretly Hate ERP Software
<a href="http://www.youtube.com/@erickimberling">Digital Transformation with Eric Kimberling</a> Digital Transformation with Eric Kimberling Follow

I've spent a quarter-century in the ERP consulting trenches, helping businesses implement these massive systems. But today, I need to share a deep, dark secret: I often hate ERP software. It's not just about venting; it's about revealing the costly, risky, and disruptive realities hidden behind the promises of digital transformation. This article is for business leaders and IT professionals embarking on or struggling with their ERP journey, offering insights drawn from decades of experience to help you make smarter choices and avoid becoming jaded like me.

My Love-Hate Relationship with ERP

My name is Eric Kimberling, CEO of Third Stage Consulting, and for 25 years, my career has revolved around Enterprise Resource Planning (ERP) software. From my early days at Price Waterhouse Coopers in the late '90s to advising global clients today, I've worked with systems like SAP, Oracle, Microsoft, and many others. I've seen firsthand the transformative potential ERP promises – the dream of integrated data, streamlined workflows, and game-changing efficiency.

I love that potential. But experience has taught me a harsh reality: ERP projects are often fraught with challenges.

They can be super costly, super expensive, super risky, and super disruptive to organizations.

So, let's pull back the curtain. Here are the core reasons why, despite building a career around it, I have such a complex relationship with ERP software – and more importantly, what you can learn from it.

1. The Monolithic Monster: Why ERP Systems Struggle to Keep Pace

Many ERP systems, particularly the larger, more established ones, feel monolithic and cumbersome. They were designed as massive, transaction-based platforms to integrate vast amounts of data across an entire organization. That sounds great in theory, but in practice:

  • Outdated Architecture: Their core design often struggles to adapt quickly.
  • Slow Evolution: While vendors invest heavily in R&D, the sheer size and complexity mean these systems can't change fast enough to keep up with the dynamic nature of modern business.
  • Business Agility Suffers: As your organization grows, changes, and evolves, the ERP system often becomes a bottleneck rather than an enabler. It's nearly impossible for a standardized system to perfectly match the unique, shifting needs of every business.

Key Takeaway: During selection, critically evaluate how adaptive and flexible a potential ERP system truly is, not just its current feature set.

2. Expensive and Risky: The Hidden Costs of ERP Implementation

We always focus on the potential ROI and business benefits during ERP evaluations. But the flip side is stark: implementations are incredibly expensive and risky.

Why? It's not just the software cost. It's the breadth of impact:

  • System-Wide Risk: ERP systems touch almost every part of your business. An implementation doesn't just put a single department at risk; it can jeopardize your entire operation.
  • Budget Blowouts: Technical or implementation problems inevitably lead to spending more time and money than planned.
  • Operational Disruption: This is the dirty secret the industry rarely highlights. Post-go-live problems are common and costly.

According to our research at Third Stage Consulting, just over 50% of organizations implementing new ERP software experience some sort of material operational disruption.

This means they might struggle to:

  • Close the books accurately.
  • Run payroll on time.
  • Ship products to customers.
  • Perform other critical business functions.

The cost of these disruptions can often dwarf the initial implementation investment.

Key Takeaway: Factor in significant contingency for both budget and potential operational disruption. Risk mitigation planning is non-negotiable.

3. Trying to Be Everything to Everyone (and Failing)

Another major frustration is that ERP vendors try to make their software appeal to everyone. They pack in features for diverse industries, from high-volume retail distribution to complex, engineer-to-order manufacturing.

  • Diluted Functionality: Trying to meet everyone's needs often means not perfectly meeting anyone's specific, nuanced requirements.
  • Ignoring Competitive Advantages: Your unique processes and competitive differentiators might not fit neatly into a standardized, off-the-shelf system.
  • Industry vs. Individual Needs: Even within a specific industry, your business model and workflows likely differ from your peers. An industry-focused solution might still require significant compromises.

Key Takeaway: Don't assume an ERP system will perfectly fit 'out-of-the-box'. Identify your non-negotiable requirements and unique processes early on and assess the true fit.

4. The Questionable Business Value Proposition

For 25 years, I've seen a consistent pattern: ERP systems often deliver questionable business value to the organizations implementing them.

  • High Failure Rates: ERP projects have notoriously high failure or under-delivery rates.
  • Unrealized Potential: Even successful implementations frequently fall short of the expected ROI.

Why does this happen?

  • Resistance to Change: Sometimes the organization fails to adapt processes or leverage the new capabilities.
  • System Limitations: Often, the software itself is too complex, cumbersome, or lacks critical functionality.
  • Budget Constraints: Initial implementation costs consume the budget, leaving no room for optimizing or adding necessary modules later.

Interestingly, two parties almost always get value:

  1. Software Vendors
  2. System Integrators/Consultants

They profit from your investment. The crucial question is: Are you getting comparable value?

Key Takeaway: Rigorously define success metrics and ROI before you start. Right-size your project scope, budget, and product selection to ensure value accrues to your organization, not just the vendors.

Navigating the ERP Maze: A Consultant's Final Thoughts

Despite these frustrations, I'm not leaving the industry. My 'love-hate' relationship fuels my commitment to helping organizations navigate these challenges more effectively. Understanding these potential pitfalls is the first step towards making smarter decisions and deploying technology in a way that genuinely serves your business needs.

ERP software can be powerful, but it demands a clear-eyed, strategic approach. Don't blindly follow the hype or underestimate the risks.

What's your experience? Do you love or hate ERP? What are the biggest challenges you've faced? Share your thoughts in the comments below!