Tierney - stock.adobe.com

Top 10 causes of RPA failures and how to avoid them

Experts in automation offer insight on why RPA implementations fail in the enterprise and how IT leaders can avoid them to ensure they're getting the most out of the technology.

On paper, implementing robotic process automation, or RPA, sounds like a slam dunk. The tools for programming bots can make it as simple as doing a task while a bot looks over your shoulder. But, in practice, there are several ways that individual bots can fail, and RPA programs can run aground that IT leaders in the enterprise need to address.

Gina Schaefer, U.S. intelligent automation practice lead at Deloitte, suggested that the root cause of many types of failures "stems from a lack of overall vision and direction for the program, defined by the leadership and embraced by the business." But she added that these RPA failures can be avoided with clear direction and guidance. "Scaled automation programs have proven time and again to drive impressive impacts and measurable financial returns," she said.

Here are 10 types of failures enterprises run into when launching RPA programs and tips on how best to avoid them.

1. Governance

Schaefer argued that the most common problem is a lack of governance. Usually, when an organization points to an inability to deliver sufficient ROI, it's because it did not invest in appropriate management and oversight for the program. When RPA was first introduced, it was surrounded by significant hype, causing companies to mistakenly believe it would be a silver bullet. In this case, they may not have approached the program with the rigor it required, assuming the business workforce need only attend a few training courses and they would -- without the support of the IT group -- generate enough extensive automations to scale a program.

"While there are undoubted benefits of user-friendly automation tools in the hands of the business and impressive one-off examples of impact, the vast majority of ROI-generating automations are delivered at the hands of a professional automation team," Schaefer said.

Gina SchaeferGina Schaefer

2. Choice of automation candidate

RPA projects sometimes fail to produce ROI because enterprises choose the wrong automation candidate. It is somewhat easy to find basic tasks that can quickly be automated. In the enthusiasm to drive automation in the enterprise, many managers don't evaluate the benefits against the true TCO. "Just because you can automate something doesn't mean you should," Schaefer said.

The automation bots for easier tasks only create incremental value relevant to a single user. Schaefer recommended enterprises adopt a value-driven approach that looks at automation as an enabler to holistic process transformation rather than discrete task automation. This way, the bot can have a major impact on an entire function and not just tweak tasks at one individual's desktop.

3. Management challenges

RPA failure often results from the management of the digital workers once deployed to production. On the surface, it may seem that, once the bot is built, the work is done and it will run autonomously with no oversight. "In reality, an automation is more like a human worker than a piece of software," Schaefer said. Much like a new employee, the automation will encounter scenarios in its early days in production that it did not see in the training.

While a comprehensive development model that anticipates the handling of these scenarios creates some degree of flexibility, nearly every automation requires a level of retraining until it has operated long enough to have encountered most scenarios. Also, like all other employees, automations experience changes in their environment, most of which require updates to the automation.

"A well-run digital workforce maintenance program should not only ensure the bots are optimized to deliver at their peak performance, but should also monitor and report on the measurable value delivered by the automations and the overall impact to the business process holistically," Schaefer said.

4. Scaling challenges

Bots are a great stopgap measure for many scenarios that involve copying data from one application or system to another, but they can face scaling challenges compared to direct API integrations. Russ Felker, CTO at GlobalTranz, a logistics service and freight management provider, found early RPA success but ran into these kinds of problems when the company started deploying more bots.

Russ FelkerRuss Felker

"Bots are a great technology but, like any technology, has a point of diminishing returns from a scaling perspective," Felker said. As the information sets and frequency of data moves increased, the bots consumed a similar amount of resources.

Felker and his team explored throwing more compute resources at the bots, reducing the frequency of data breadth and depth moved by the bots or moving to a more direct integration outside of the bot technology. They eventually converted parts of the data movement to direct links between the systems to make data flow more efficient.

"Bots gave us the ability to implement more quickly, but we also realized we needed a more forward-looking monitoring and management policy to identify when moving from a bot to a more integrated process made sense," Felker said.

5. Third-party problems

Felker also found complications in RPA being used to retrieve data from third parties because third-party interfaces aren't uniform. For example, truckers, many of whom operate independently, have traditionally provided paper documents to show proof of delivery rather than use applications. Felker's team determined that automating the retrieval of these documents with RPA would deliver great efficiency and value. But then they had to contend with the realization that documents are not always posted to the same place, with the exact same layout or in the exact same order.

"Bots don't respond to variance very well," Felker said. "The software does the specific things it's asked to do very well but is a bit inflexible."

It's important to remember that bots are not intelligent -- they simply automate rote tasks. If the task set for a bot alters or changes in a way that wasn't anticipated, the bot will fail. GlobalTranz has had this happen occasionally and had to improve monitoring and the notifications within those bots over time to better capture and redirect any issues that arose.

6. Shadow deployments

