Balancing system integrity and customizations in ERP: Are you equipped to navigate this delicate balance?
In the world of ERP systems, striking the right balance between customization and stability is key. To navigate this delicate balance:
- Assess core business needs to determine essential customizations without compromising system integrity.
- Regularly review and prune unnecessary customizations that may clutter or destabilize the system.
- Implement robust testing protocols for any new customizations to safeguard against potential disruptions.
How do you maintain the equilibrium between system integrity and customizations in your ERP experience?
Balancing system integrity and customizations in ERP: Are you equipped to navigate this delicate balance?
In the world of ERP systems, striking the right balance between customization and stability is key. To navigate this delicate balance:
- Assess core business needs to determine essential customizations without compromising system integrity.
- Regularly review and prune unnecessary customizations that may clutter or destabilize the system.
- Implement robust testing protocols for any new customizations to safeguard against potential disruptions.
How do you maintain the equilibrium between system integrity and customizations in your ERP experience?
-
Have seen many ERP implementations fail primarily due to too many customisations. The core team should be well versed with the features available in the new ERP that is being implemented. If the core team has to be totally convinced that the standard features of the ERP can address the problem in hand, they need to convince the end users on not undertaking any customisation. End users would want the ERP to replicate their legacy software l and end up with too many customisations. This will impact the stability of the system and would also create trouble when the ERP needs to be upgraded to the latest version.
-
Usman Ghani
CEO & Co-Founder | Empowering Startup with SAP Integration | 20+ Years of ERP Excellence
The less customization you implement, the less pain you'll suffer in the future. I always advise clients to avoid customizations whenever possible and keep their core clean. Before opting for customization, ask yourself why your business process can't fit within the standard solutions. if Fortune 500 companies can manage within standard ERP functionality, why can't you? A clean core will help you in smoother upgrades, better scalability and long term system integrity
-
Would suggest taking end users into confidence first. Success of an ERP depends on its actual usage. Suggest to have open mind in acknowledging this fact. Need a way around to accommodate unforeseen business scenarios. Be open to integrate with other bespoke / products, if any. Identify and keep a good Coach who can keep motivating the team thru the tough times of implementation by focusing on the future benefits. Implementing ERP is like constructing a bridge. Need to go thru lot of pain first to gain later. Be careful to ensure that no pain no gain is clearly communicated. Quick fix and handling the initial & stabilisation phase is extremely crucial. Aspects of insecurity can’t be underestimated. Alternative roles maybe communicated.
-
When assessing whether or not you should customize your ERP solution, follow this 5 step process: 1. Assess if the requirement that is driving a customization request can actually be met in the OOTB product. If so, leverage OOTB and don’t move to step 2. 2. Assess if the process in question can be modified to work OOTB. If so, mold the process and don’t move to step 3. 3. Assess if you can eliminate the process. Try to understand if the process / requirement is actually creating value or not. If you can eliminate, don’t move to step 4. 4. Assess if you can leverage a 3rd party ISV solution. It is always better for someone else to manage the code. If you fine one suitable, don’t move to step 5. 5. Customize.
-
In an ever changing world, it’s easy to say “clean core” and “be standard” but it’s easier said than done. As always people, process and systems come in order. The people have to be prepped using the change management processes (Prosci is my fav) before the processes are standardized using industry specific processes (best practices) and then use the system functionality (bummer that many industry processes are not built in to many of the standard ERP systems) there are frameworks such as TOGAF which can help build the architecture. Please note that stakeholders have their own vested interests and that in my experience has been the primary reason for extra customizations
更多相关阅读内容
-
ERP ImplementationsHow do you manage ERP scope creep and budget overruns during implementation?
-
ERP ImplementationsHow do you handle the resistance and feedback from your ERP users and customers?
-
ERP ImplementationsHow do you develop and implement a post-implementation support plan and budget?
-
Enterprise Resource Planning (ERP)You’re struggling to lead your team in a new ERP implementation. How can you gain their trust and support?