This post is also available in: Spanish
The correct implementation of a BPM suite will improve the entire organization. It will bring weaknesses to light and strengthen all activities. However, it requires substantial Changes in Management and even in understanding the way work is performed therefore it’s not risk free.
Many BPM projects still focus on Process Reengineering on a theoretical level therefore it would be very difficult to justify the time and cost spent in relation to the benefits gained.
For individuals and for organizations, any change involves moving away from the usual, well known and tested function (comfort zone), towards a new function, which could be perceived as risky or threatening (danger zone), therefore if measures are not taken to appease concerns it could considerably ruin the success of any project.
As a process management implementation project using a BPM suite affects all or most of the company, its success largely depends on appropriate change management in the people orientated organizational culture, ensuring alignment of thought/ action which in turn leads to the coherence and coordination of actions focused on achieving results.
The change causes incertitude as the results are unknown until it is in place. Therefore rejection to change is general and affects those responsible for the change and everyone involved in it.
Basically, this fear is appeased if each and every participant believes that they will benefit from the change. Thus, the change can only happen with managerial involvement and the participation of leaders who motivate the staff. Staff will become involved when they are treated as active subjects, have responsibilities and feel important and valued within the company.
Problems with change management can differ depending on the role of the participants. There are two possible roles:
- The role of process implementer and modifier: basically, those responsible for the change, including managers, executives and intermediary heads of various departments through which the processes flow and all Users in their role of helping to define the processes by giving their opinion of how work is actually performed and suggesting possible improvements.
- The role of the User who’s day-to-day work involves executing process tasks.
Understandably, a large number of staff will assume both roles, because in addition to being system users they may participate, to a greater or lesser extent, in the implementation.
The change will affect these people in both their roles, indeed, the greater their participation in the implementation, the greater their motivation and positivity toward assuming the change as a user.
The biggest help these entities will receive to make the change in BPM projects will come from the platform itself. If the interface of the worktable and of each task is designed with the users’ wellbeing in mind, the work will be comfortable and problem free and the initial rejection will transform into satisfaction and efficiency.
With AuraPortal automated workflow operations are extremely comfortable, much more so than if AuraPortal is not used. The fact of writing everything on the computer screen is more of a break than a burden. Having AuraPortal does not mean more work; on the contrary, work is reduced. The proof is that when people start to use this system and discover how easy and efficient it is, they wouldn’t contemplate working any other way.
In fact, as soon as a process is running:
- The system itself is the driving force that distributes work to everyone who should execute an action of any kind, in accordance with the Process Diagram, the Business Rules applicable to the process and the annotations made by each participant.
- Each of these people, on receiving the task in their personal agenda, does their work according to the task instructions, expresses their opinion and completes the task.
- Each task contains all the necessary data and documents for the executor to complete their work without having to leave the task, even if they are contained in other integrated applications used by the entity. The executor does not need to look for information; the information comes to the user.
Therefore problems usually come from the role of process implementer, in particular from the managers of the different departments through which the processes flow, as transversal processes may clash. However, system users are likely to accept this new software.