9 Robotic Process Automation (RPA) pitfalls to avoid

9 Robotic Process Automation (RPA) pitfalls to avoid

Robotic Process Automation (RPA) is gaining acceptance especially in the finance and telecom industries however we have spoken to a number of executives and there are plenty RPA failure stories, too. We outlined some of the most common pitfalls, leveraging existing papers on the issue like this one by UiPath. We explain these points in detail below:

  • Organizational pitfalls:
    • 1- Lack of time commitment from local team
    • 2- Lack of leadership buy-in
    • 3- Lack of IT ownership
  • Process pitfalls:
    • 4- Choosing a process with insignificant business impact
    • 5- Choosing a too complex process
    • 6- Choosing a process where better custom solutions exist
    • 7- Lack of focus in process selection
    • 8- Striving for end-to-end automation when it is not cost-effective
  • Technical pitfalls:
    • 9- Choosing a solution that requires intensive programming

Organizational alignment is key for any project’s success

Especially in projects where there’s no outside implementation partner, organizational alignment is key because your organization will be responsible for the whole solution. Both local team and leadership needs to be fully on-board, with top management regularly reviewing progress and local teams devoting significant time to automating processes getting help from departments like Strategy.

Adjacent teams that rely on automated processes also need to be notified and convinced in advance and especially in the beginning of automation they should be on the lookout for any issues.

The most important decision is the process to be automated

Ideal process is impactful, simple, lacks a custom solution and is difficult to be automated with non-RPA techniques. Let’s explain all 4 points:

Business impact is key to excite the organization. RPA project on a process with low business impact will have little momentum. Processes with high business impact tend to be high volume, high effort processes that touch the customer. Nothing like telling a CEO we can approve loans in 2 minutes rather than 2 days.

Process complexity is important. Processes involving high level cognitive tasks are bad candidates for automation.

Custom solutions tend to outperform generic solutions and RPA is a very generic solution. For example, Anant Kale from AppZen recently mentioned how some companies are trying to use RPA for expense audits. I think that’s a great example for a process where a high quality custom solution exists. No RPA solution will be able to go into as much depth as AppZen can over an expense item.

AppZen has a database of fraud patterns and built a knowledge layer of where and how people spend for travel and entertainment (T&E). An RPA solution will not have access to any of that data and will likely perform poorly compared to a custom expense auditing solution. However, managing multiple solutions brings new IT complexities so better make sure that the new custom solution is worth the effort of migration.

RPA is not the only mode of automation. Replacing legacy systems or building powerful API interfaces to legacy systems can help you automate numerous processes with less effort than building RPA solutions. Because RPA systems use imperfect screen scraping solutions, upgrading legacy systems offer faster and more accurate automation solutions.

Once RPA demonstrates its value, keeping the organization focused is hard

The first process to be automated will likely be selected with a robust process. If that automation delivers significant value, all senior managers will be excited to jump aboard and start automating their processes. This can lead to a loss of focus as RPA experts are stretched thin due to demands from varying departments. Automation of less critical processes will deliver less value than initial pilot and this can lead to an “automation-fatigue”. Though numerous departments spent significant effort to automate processes, they will end up with little improvement.

To keep the organization motivated, RPA experts should be focused on a limited number of high impact projects. As RPA expertise increases in the organization, individual teams will start to take initiative and automate their own processes. This is the ideal state as automation will improve operations without the need for significant time commitment from senior leadership

Full process automation is desirable but it may not be economical

Many processes are 70-80% automatable without great difficulty. However, as the level of automation increases, businesses face diminishing returns. Automating a process completely may be five times more expensive than automating a process up to 80% because that additional 20% will require automation code that’s a lot more complicated than the code required to automate up to 80%. Process redesign, keeping human in the loop for edge cases are all solutions to operate 80% automated processes with optimal efficiency.

RPA is an evolving field, don’t buy outdated solutions

Bankers, especially those on the technical side, like to boast how they are actually running tech companies and using the state of the art. However when we start discussing how they implement RPA solutions, some have not even heard about self-learning automation solutions. Newer solutions called cognitive automation or intelligent automation (depending on the company promoting the solution) are able to watch as automatable work is performed by humans, learn the automation needed and takeover when ready.

Especially when you are outsourcing your RPA setup to a consultant or BPO, keep in mind that they may have a conflict of interest. Programmable solutions take longer to implement and therefore result in longer billable hours, however such programming may not be needed if cognitive automation is used.

So far these have been the cases I frequently heard from the trenches. Will keep on updating as we hear more implementation stories. Please leave a comment if you have other stories.

Now that you know what to avoid, it may be a good time to learn how to design your RPA implementation or choose the right RPA vendors for your business.

Leave a Reply

Your email address will not be published. Required fields are marked *