{"id":27143,"date":"2019-06-04T07:10:19","date_gmt":"2019-06-04T12:10:19","guid":{"rendered":"https:\/\/centricconsulting.com\/?p=27143"},"modified":"2023-09-19T17:21:35","modified_gmt":"2023-09-19T21:21:35","slug":"improving-business-processes-to-make-way-for-robotic-process-automation","status":"publish","type":"post","link":"https:\/\/centricconsulting.com\/blog\/improving-business-processes-to-make-way-for-robotic-process-automation\/","title":{"rendered":"Improving Business Processes to Make Way for Robotic Process Automation"},"content":{"rendered":"
To improve or not to improve, that is the RPA question?<\/p>\n
Sorry to Mr. Shakespeare for taking such an iconic line and turning it on its side, but it is fitting when we speak about the current RPA environment.<\/p>\n
For those who are unaware, robotic process automation (RPA)<\/a> is a way to enhance the work experience by taking routine, repeatable, and rules-based tasks and turning these into software robots (bots).<\/p>\n Then you use your choice of RPA tools offered by a multitude of vendors.<\/p>\n However, this blog is not necessarily about RPA. It is about the process you want to automate and whether you should first improve the process or automate \u201cas is.\u201d<\/strong><\/p>\n In conversations I\u2019ve had with individuals and organizations across a variety of industries, there is a consistent stance for improving processes first and then automating. I, too, am in the \u201cprocess improvement first\u201d camp.<\/p>\n Generally, if a customer chooses automation with no thought on improvement, I recommend otherwise. Automating as is, ultimately results in establishing an inefficient process that returns poor results, immediately.<\/strong><\/p>\n There are organizations that take the approach to automate everything brought to their attention with the intent of running it for some time, capturing the learnings, and going back and improving the process so they can modify the automation afterward.<\/p>\n The issues I see with this plan are two-fold:<\/p>\n I learned early in my career an acronym I have used in all my projects and engagements. DIRTFT<\/strong>, pronounced \u201cdirt foot,\u201d stands for \u201cDo It Right The First Time.\u201d <\/strong><\/p>\n I am a firm believer in taking the time (and cost) upfront to review and make a process more efficient before looking at the potential for automation. Throughout that review and improvement of the process, you may find at the end of your improvement cycle, you create a process efficient enough automation is no longer needed.<\/p>\n Or, you may find there are other technologies already available in your organization that might supplement your process without the need for an RPA automation cycle.<\/p>\n Regardless of the outcome of your analysis, the first step you should take is a thorough review of the process.<\/strong> So, if at the end of that review RPA is still a viable solution, you are already ahead in meeting process requirements. Another plus for the \u201creview for improvement first\u201d camp.<\/p>\n Now, this does not mean every process needs an initial in-depth evaluation determining the need for improvement first.<\/p>\n I have spoken with organizations that have automated right from the start, knowing in some cases the \u201ccode\u201d is throwaway code because their longer-term strategy includes a larger overhaul of the process or processes, as well as the applications used as part of the process. They believe short-term automation provides a lift for their long-term plan. If your organization agrees with that approach, consider this option.<\/p>\n As you look at your processes for improvement and automation opportunities, to enhance the automation experience, keep the following areas and decision points in mind:<\/p>\n Automate simpler processes first,\u00a0then focus on more complex processes only when the company matures its RPA presence.<\/p>\n A few areas to take into consideration:<\/p>\n This is not a comprehensive list, but a starting point.<\/p>\n If you are unsure as to whether a process is too complex for automation, take the following points into account as you perform your analysis:<\/p>\n <\/a><\/p>\nImproving Processes First<\/h2>\n
\n
Take the Time to Review<\/h2>\n
Exceptions to the Rule<\/h2>\n
Is Your Process Routine, Repeatable and Rules-Based?<\/h2>\n
\n
What is Driving the Need for Automation or Efficiencies?<\/h2>\n
\n
What is the Complexity of the Current Process?<\/h2>\n
\n
In Conclusion<\/h2>\n