The Biggest Challenge for ERP Implementations: Defining Business Processes and Workflows
There are seven
critical challenges that can disrupt an ERP implementation if not addressed
appropriately:
1. Program management
2. Business process and workflow definition and
improvement
3. Organizational change management and
communications
4. Business and technical integration
5. Globalization and localization
6. Independent oversight of technical resources
7. ERP benefits realization
Insufficiently
defining business processes and workflows is the biggest challenge in
implementing ERP. After that other major challenges are poor program management
and not enough focus on organizational change management. The fact that
business process and workflows are such a potential land mine for ERP
implementations is not surprising for a number of reasons. There are six main
reasons why this presents such a challenge for organizations:
1. Unrealistic expectations. Many of the companies expect that
implementing a new enterprise solution will simply transform their business
overnight, without carefully defining and engineering “to-be” business
processes and workflows. This unrealistic expectation helps explain why; most
ERP projects take longer than expected.
2. Vendors often oversell and oversimplify. Many vendors oversell and oversimplify their
software’s use of industry best-practices and streamlined business processes.
While their software will inevitably improve business processes, they still
need to be defined in the context of the implementing company’s operations and
business policies and procedures.
3. There are often complex processes outside of
the ERP system. Business processes
may entail activities to be completed in the ERP
system, but chances are,
there are also processes that touch other systems or manual processes. These
non-ERP processes need to be incorporated into the overall workflows in order for
employees to better understand them.
4. Most ERP systems are very flexible. Most modern ERP solutions are extremely
robust and flexible, so even a simple business process such as creating a sales
order is likely to have multiple variations. In cases like this and hundreds of
other business processes, it is not enough to say that you are going to simply
adopt the software’s processes; even those workflows need to be defined, which
takes time and resources.
5. Business processes are a source of competitive
advantage. While some business
processes, such as general ledger or financial reporting, are not sources of
competitive advantage, other core functional areas are likely to differentiate
your organization from competitors. For this reason, it is not always advisable
to simply adopt vanilla functionality that can be easily replicated by others
in your industry.
6. Employees need well-defined processes. Processes and workflows need to be clearly
defined so employees can be adequately trained. Software developers and
implementers have very different process definition needs than employees, who
will ultimately be responsible for performing the tasks. Organizational change
management, communications, and training activities are effective only with
well-defined business processes.
ERP software is not implemented by simply plugging it in and
assuming business processes and workflows will fall into place. Instead,
organizations need to carefully define and re-engineer their processes. By
keeping the above points in mind, your organization will be less likely to
overlook a key, but often overlooked, component of an effective ERP implementation.
Comments
Post a Comment