How do you identify initial RPA focus areas
It has been quite a while since corporate corridors are abound with news of digital disruption especially Robotic Process Automation (RPA) and AI impacting every walk of life from employment to healthcare diagnosis to retail.
While strategy heads and digital officers have amassed enormous amount of information on trends in Automation, one key question that we face while working with clients is on identifying the right starting point. In this post, I would like to share some of the pointers that will enable you to identify areas within your organisation where software bots can be effectively leveraged.
The best way to start is to have an analysis of the nature of employee deployment and identify areas where they are performing the following:
- manually accessing and gathering data from several different applications to complete their activities
- manually moving data from one system to another
- manually checking the consistency of data between multiple systems
- manually updating the same information in multiple systems
- waiting for alerts/events to initiate their activities
- manually remediating data across several accounts
The above pointers would help you shortlist the processes that are possible contenders for automation. The next logical step to further pin down would be to consider:
- Whether the process is something which can be clearly defined
- Whether process is driven by business rules or whether human judgement takes precedence
- Whether the frequency of the process is significant to be considered for automation
It would also be worthwhile to classify and prioritise tasks from an organisation perspective. The following table indicates a typical classification summarised based on our experience.
|Business Drivers||· Strategic digital initiative constrained by legacy integration
· High in-bound call volumes
· Complex corporate products
· Process to be closed monthly or quarterly
· Regulatory filings and reporting
|People||· Teams of size greater than 15.
· Teams own the processes
· Knowledge workers/large teams handling low value tasks
|Process||· Percentage automated is lesser than fifty percentage of the processes
· Temporary or outsourced workers used and cases where data sensitivity
|IT||· Cases where numerous legacy platforms are used which requires prolonged
|Location||· High cost and high growth countries/ cities|
|Compliance||· Internally controlled functions that have direct control on tools and processes
· Regulatory pressure on continued use of manual processes
Opportunity identification and prioritization is the key in any RPA adoption. Having worked with several clients, especially in BFSI, 10XDS has developed a rapid top down framework based on the key functions in an organization. Do reach us for more details at firstname.lastname@example.org