Through the treacherous years of manual processes, outdated legacy systems, inaccurate performance data and internal operational breakdowns, most organizations are ready for a heavy dose of business process reengineering.

Everyone has different opinions of what business process reengineering actually means and what its correlation is to ERP implementations. Our team has found five common myths about business process reengineering that we will share along with a healthy dose of reality check:

Myth 1: ERP project teams should focus on “to-be” rather than “as-is” processes. If you are an ERP vendor or sales rep, current-state processes probably don’t affect your day-to-day. But if you are the organization making the changes or the employees doing the work every day, then the current processes absolutely do matter. It is critical that you assess the current state of your processes to help you define the future state as part of your business process reengineering efforts. This also helps you define the gaps between your current and future state so you can communicate change impacts to employees. 

Myth 2: Business process reengineering can be done without organizational change management. Many executives think that they can simply redefine and implement business processes without organizational change management. However, this is a very misguided view of how to enable process and system changes. The most effective business process reengineering efforts succeed largely because of the way change management is addressed – not because of how well the processes are defined on paper.

Myth 3: You can’t reengineer business processes before knowing which software you are going to implement. Obviously, screen transactions and menu options are driven by specific ERP software, but the how, what and when of what your business actually can be defined independent of software. For this reason, it is advantageous to map and improve your business processes prior to selecting and implementing a new system.

Myth 4: All business processes need to be overhauled before selecting and implementing a new ERP system. Some executives believe that they need to evaluate, redesign and reengineer their entire business prior to selecting and implementing a new ERP system. However, this is not the case. The most successful organizations focus on improving their core areas of competitive advantage, while letting non-core business processes follow the lead of the software’s out-of-the-box functionality.

Myth 5: Business process reengineering will cause your ERP system to take more time and money to implement. The Achilles heel of many failed ERP implementations is that they assume that “doing things right” will cost more time and money than if they cut some corners along the way. While it may look good on paper to strip out any extensive business process work, the reality is that your project will most likely take longer to implement and fail at go-live if business processes are not adequately addressed. Remember it is much less expensive to do things right the first time than to clean up after an ERP failure.

If you have hopes of a successful ERP implementation—and let’s face it, everyone does—be sure to keep a realistic view in mind and don’t cut corners. And, as always, beware of these five deadly myths.

Posts You May Like:

ERP vs EPM: Do You Know the Difference?

ERP vs EPM: Do You Know the Difference?

While there are many different enterprise solutions on the market, enterprise resource planning (ERP) software and enterprise performance management (EPM) software are two solutions that many companies, across industries, consider for their business.  While these two...

HRIS vs HCM vs HRMS: What’s the Difference?

HRIS vs HCM vs HRMS: What’s the Difference?

According to a recent global report, nearly 50% of companies are currently using some form of HR software-as-a-service (SaaS) or platform or a hybrid solution. In 2019, only 20% of companies had adopted such strategies.  Are you thinking about implementing HR...