Put on your best Forrest Gump impersonation and repeat to yourself, \u201cProcess is as process does.\u201d Of course, this isn\u2019t the exact line from the movie, but you get where I\u2019m going. How does Forrest Gump apply to robotic process automation (RPA)?<\/p>\n
Sit back, enjoy a box of chocolates, and let me explain.<\/p>\n
Automation<\/a> uses technology to carry out tasks without any human intervention. RPA is a specific type of automation that mimics how we interact with our keyboards and mouses to carry out specific, often shorter, tasks. RPA is programmatic: it functions by following specific instructions in a specific way, which means it has the power to simplify processes if it\u2019s programmed to do so.<\/strong><\/p>\n I can count the times an organization reviewed its current processes before deciding to automate. When that happens, all I can think about is Forrest whispering in my ear, \u201cProcess is as process does.\u201d Without understanding the process it wants to automate, an organization puts itself in a tricky situation. As one of my colleagues likes to say, \u201cWhen you automate a bad process, you get the same bad results, faster.\u201d<\/p>\n When you automate a process, you\u2019re moving the work from a human actor to a digital worker. But if the process already had issues, the work would end up with the human actor for cleanup. Automation without proper planning does not simplify processes, nor is it a very efficient use of your resources.<\/p>\n So, how can you avoid automating a bad process<\/a>? Repeat three simple letters: USA, USA, USA!<\/p>\n I first learned the USA approach to RPA from a colleague I met at a speaking event. We met months ago, but I mention our conversation whenever I speak with customers, prospects and even our internal resources. While USA can\u2019t solve every automation issue, it will always provide you with an effective use of your time and resources.<\/strong><\/p>\n Does anyone truly understand the intricacies of their processes? Probably not, and that is why it is so important to understand as deeply as possible its execution, its touchpoints, its failings and its results. Without spending time with the people who use this process every day, you cannot make an informed decision about whether you should automate this process.<\/p>\n When you conduct a discovery session<\/a> with the process\u2019 users, you can record your discussion and the work done on the user\u2019s desktop. In some cases, a discovery session reveals the potential exceptions to the process\u2019 execution. All of this information is essential as you move to the next step: simplification.<\/p>\n Simplifying the process is nearly impossible without understanding how it works once executed. You can either make assumptions to attempt simplification, or you can collect more data.<\/p>\n However, simplifying the process too much could diminish the overall quality of its output. Instead, lay the process out step-by-step and determine how RPA can achieve the same level of quality but in fewer or more refined steps. Once you reach that desired quality, you can move to the final step: automation.<\/strong><\/p>\n Once you understand and simplify the process, it is time to automate. Or is it?<\/p>\n Many organizations jump into automation without evaluating whether they should automate the simplified process. In some cases, by simplifying the process, the company improved it enough to no longer require automation. Sometimes, an organization can even repurpose its current tools to simplify the process, forgoing the need for RPA.<\/p>\n If you are still unsure about automating the process you improved, ask yourself these questions:<\/strong><\/p>\n Even if you don\u2019t answer \u201cyes\u201d to all of these questions, your process can still be a good candidate for automation. Review the overall process again and decide if you can automate certain pieces and keep others in the hands of human actors. Automation best covers specific and straightforward tasks<\/a>, which allows your non-digital staff to handle the more complex pieces.<\/p>\n\n
Understand<\/h3>\n
Simplify<\/h3>\n
Automate<\/h3>\n
\n
Conclusion<\/h2>\n