Leadership Reflection #13: Why ERP Implementations Fail for the Same Reason Most Change Initiatives Fail

“Do. Or do not. There is no try.” While I may be dating myself by quoting Yoda, I've found there is an uncomfortable truth hidden within that advice. Organizations often treat ERP implementations as technology projects. They aren't, they're actually change management projects. Over the course of my career, I've participated in and led multiple ERP implementations across different industries and organizational sizes. Despite differences in software, vendors, and budgets, the factors that determine success are surprisingly consistent.

The most successful implementations I've seen begin with a clear understanding of why the organization is making the change and the following and how will this help the organization better serve its employees, customers, donors, students, or stakeholders? I've identified the following items as the most critical in successful implementation project:

1. Define Clear Objectives
   A successful ERP implementation begins with clearly defined goals. Whether it's improving efficiency, gaining real-time insights, or enhancing customer experience, clear objectives are essential. When I advised a multinational firm, these goals became our guiding compass throughout the ERP journey.

2. Prioritize Customization
   Every organization is unique, and a one-size-fits-all ERP approach can be a costly mistake. While working with a manufacturing company, we realized too late that our chosen ERP lacked the customization needed for our specific workflows. Prioritizing customization is vital to ensure compatibility with your organization’s processes.

3. Invest in Comprehensive Training
   Implementing a new ERP system is a transformation, not just a technical upgrade. It requires everyone in the organization to adapt. During a healthcare firm's implementation, we initially underestimated the need for training, leading to resistance. Comprehensive, role-specific training resolved these issues and paved the way for smoother adoption.

4. Engage in Regular Assessment
   Ongoing assessments are as important as the initial setup. At one startup, neglecting routine system checks caused minor issues to snowball into larger operational problems. Regular evaluations ensure small glitches are fixed before they escalate.

5. Exercise Patience
   ERP implementation is a marathon, not a sprint. Rushing the process can lead to incomplete implementations, as I learned firsthand with a retail giant. Patience allows for a thorough and more effective rollout.

The biggest lesson I've learned is simple: ERP implementations are rarely technology projects. They are leadership projects. Of course, the software matters. But clear vision, stakeholder buy-in, training, accountability, and organizational readiness matter far more in successfully implementing a new system.

Technology may enable transformation but leadership is what makes it happen.