ERP: Do and don't
There are many factors to consider when introducing a new ERP system
This article was written by Lennart Garbarsch, CEO of Tabellae A/S.
In all modesty, I have followed more than 200 ERP implementations (from the sideline) over the past 12-14 years. The vast majority of ERP projects have ended well, but there is no one who has only had clean days of sunshine along the way. There are always challenging periods in a project - and this is where the ERP partner's strength and ability really matters.
Many projects have "developed" in both scope and implementation time. Most often, this is due to the fact that knowledge is gained in a project and new opportunities for gain are identified. And that's good! However, there are also projects where a slightly different focus could benefit from dribbling the project even better to the finish line. It has given me a number of experiences that I will share with you.
10 good advice
1) Select ERP partner with specific knowledge within the field of the business before choosing ERP system.
2) Avoid encoding functionality that can be purchased in standard tools.
3) Adapt to the company's business model. Don't buy it with "we start with 100% standard" without there being a plan (and a budget) for the further course.
4) Agilt can mean "too dynamic" and can be abused in projects where you might "think" that you work agile without doing so.
5) Cloud or not? It is not an easy question, but it is important to understand that "life on the ground" must also work (eg. printers, label machines, on-premise systems)
6) Digital transformation requires integration. Often between many systems and processes. Most preferably without a lot of coding - because then it is easier to maintain.
7) Fixed prices only apply to "fixed scopes". Therefore, new knowledge and new recognitions cannot be handled at a fixed price. NB: There is nothing called "fixed scopes".
8) Focus on the "output" of the ERP system early in the process. The output is the interfaces and business documents that the customers see. They just have to be perfect. Your customers are basically uninterested in your new ERP system version XYZ.
9) Set internal time for tests. It doesn't make much sense not to have allocated enough time for this part. You have time!
On the other hand, if this part is not planned, it can lead to panic, overtime, budgetary delays and burnt out employees. Your ERP supplier and Output Management supplier can help and have experience with this part - but you have to carry out these tests yourself.
10) Use standard software and "Best of Breed". It is perhaps cheap, but not smart to use an ERP provider's home-coded solution for something like time registration, data / document integration or bank transfers. You will depend on this ERP provider, regardless of whether the rest of the delivery is better handled by another in the future.
Contact Tabellae to hear how YOUR business comes best through the introduction of a new ERP system.