I see this a lot, organizations invest tons of time in analysing and modeling business processes. And they end up with a collection of process models but still don’t know which processes should be automated with BPMS technology. And I think this is because many organizations struggle with how to get started with process automation. For example, should they tackle simple processes first or should they tackle the biggest and most complex process first? How will the processes be categorized to determine which process offers the most value from automation?
Having gone through this process (no pun intended) many times with many organizations, I’ve come up with 5 simple questions that help organizations determine what processes have automation potential and the possibility of offering high value results. Here it goes:
- Do you have any “paper heavy” processes? Is there a paper form that gets routed to different process participants as part of the process?
- Do your process workers waste time looking for forms or documents they need to complete a specific step?
- Does the process require manual duplication of data? Where maybe an email address has to be manually copied from one system to another?
- Do your processes “hang” because one of the process workers didn’t receive an email that tells them to proceed with the next step?
- Are there other “routine” tasks that are very time consuming or can halt the process in its tracks if the task owner goes on holiday or simply forgets one day?
If you can answer “yes” to one or more of the above questions, you are looking at a process with automation potential. If you’re still not 100% sure whether a process is a good fit for automation or you want more time to figure out the impact of such a “yes” then it’s time to speak to the people who perform the process day in and day out.
But beware, these process owners might be comfortable with the status-quo, in fact they might find what they do today is the ideal process. It could be that many of them have already created their own workarounds to avoid potential process problems. Either way, you should gather these details first hand so you can create the perfect automation scenario that reduces error rates and significantly decreases process cycle times. Would you agree?