The Second Deadly Sin of ERP Implementation
#2: Less-Than-Thorough Requirements Gathering
Organizations invest in ERP to enable greater execution and efficiency. So it makes no sense to implement a solution that simply automates your existing processes.
It’s easier and faster to take that approach. But as business process improvement experts say, automating a bad process just makes the bad process faster.
Your ROI will be better and time-to-transformation shorter if your implementation team and users make the effort to analyze current core processes, identify pain points, chokepoints and problems, determine needs, and then clearly define a future state.
Comprehensive requirements gathering is the foundation on which successful implementations are built. Shorting or eliminating this vital step is how organizations end up with limited gains or a clumsy, unsuitable partial-fit solution
Do not start implementation without setting clear objectives, determining specific requirements, and knowing exactly how you want your core processes to look.
The 7 Deadly Sins of ERP Implementation
Some mistakes are just bad strategic or financial decisions. Some are the inevitable consequence of situational or organizational factors. Some, however, are the result of process-oriented or people-centric choices – and are easily avoided. These are The Seven Deadly Sins of ERP Implementation.