I don’t believe in BPM!! Because…
1. BPM has been there from long; nothing new - A Myth
Reality Check: Business process management is not a new word but the concept of BPM as a discipline has only evolved in last few years. Earlier we used to see that happening on hard code. BPM as a discipline is an evolved quality method, in a way, for applying to process improvement and monitoring programs. Now we have dynamic visual process diagrams which can be configured to suit the business needs. What benefits and ease these BPM tools offer these days, were unthinkable a few years back. They bring extreme agility and nimbleness to the organizations.
2. BPM is applicable for complex processes - A Myth
Reality Check: Some of the most important business processes are short and simple processes. BPM enables managers to make quicker, better and more-informed decisions. BPM brings more visibility to all stakeholders, owner, managers and participants. BPM lets managers foresee future problems using trend analysis, improve organizational efficiency, minimize risks, enforce organizational policies, comply to regulatory compliances and make processes seamless.
3. BPM is only a workflow – A Myth
Reality-Check: Although BPM started out as a workflow modeling tools - it has now evolved into a full life-cycle that includes modeling, process execution, process monitoring, reporting, process simulation and process optimization. Every BPM tool includes modeling, execution, monitoring and optimization capabilities.
4. BPM is for programmers – A myth
Reality Check: The better BPM tools do not need programmers or the IT department to create workflows. These tools are web-based wizards enabling process participants / users to create workflows by themselves because they are drag-and-drop. This enables business users to create their own workflows based on real business needs. But for the first time, they may need help of the development team, who can build, operate and transfer knowledge to the process participants / managers.
5. We can handle business rules in Java or C# - A Myth
Reality Check: It is a myth because though it is possible, they are simply hard coded and never allow user community to change the business rules on the fly. It involves heavy dependability on the development team for execution, forcing to follow manual overrides or work-arounds till the change is affected. BPM enables effective way of incorporating the business rules in the processes and also change them on the fly.
6. BPM projects are long term projects – A Myth
Reality Check: Most BPM projects can go live in less than 90 days for immediate processes. Deployment and final touches like trainings take an extra few days. If BPM is intended to be done across the organization for all processes, it can be done in sprints of 90 days. The hardest part of the BPM project is actually getting the brainstorming done sufficiently at the stage of freezing the business pain points and defining the objectives. Project that starts with a lacuna at planning stage can end up with a lacuna.
7. We are focusing on automating processes but not rules – A Myth
Reality Check: The key misconception here is to think that one can do effective process automation and digitization without digitizing and automating the business rules. These business rules are sometimes in policies or in the heads of process participants or hard-coded in existing applications. If these rules are not digitized and automated, what you end up with are process bottlenecks. BPM tools have smart objects with help of which we can configure the business rules.
8. BPM is expensive – A Myth