So you have been through countless meetings and discussions with your peers, managers, executives, and anyone who would be a tad interested in Business Process Management, and how a BPM platform would not only streamline line-of business processes but also improve the overall efficiency of the organization. You tried every possible way to convince people in your organization that “process” is not just about drawing rectangular blocks on a blackboard, or post-it notes on large paper boards, but about the methodology that encapsulates process improvement and the larger gain that such a methodology could provide to the organization in the long run. You discussed how process improvement and management could provide better ROI, increase efficiency and visibility, and improve collaboration; how a BPM system, model-driven framework and Service Oriented Architecture would increase the rate of deployment of business critical processes. And you received those blank stares, subtle smirks, or outright rejection from people who could not understand the need for “another” methodology.
Finally, just when you think that you have no more energy left to fight the “process battle”, your manager gives you a shot to prove your point. Even before you feel relieved that your voice has been heard, you have your task cut out. Questions linger, for which you have to find solutions quickly. There is no time to “stand and stare”. Where do you start? How do you select the “right” process? How do you get a quick win out of your process implementation (improvement) project? How do you convey the right message to the stakeholders?
The answer lies in the 3 P’s for continuous process improvement: Process Discovery, Process Optimization and Process Implementation. The 3-P’s are like three pillars that form the base of your process improvement effort. Just like a house, the process will fail without a strong foundation. The process improvement effort is similar to building a house because you always start with the base first and ensure that the foundation is strong enough to support the overlying structure. While defining the foundation for the improvement effort, the following should be thought about:
Once you have a solid understanding of the above requirements, the next step is to devise a roadmap for the improvement effort, by following the below mentioned steps:
Selecting the right “first” process can be quite a daunting task. The key is to find a balance between departmental and cross-functional processes. While initiating process efficiency and improvement efforts, always “Think Big, Start Small and Scale Fast”. Always keep the big picture in mind. Think about processes that have a high impact on your line of business; processes that are directly connected to your organization’s revenue streams or those that directly or indirectly impact your customers; processes that when improved will garner the interest of managers and executives alike. Some examples would be:
Once you zero in on your process, think of the value that you would want to showcase. For example, if you choose to improve the Incident Management process, you may want to think in terms of faster resolution rates, increased transparency, and real time updates on customer issues. Also, while deciding on which process to improve (as your first process), try to pick one that caters to a single department or maybe two. Do-not try to pick the most difficult process as the first one to improve. Doing so may jeopardize the opportunity at hand. For example, if you pick the “New Hire Onboarding” process, keep the integration with external systems (payroll systems, benefits systems etc.) for the second iteration; focus on how immediate changes or smaller improvements can reap huge benefits. For example, sending reminder notifications to the HR manager regarding the start date of a new hire to ensure that all last minute actions are taken care prior to the new hire joining could be considered a significant improvement.
Once the process to be improved is discovered, the next step is to think about optimizing the process. Very often we fall into a labyrinth of “lean, value-add, non-value add” steps and spend too much time over-analyzing ways to improve the process. Since the process you have chosen will have to go through a few iterations before really becoming “lean”, try to keep it simple in the first phase. Yes, you heard it. Be prepared for iterations or continuous process improvement. But the key here is to think of the big picture. Have a roadmap for your process improvement initiative. Divide the effort into phases and set the expectations at the outset. The following are the important steps to consider during the optimization phase:
Increase Incident Management process efficiency
By stating the goal explicitly, you can measure the success rate of the process improvement effort post implementation.
If you do-not have enough time to get members of different Business Units to be part of the Steering Committee, just stick with the current sponsor. You can include more members as you make progress with the process. What you must realize is that when you hit a roadblock, take an alternate route (in this case postponing the creation of a steering committee to a later date).Remember you do-not have to get everything right the first time. Learn to improvise. While defining measures, do-not be extremely aggressive by stating that the process will decrease the cycle time by more than 90% during the first iteration. Be cautious not to go overboard or overstate what the goal might be. The primary outcome of the process improvement effort should be to showcase how a well-defined, process-centric methodology coupled with process measures can improve business critical processes.
Once the process discovery and process optimization steps are taken care of, the next step is the actual implementation of the process. The question here is how quickly can you implement the optimized “To-Be” process? Are you going to build the process using the traditional “Software Development Life Cycle (SDLC)”, or are you going to do rapid development using BPM systems. The answer to this question may vary depending on various internal factors, such as the development practice at your organization, time to implement and resource availability. If your organization already has a BPM suite but has no idea how to use it, you just hit the jackpot. Traditional ways of implementing processes can be time consuming and resource heavy because most of the process implementation onus is on the development team. Also, the process owners see the final product only at the “testing” stage and usually find discrepancies between the initial vision and developed process. Changing functionality due to change in requirements might lead to further delays in releasing the improved business critical process and this may hamper the initial momentum that you may have gained for the improvement effort. BPM systems create a level playing field wherein the process owners can rapidly model the improved process flow, implement changes by leveraging the robust model-driven framework and be actively involved in every step of the implementation.
If you keep the 3-P’s in mind during your process improvement efforts, you will definitely see incremental gains, which will lead to huge future gains and steer your organization toward a more well refined process-centric mindset. The key to a successful process improvement endeavor is not how many processes you implemented but how many that you implemented made a difference in enhancing business critical processes and in setting your organization on the process super-highway.
Bio-- Naveen Adibhatla is a business process management enthusiast and evangelist. He currently oversees business process management at RingCentral Inc. He may be contacted at nav.adi@gmail.com
There are no products in your shopping cart.
| 0 Items |
Membership at BPMInstitute.org includes access to our other communities
