Making minor Mistakes is normal Many companies
in the SME sector
are still new to ERP

This is because the project managers are usually newcomers in the fields of ERP, CRM or digital transformation. Making minor mistakes is therefore normal and unavoidable. Nevertheless, project management should attach importance to the following points.

ERP Project = Company Project

Your ERP project should be a company-wide project - and not a project for which only certain departments are responsible. Of course, there are also “natural” contact persons in the project who are particularly familiar with a topic due to their specialist knowledge. However, this does not mean that this person is automatically responsible for implementation.

Of course, a structured ERP project plan with clear responsibilities is essential - otherwise your project would be a mess. At the same time, however, the rigid departmental boundaries and thus also the so-called “silo thinking” must be broken down for the project work. **Cross-departmental thinking and acting is necessary for your success.

The rule is:

ERP Project ≠ Routine

In day-to-day business, the processes and structures are clearly defined - everyone knows where to start and when. And this well-established routine is very important, as it is the only way to ensure that day-to-day business works efficiently.

In the project, however, things look different again. These rules do not exist here. There can always be unexpected situations that need to be responded to. More flexibility is required here.

Ongoing Project Responsibility

The above-mentioned responsibilities in the project must be clearly defined in the project preparation phase. This is because constantly changing responsibilities mean that the team has to constantly readjust to working together. This would be a huge time waster for your ERP implementation and would set you back again and again in the project plan.