In the world of ERP, there’s a term and strategy that’s gaining traction: the so-called “adopt not adapt” approach. It encourages businesses to use best practice software solutions as they are, rather than customising them to fit their internal processes.

An abstract image representing adopting on the left compared with adapting with the right

What is the “Adopt Not Adapt” Approach?

“Adopt not adapt” is mainly associated with cloud-first models, which are typically characterised by being provider-hosted, accessible across multiple types of device, sold on subscription-based models, and notably, include evergreen updates.

Key aspects of “adopt not adapt” include:

  • Avoiding customisation: Businesses are advised to, or aspire to, use the software as it is, without making modifications to suit their specific needs. This can fast-track implementation and avoid the costs and complexities associated with upgrading customized solutions.
  • Embracing best practice scenarios: Companies are encouraged to re-/define their processes based on best practice scenarios provided by the software.
  • Regular product enhancements: The approach promotes the acceptance of regular product enhancements, which in the case of D365 F&O are available four times a year.

The Benefits and Challenges

The benefits of adopting a system and minimising customisation are faster implementation, lower costs, and easier upgrades.

The main challenge is that the approach represents a significant cultural shift for many businesses. Existing processes may (i) be considered “unique” by the business, which is rarely the case, (ii) be deeply entrenched, and/or (iii) be dependent on specific individuals and their knowledge. These factors make it harder to prepare for and implement the change necessary to successfully adopt.

Summary

The “adopt not adapt” approach is a bold strategy for businesses looking to streamline their ERP implementation process. By embracing best practices and avoiding unnecessary customisations, businesses can potentially save time and resources.

However, it’s crucial to carefully consider specific needs, circumstances, and culture of a business, recognising that any software chosen will necessitate some level of organisational change.

In reality, there’s happy medium to be found somewhere between all out “adopting” and all out “adapting”. Keep “adopt not adapt” as a mantra, to maintain focus on a key goal of ERP implementation; improving business processes and efficiency.

Published by Mike Pearsall

Mike is a founding editor of AX7 - The D365 F&O Blog. He is a business and solution architect with experience of successfully implementing D365 F&O on both client and partner side, as well as strong knowledge of the wider D365 suite and Power Platform.

Join the conversation

5 Comments

Leave a comment

Your email address will not be published. Required fields are marked *