RPA Process Candidate Checklist
Michael McLaughlin
VP Strategic Alliances and Co-founder & Co-host of the Previously Learnt podcast
When discussing what processes a company should automate, I often get asked the question - What makes a good Robotic Process Automation (RPA) candidate?
So I thought this might help:
Structured Process - Could a set of task instructions be easily given to a new employee?
- If processes can be defined and communicated to new workers, they are typically good automation candidates
Clear decision logic Could the decision points be defined and documented?
- Automations follow defined workflow and rules based logic. They are not Artificially Intelligent
Defined or definable workflow -Is there a workflow guide or runbook?
- An existing runbook or workflow is not essential but assists the speed to build the automation
Uses multiple application or tools Does execution require the use of multiple systems and/or applications?
- Processes using humans as the interconnection between systems make good candidates for automation
No emotion or subjectivity Is there room for ambiguity or feeling in the process?
- Processes requiring human judgement are not typically good candidates for hands-off automation. They may still be suitable for assisted automation (i.e. automation carries out the work based on a human decision or approval)
Prone to human error Is there a high rate of error or high impact if errors occur?
- Automated processes will operate with zero human error and this provide significant benefit
Unfulfilling Is the process repetitive, mundane and unsatisfying
- Removing low-end human work improves employee satisfaction and makes better use of human skills
High volume / low to medium complexity Is there a high volume of activity?
- Supports a return on investment for the solution
Low volume / high complexity Is there a lower volume but high complexity/long execution time?
- Supports a return on investment for the solution
24 hour operation Does the process (or could the process) run 24 hours a day?
- Automations can run 24/7 so are well suited to processes requiring 24 hour operation – or those that could be 24/7 given an unlimited workforce
Legacy or external applications Does the process use legacy applications and/or external systems (i.e. owned by a provider or customer?)
- Automation can manage processes using legacy or external systems which could not be automated using other methods
Part automation Is there a volume of repetitive and defined work which requires human judgement to initiate, approve or define?
- Processes do not need to be 100% automated to deliver benefit, and often the Virtual Worker can be configured to do the bulk of the work, based on human initiation, approval, or authorisation
Hope it helps, let me know if you have any questions...
Associated Vice President | Enterprise Architect | Specializing in BFSI & Next-Gen Tech Solutions - PRINCE2, AA Advanced RPA
6 年nicely covered?