5 risks in implementing BPM
BPM (Business Process Management) is in essence a concept for managing an organization’s business processes. Spherical BPM in vacuum allows to increase efficiency of use of resources of the company. I believe that in the situation of a permanent Russian crisis, BPM is one of the main optimization tools. But even if you have convinced shareholders, in addition to standard project risks, do not forget to consider BPM-specific:
The main risk - you can create a powerful tool that does not solve the problem of business. Or decides, but partially. The introduction of BPM implies a reduction in the time spent on a business process, for example, due to its optimization or the release of human resources. If this is not the case, or only partially, the costs and implementation efforts may be wasted.
As with all projects, there is a “risk of additional changes” after the project has already been agreed and signed. Typically, BPM-software allows you to make small changes without meeting deadlines and increasing cost. But keep in mind that most likely you will have to balance on a thin perch called "This change entails a significant increase in cost" and "This feature is not supported in the current release."
It is tempting to try to implement important and necessary but unsupported functionality on BPM software. Implement only the functionality required by the BPM project.
')
After the BPM project is started, you may find that the project is stalling due to the fact that some activities must be completed / completed before the BPM starts. And you cannot influence these activities. Therefore, it makes sense to make sure that the necessary software is installed, that it is the appropriate version. What remote servers are available on the right ports, etc.
BPM changes the work of the organization. It changes the working methods of employees. And people do not like change, they are afraid of losing their jobs, prestige and power. New technologies scare employees, and they will rest assuredly resist change with all their might. According to experts, about 40 percent of employees negatively perceive the introduction of BPM.
The success of BPM depends on how quickly the deployment went, how many employees adopted this tool as a worker. It is very important that usability is simple and clear and does not cause a wave of hatred even among those employees who accept changes. And it is very important for the management to bring the main advantages of BPM and support the project at the stage of implementation and further use.
The article is not a dogma and an axiom, but an invitation for discussion.
1. Implementation does not solve the problem of business.
The main risk - you can create a powerful tool that does not solve the problem of business. Or decides, but partially. The introduction of BPM implies a reduction in the time spent on a business process, for example, due to its optimization or the release of human resources. If this is not the case, or only partially, the costs and implementation efforts may be wasted.
2. Unexpected changes.
As with all projects, there is a “risk of additional changes” after the project has already been agreed and signed. Typically, BPM-software allows you to make small changes without meeting deadlines and increasing cost. But keep in mind that most likely you will have to balance on a thin perch called "This change entails a significant increase in cost" and "This feature is not supported in the current release."
3. Use BPM for what it is not intended for.
It is tempting to try to implement important and necessary but unsupported functionality on BPM software. Implement only the functionality required by the BPM project.
')
4. There are no preparatory work.
After the BPM project is started, you may find that the project is stalling due to the fact that some activities must be completed / completed before the BPM starts. And you cannot influence these activities. Therefore, it makes sense to make sure that the necessary software is installed, that it is the appropriate version. What remote servers are available on the right ports, etc.
5. Resistance to change
BPM changes the work of the organization. It changes the working methods of employees. And people do not like change, they are afraid of losing their jobs, prestige and power. New technologies scare employees, and they will rest assuredly resist change with all their might. According to experts, about 40 percent of employees negatively perceive the introduction of BPM.
The success of BPM depends on how quickly the deployment went, how many employees adopted this tool as a worker. It is very important that usability is simple and clear and does not cause a wave of hatred even among those employees who accept changes. And it is very important for the management to bring the main advantages of BPM and support the project at the stage of implementation and further use.
The article is not a dogma and an axiom, but an invitation for discussion.
Source: https://habr.com/ru/post/213621/
All Articles