- ERP is about your business, not the technology.
- ERP initiatives are very challenging.
- Selecting the right software is the first step in a successful ERP implementation.
- No ERP software is perfect. All have their strengths, weaknesses, and tradeoffs.
- A business blueprint is the second step to an effective ERP implementation.
- Business process re-engineering should happen before, not after, you implement your ERP software.
- ERP software best practices and pre-configured solutions do not solve all the challenges of ERP.
- SaaS ERP won’t eliminate all of your risks, either.
- Your project will fail without adequate organizational change management.
- Executive buy-in and support is critical to ERP success.
- The “A-Team” is critical to ERP success.
- There is no “one size fits all” ERP strategy.
- If your operations and ERP system are misaligned, it’s probably not the software’s fault.
- Expectations are high, but most ERP implementations don’t properly define the “finish line.”
- Most organizations strive fore “no customization,” but most fail to do so.
- You don’t have to implement ERP all at once.
- In addition to planning, implementation is also about execution.
- If you don’t measure it, you won’t achieve it.
- It is important to recognize the “canary in the coal mine,” or signs that your implementation may be in trouble.
- ERP success and benefits realization is largely determined before the implementation starts.
Posts You May Like:
You may already know the various culprits that can contribute to ERP failure. While software issues can derail a project, the most common culprits are related to the implementation approach. One example of a common failure point related to an organization’s...
Project planning can help your initiative stay on track, but rarely does everything go according to plan. There will undoubtedly be times during your project when your plans are threatening to change, and your organization will need to be able to manage these changes...