These days, there is a multitude of reasons to create huge implementation projects. And to be honest, each single argument to add to your project scope can make sense. No doubt about that! However, the question is, what have we learned from the ERP/CRM implementations that we’ve seen in the 300+ years combined experience?
To give you some insight:
- Customers are often optimistic when it comes to estimating their available time, skill sets, focus and motivation
- During the implementation, it’s not easy to stick to the initial plan
- Implementation projects have the tendency to take longer than expected
- These so called ‘big-bang’ implementations have caused disruption and sometimes even temporarily paralyzed complete organizations
- In today’s fast changing world, initial project principles can quickly become outdated
The conclusion is that huge and long-lasting implementations with a wide and flexible project scope can be problematic if not handled with care and experience. Not rarely, the problems become greater than the benefits. And the possible disruption of your day-to-day operation can cause a reduction of customer loyalty. Or even worse.
Implementing new software, adapting, and modernizing your business processes and creating a fresh, new company culture means an enormous effort for your organization. And it demands a lot from your teams. Especially because you also have a business to run. So, the alternative for a big-bang approach is to split the project into several smaller steps. And have the discipline to stick to the plan.
A small step method
A series of smaller project steps delivers numerous advantages. A shorter ‘time-to-value’ and the possibility to adapt more quickly to changing circumstances are certainly two of them.
In today’s fast changing world, we all must get used to constant change. Change is the only constant. It is no longer the right mindset to implement a perfect ERP or CRM solution that you will then use for 5 or 10 years. It’s more effective to consider your digital transformation journey as a process rather than a project. And just like with marketing collateral, most likely as a process that is never finished.
How do you implement Business Central in Small Steps?
Business Central, and it’s predecessor NAV, were always implemented as a fully Engineered To Order (ETO) solution – with full project management, design, consultancy, development, etc. For larger more complex projects, this is still often the best route; our team has the expertise and processes to make sure that we deliver projects successfully - and with our customers informed as to important milestones etc. However, since we launched Accelerated Business Central (ABC) a fast and modular implementation of Business Central, many companies have been enjoying the benefits of the modern cloud solution without the need for a large and disruptive project. As those businesses grow, they can make changes, and add functionality as required.
Accelerated Business Central
Aimee Thompson
Before joining the Dynamics team, Aimee had worked as a Junior Content Producer. She is currently the Sales and Marketing Apprentice - aiming to achieve a level 3 qualification, BSC Principles of coding and a CIM qualification.