To avoid an RPA failure, it's important to set guardrails for bot deployments so that frontline users are less likely to make mistakes. "Bots make it easier for people outside of the core development team to essentially create code," Felker said. This can lead to shadow development in organizations and a lack of oversight.

Similar to any other technology, there needs to be proper management, monitoring and logging around the bots. "The ease of bot creation and deployment is deceptive -- it feels so simple to just create a deploy, but without the backing technology and process, the bot is likely to cause more headaches and create more work than just doing the task manually," Felker said.

According to Felker, IT should also work directly with business users and communicate that RPA is only one tool in their IT toolbox. When determining whether a task is suitable for RPA, it's important to ask questions about the variability and repeatability of a task before assigning a bot to it.

7. Unrealistic expectations

"Most of the failures I've encountered center on unrealistic expectations," said Lauren Lang, associate director for the business performance improvement practice at Protiviti, a global consultancy. Many projects begin with hopes of instant gratification. Although this is less prevalent than it was two years ago, it still exists. Some of the results of these types of RPA failures included RPA environments established with flaws, missed requirements that become poor designs and automated processes not tested with production data.

Lauren LangLauren Lang

It's important to keep in mind that there are failures of automated processes and failures of RPA implementations, according to Lang. The failures of automated processes are as critical as the processes they run. For example, an automated process that performs a portion of the payroll processes has the potential to be disruptive to the point of impacting an organization's brand.

Then, there are processes that become more of a nuisance when they fail. An example is an automated process that works to generate and distribute reports. Its impact is low if it simply will not run or produces inaccurate reports.

The impact of RPA implementation failures is especially destructive when an organization is just starting off with RPA. Early failures include flawed infrastructure buildouts, poor requirements gathering and designs, and perceived failures created by unrealistic, early expectations. The impact here is arguably the greatest since RPA can become branded as an abject failure within the organization.

"That leads to people in the organization wincing at the idea of taking on an RPA effort," Lang said.

Applying learnings from early projects is critical. "RPA is no exception to the rule that to learn what it feels like to get burned, one must get burned," Lang said. "The key here is to create an environment that rewards people for overcoming mistakes."

8. Siloed RPA deployment

Most digital transformation projects fail because those who rely on it don't understand how it operates or felt that they were left out of the planning process, said Prince Kohli, CTO at Automation Anywhere, an RPA tools provider. To avoid these mistakes, capitalize on the skill of nontechnical employees who appreciate being involved in bot development and can offer insight into how automation technology can advance business goals. By making the team who'll be using RPA daily feel engaged in the development of the process, they are more likely to buy into utilizing RPA from the beginning.

Prince KohliPrince Kohli

IT is a critical partner throughout the transformation process. Their role is to ensure that the system is scalable, reliable, secure and performs well. Getting nonspecialists involved in the creation of bots helps mitigate the risk of RPA failure for several reasons. At one level, it lightens the workload placed on specialized developers and helps with budgets and recruiting efforts in the process.

"Bringing business stakeholders into bot creation also makes the bots more aligned with the way the business works," Kohli said. After all, who knows the processes better than the people who work with them every day?

9. Poor change management communication

Many leaders fail to think holistically about the organization's culture that will need to adapt and support changes to its working environment before embarking on their RPA journey. "Embracing new technologies is not easy, particularly RPA, as it not only stands to change how individuals perform their jobs, but will transform the behavior of the organization as a whole," Kohli said. Therefore, communicating these changes effectively, listening to employees' concerns and securing their buy-in are essential for success.

It's also important to train employees' skills and their ability to navigate this new bot-human culture. "Just as we train new drivers before they hit the road, it is important to ensure that your employees understand how to operate RPA technology, how to build bots and how to perform their new, bot-enhanced roles," Kohli said.

10. Improperly defining success criteria

IT leaders also inadvertently doom their automation initiatives from the start by failing to define success, Kohli said. Understanding the desired outcomes at the beginning sets up the entire journey for success, yet oftentimes, organizations embark on RPA with a sole focus on cost savings. While saving time and money is certainly valuable, this view is so narrow it obscures other tremendous value-adds of a successful RPA adoption. These include the quality of the deployment, overall productivity increase and, most importantly, its impact on people.

After taking the time to identify the goal, it becomes easier to identify a plan and focus on processes that ladder back to that overarching vision. Processes must be evaluated against attributes that showcase RPA's key strengths. Kohli advocates for identifying processes and ranking them on key attributes, such as being rules-based, involving structured input, and having high volume and high error rates. These will be better candidates for automation and will ultimately have a greater impact on the organization.

"Benefiting people is, in my opinion, the most valuable aspect of RPA as it provides an invaluable impact, such as increasing employee happiness and satisfaction," Kohli said. "Engaged employees are more productive, healthy and less likely to leave to greener pastures."

Dig Deeper on Digital transformation

Cloud Computing
Mobile Computing
Data Center
and ESG