Business is Changing! Don’t Fight it – Embrace It!
A key challenge with any ERP implementation is changing business requirements. Yet many project teams are surprised when business requirements change. Think about it, the scope of an ERP implementation is based upon a “point in time” solution. Competitive business models are constantly evolving to meet customer demands. Today, the majority of ERP implementation approaches discourage changing requirements by having laborious scope change control procedures that tends to be more of a roadblock than an enabler. What is required is a more proactive approach to identify differentiated requirements that can provide a competitive advantage to ERP customers.
What Are Differentiated Requirements?
Differentiated requirements are business requirements that will support a business solution that is uniquely different from another business solution. They allude to a significant, comparative difference. Differentiated business requirements are very useful in ERP software selections because they focus on the unique differences between the ERP software packages. In the context of an ERP implementation differentiated business requirements refer to unique business requirements that are different from company’s peers or competitors. Consider the following illustration:
Allow me expand on a couple of thoughts:
- Differentiated requirements are not best practices. Best practices are common and generally accepted business practices across a specific industry and/or country. Best practices are generally available in the market and therefore are not competitive (or no longer competitive).
- Differentiated requirements should focus on competitive business requirements that uniquely position a customer’s offerings in the market. Practically speaking, a customer should be more concerned about being competitive in revenue-generating business processes (i.e. Order to Cash) rather than revenue-supporting business processes (i.e. Expense Reporting).
- Competent ERP software is designed to address generally accepted best practices. ERP software will not address the unique competitive business requirements of an individual customer.
Handling Differentiated Business Requirements Late in the Game
Now comes the challenge of handling differentiated business requirements late in the implementation. If you notice I did not say we should address all requirements. There are risks associated with addressing business requirements at the end of an implementation cycle. The question you need to ask is whether the business requirement will create more business value than the implementation risk generated. There are four steps you can take to address differentiated business requirements:
- Reduce the possibility for late competitive business requirements by proactively searching for these requirements during earlier stages of the implementation. This will require a competent understanding of business processes, their key results, and how they can be competitive.
Maintain a business solution modeling (a.k.a. prototyping) environment to quickly determine how the differentiated requirement can be addressed. Business solution modeling will enable simulations on how the three components of a business solution could support the competitive requirement.
Best Practice: There should be no more than 3 prototyping iterations for an ERP implementation. If you need a 4th iteration then some thing is not right and a project analysis should be performed.
- Plan for this scenario to happen. Let me restate that the scope for an ERP implementation is based upon a point in time solution. This scenario should be formally listed as a risk and managed as such. This scenario is almost a certainty for a revenue-generating business process (ex. Order to Cash) given the external competitive forces at work.
- Develop a roadmap during the implementation to articulate how new or advanced business requirements will be handled in the future. Too often a customer may believe that they have only a single opportunity to get both their needs and wants addressed in the ERP software.
Just as we expect a customer’s organization to adopt change with an ERP implementation, project teams need to expect and embrace change for differentiated requirements. The key challenge is identifying which requirements are competitive and strategic. Too often we narrowly focus on functional areas and not the entire business process.
This is a challenge that all three key players of an ERP implementation (software providers, implementation partners, customers) must address. Please do not underestimate this under-appreciated challenge. It can be a huge mindset change for business owners that focus more on functional optimization rather than strategic customer advantage. The best strategy for addressing late requirements is to plan for this scenario and have the appropriate iterative processes in place to quickly define, assess, and implement requirements that have competitive value to the customer.