Is Your Business Process Right for RPA?
One of the most interesting technology solutions to arrive on the business application stage over the last few years is robotic process automation or RPA. RPA takes a bunch of other solutions that each had their place in a narrowly defined environment and brings them together to create a more powerful tool capable of automating many more business processes. The sum is greater than the parts!
So, what is it? In layman terms, RPA is a tool which teaches a user’s computer to automatically perform a series of manual tasks. These manual tasks could include:
- Logging into a website and finding a certain piece of data related to an individual record
- Entering a located piece of data from one system into another system
- Creating a new record, folder, or user profile for a new user or employee
- Reading a business card and entering it into a CRM
I am sure you can think of many such tasks in your own life as well as your organization.
One terrific example is the onboarding of a new employee. Historically this process involves many paper or scanned documents, dozens of individual data points, data entry into multiple systems, and perhaps even the printing of paper documents for an employee folder. This process can take an HR manager several hours per employee to complete. Yet in the world of RPA, once the source documents have been digitized, the tool can handle all these tasks in moments leaving an HR director more time to focus on the impactful elements of his or her job.
But how can you decide if RPA is a solution for your business tasks? The answer – or at least a clue – may lie in the following table which is divided in four quadrants with the current level of digital processing across the x axis and the level of complexity up the y axis.
Complexity is the amount that the steps of a task change from one instance to another – irrespective of number of steps. An example is the processing of invoices from a single vendor which are unlikely to change from invoice to invoice. On the other side of that coin, the processing of all the documents defining a relationship with a vendor (which includes invoices as well as financials, POs, LOA, and correspondence) is complicated and may require previously undefined steps often. Preparation of tax schedules that may reference checks, websites, and statements from any number of providers is another example of a task with steps that can change from instance to instance.
Current level of digital processing represents the portion of the steps that are processed by the computer. Anything that requires paper obviously possesses a low level of digital processing. But reading scanned handwritten documents is another process that requires human intervention even though it is done on a computer.
It is not surprising that some processes are not candidates for RPA. Anything in Quadrant II where the process is manual, changes with each instance, and requires expertise and human intuition will not automate – even when done on a computer. A clear example is custom software development where an individual must think through the solution and test that it does what was intended.
Quadrant III includes processes that may go either way. Clearly the manual steps will need to be processed by a human, but the static nature of the activity suggests that some automation may be possible. An example of a Quadrant III task that can’t be automated by RPA is picking grapes (a duck walks into a bar…). But a process of recording retail shrinkage (theft and spoilage) which involves physical measuring of inventory followed by computer processing, distribution, and recording could benefit from some RPA.
Quadrant I offers additional opportunities for semi-automation. Tasks in this area are fully digital but require lots of manual intervention. Both of my examples of complication above, preparing tax schedules and defining a relationship that includes many types of digital documents are examples that can benefit from semi-automation.
Quadrant IV is where RPA really shines. Regardless how many steps are included in each task or how many tasks are included in each process, each component can be easily defined and does not change from instance to instance. Returning to my example above, it does not matter how many different systems are involved in the onboarding of a new employees, if they are all accessible from one computer and are the same for every new hire, an RPA robot can be used to complete the entire task. Do you have processes in your organization that meet the criteria of Quadrant IV?
Clearly this post is an over-simplification of possible scenarios and avoids the inevitable gray areas between quadrants, but this is only intended to get you thinking about how RPA might be useful in your organization. If you are seeking deeper answers to your RPA questions, stay tuned to our future posts or give one of us at Netrix a call. We would love to help you explore the efficiency improving and costs savings that RPA may be able to deliver.