The 5 project risks during implementation

projectrisico 1 elkaar niet begrijpen.jpg

Risk 1: Misunderstanding each other

During an implementation it is very important that everyone speaks the same "language". Each company has its own language with specific terminology, even general generic terms can have their own content within an organization. An implementation partner, on the other hand, uses an application jargon, which is difficult to translate into the company's own vocabulary. Without a shared language, misunderstandings arise which can have a major impact on the success of the project. Having a good translator or interpreter who can bridge the gap between the company's own terminology and the implementation jargon is invaluable to achieving this common language.

Risk 2: Too complex

Often the complexity within an organization is overestimated. Being able to present the important issues in an understandable, simple way is important to achieve a good result. Identifying the core of the activities is of great importance here. Since not everyone in the organization is able to distinguish the main issues from the side issues, internal guidance and consultation is needed. Also, keep the 80/20 rule in mind before trying to implement all the exceptions within your company.

Risk 3: Unclear scope

When the scope of a project is not clearly defined beforehand, people (unconsciously) create expectations that will not be met. Only when it is clear what will be done (and especially what will not be done), a project can be brought to a positive conclusion.

Risk 4: Scope changes during the project

A clearly defined scope, as described above, is not sufficient. The defined scope should be monitored during the project. Only when necessary, it is justified to change the scope during the project. How you deals with this, must be agreed upon beforehand. You have to take into account that every change of scope has consequences. When changing the scope, these consequences for the project (e.g. in terms of timing and/or budget) must be clear.

Risk 5: Not enough commitment

The success of an implementation does not depend solely on the commitment of the implementation partner. The involvement within the own organization is at least as important. Sufficient time must be set aside for the project team and for training the entire organization. Management must also be strongly involved, since this type of implementation project goes much further than an IT project. It is a business project that, if done well, will have a direct impact on the success of the organization. Knowing why changes are being made and what the expected benefits are will motivate people. Change management can help here, as well as involving as many people as possible in the project and its preparation. This can only enhance the success of your implementation.

"Everyone wants change, but no one wants to change."

i.deeds has developed an approach that ensures that these pitfalls are avoided. If you would like our support with your project, please do not hesitate to contact us!