4 min read
Aug 30, 2022 9:57:33 AM

Robotic Process Automation (RPA) has caught the imagination of business leaders and garnered huge investments in the past few years due to its ability to enable business users with limited programming experience to automate process quickly and realize huge business benefits – Improved Operating Cost, Better Customer Experience, Compliance etc. While these projects cannot replace the enterprise level technology projects executed by the IT teams -that automates mission critical processes and routines, expected to be reliable, and built to scale- it surely can take on low key processes, reduce the IT burden, and accelerate value creation by empowering employees with simple RPA software that require very little learning.

Robotic Process Automation Journey

A majority of organizations, irrespective of their size – Be it a Fortune 2000 or SMB- typically follow the bottoms up approach of starting small usually within a specific function -like Finance, HR, Procurement, Global Service Centers, Back Office Operations- that are rule based and with limited deviation from the set process, to prove out the concept, showcase the success and try to replicate RPA to other parts of the organization.

As these departments and organizations mature, they seek out advanced tools like Intelligent Process Automation (Combination of AI/RPA), HyperAutomation (E2E Process Automation), Custom Automation, Low-Code / No-Code Automation to address use cases that are considered too complex for the basic RPA to address.

Accelerated RPA adoption – Pit Falls

It is common for departments leaders to increase the automation investment basis the initial success, for other departments and eventually the organization to follow the suite. There is suddenly a proliferation of unmonitored, silo’ed automation bots running across the organization that could turn your RPA journey into a nightmare:

  1. Disruption to related processes - Automation opportunities are mostly identified by process Subject Matter Experts (SME) – Like AP/AR Analyst, HR Analyst, Back Office Associate, etc.- While they might be experts in the process that is under their direct scope, they are separated (by org. structures) from the upstream/downstream process that might be impacted. Situations like these usually results in gains to the process in scope but a whole lot of rework to related processes.

  2. Decentralized License Procurement and Bot Utilization - While the Bot licenses are a fraction of the price of a Full-time resource be it Domestic or Low Cost Location, The licensing and the upkeep cost could easily spiral out of control especially when departments taste early success and double down their bets independently. The departments procure licenses, duplicate purchases from multiple RPA Software vendors capable of delivering the similar outcomes, invest in varying tools (AI/Cognitive Services, Process/Task Mining, RPA, RDA Licenses) from various RPA Software vendors for the lack of an Wholistic Enterprise Automation Strategy. The bot utilization management is another area that is often overlooked, this can tremendously help unlock the economies of scale and help reallocate the budget to advance the automation journey benefit taking a wholistic enterprise approach

  3. Broken Bots and Lack of formal support structure - RPA bots usually operate at the presentation layer, mimicking how an employee would go about executing a task. Simply put, a bot scrapes data from various screens, performs the desired function per the process, and updates target data fields. Changes to the underlying system or its presentation layer will cause the bot to malfunction, fail, or execute incorrectly. It is common for departments to invest in building bots but assume that the same developers will also support these bots for life. The Bot developers usually have a day job (AP/AR Analyst, HR Analyst, etc) and if it comes to maintaining the bot or doing their day job – it is a no brainer. Additionally, they are not expected to follow the coding best practices as a Developer in the technology department would. It is thus common to that the bots are eventually rendered obsolete with the attrition of the bot developer. It is thus critical to consider the investment towards a formalized support structures to maintain, update and upkeep the automation programs to realize the desired business value.

  4. Bots built without a fixing faulty processes or logic, will automate defects - The Bots will perform the action exactly how it is programmed to, so if a program is built to automate a process that is broken, inherently faulty or consistently yields defects – the bot will accelerate this exact faulty process and throw out the defects at a faster pace and the department will be buried with rework that needs be executed manually. So what should have yielded productivity gains ends up being the exact opposite and delivers poor customer experience. It is a best practice to evaluate the process for deficiencies, fixing or re-engineering it before building automations.

  5. Increased risks due to non-compliance with established organizational Information security policies or industry norms - While RPA can be leveraged to improve information risk and compliance by letting the bot handle processes that deals with personal and sensitive data like social security, credit card. The level of secure handling of such information is dependent on the RPA developer. Sensitive data and bot passwords handled by the bots, may be exposed to hackers if the enterprise/ industry specific information security policies and procedures are not incorporated as part of the code. The RPA password are often exchanged so that they could be reused, if this vulnerability is exploited it can provide the intruder access to the sensitive data as well as access to the network, which can be further exploited. These incidents can be extremely expensive to overcome and cost several hundred times the productivity benefit. It is thus imperative that RPA bots be built to standards and periodically audited for information security risks and mitigated.


Interested in discovering where you're at in your RPA journey? Contact our team today for a maturity assessment.

Get Email Notifications