How to explain Robotic Process Automation (RPA) in plain English

How to explain Robotic Process Automation (RPA) in plain English

What is robotic process automation (RPA)? What kinds of tasks can it handle? Here’s a primer for IT and business leaders – and anyone needing to demystify the concept

158 readers like this
ai rpa fears

If “machine learning” sounds like the beginning of a bleak dystopian future – think The Terminator mixed with The Matrix – then “robotic process automation” must be the phase when the machines rise up to rule humankind with ruthless efficiency.

First things first: There aren’t really any robots involved.

Fortunately, robotic process automation (RPA) involves nothing of the sort, except perhaps for the efficiency part. There aren’t really even any robots involved.

“Robotic process automation is not a physical [or] mechanical robot,” says Chris Huff, chief strategy officer at Kofax.

What is robotic process automation?

Rather, the “robot” in robotic process automation is software running on a physical or virtual machine.

“RPA is a form of business process automation that allows anyone to define a set of instructions for a robot or ‘bot’ to perform,” says Aaron Bultman, director of product at Nintex. “RPA bots are capable of mimicking most human-computer interactions to carry out a ton of error-free tasks, at high volume and speed.”

If that sounds sort of, well, boring – especially compared to the Hollywood robots – that’s by design. RPA is ultimately about automating some of the most mundane and repetitive computer-based tasks and processes in the workplace. Think copy-paste tasks and moving files from one location to another, for example.

RPA automates everyday processes that once required human action – often a great deal of it performed in rote, time-consuming fashion. That’s also how RPA promises to boost efficiency for organizations.

[ Related read: AI vs. machine learning: What’s the difference? ]

Let’s back up for a moment and add some other clear-cut definitions of RPA to our arsenal. Use these to sharpen your own understanding – or to help explain RPA to colleagues, customers, or partners, especially when working with non-technical folks.

5 ways to define RPA in plain English

  • “In layman’s terms, RPA is the process by which a software bot uses a combination of automation, computer vision, and machine learning to automate repetitive, high-volume tasks that are rule-based and trigger-driven.” –David Landreman,, CPO of Olive.
  • “Robotic process automation is nothing but instructing a machine to execute mundane, repetitive manual tasks. If there is a logical step to performing a task, a bot will be able to replicate it.” –Vishnu KC, senior software analyst lead at ClaySys Technologies.
  • “RPA is software that automates rules-based actions performed on a computer.” –Chris Huff, chief strategy officer at Kofax.
  • “RPA is an advanced form of business process automation that is able to record tasks performed by a human on their computer, then perform those same tasks without human intervention. Essentially, it is a virtual robot copycat.” –Marcel Shaw, federal systems engineer at Ivanti.
  • “Put simply, the role of RPA is to automate repetitive tasks that were previously handled by humans. The software is programmed to do repetitive tasks across applications and systems. The software is taught a workflow with multiple steps and applications.”–Antony Edwards, COO at Eggplant.

[ Is your culture agile enough to handle RPA? Get the digital transformation eBook: Teaching an elephant to dance. ]

Is that process a match for RPA?

Evaluating your internal processes and workflows that would be good candidates for RPA is its own story for another day. That said, there are some fundamental criteria worth noting here since they can help you and your team get a better handle on what RPA is and how it could be useful. Moreover, these criteria can help as you discuss RPA with non-technical colleagues elsewhere in the company. One of the big categories: Any processes that require people to do a high volume of repetitive data work.

“RPA is ideal for tasks involving a high level of human data processing,” says Landreman,, the CPO at Olive. “The most common uses of RPA programs supplement repetitive functions or data-intensive processes, where logic-based outcomes are anticipated.”

Landreman, shares four basic check-offs when determining possible RPA fits:

  • The process must be rule-based.
  • The process must be repeated at regular intervals, or have a pre-defined trigger.
  • The process must have defined inputs and outputs.
  • The task should have sufficient volume.

What can RPA do? Example use cases

Show people outside of IT how RPA could reduce drudge work in their day-to-day jobs.

Explaining and evangelizing RPA outside of IT should be a bit easier than doing so for other topics that are harder to distill down for non-technical people, such as serverless or microservices. The definitions above speak to this. It can also be easier to show people outside of IT how RPA benefits them directly by reducing drudge work in their day-to-day jobs. (The same task might be more challenging when it comes to explaining to a field service technician how, say, containerization benefits them.)

“Businesses and organizations like RPA because it helps them improve productivity across a wide range of populations – users, customers, employees, sales and marketing people, business people, accountants, legal and finance analysts, etc.,” says Muddu Sudhakar, CEO at Aisera.

Still, the light bulbs usually turn on quicker with accessible examples of how technology can be used in the enterprise. So let’s return to data-intensive processes as a good starting point. Sudhakar reminds us of how many different actions can attend data: data receiving, data processing, data collection, data correction, data creation, and so forth.

Think about the repetitive processes in business functions such as finance, customer service, and HR.

Consider the amount of this kind of work in an area like finance: Receivables and payables alone have traditionally required tons of manual, repetitive effort by skilled workers. This is why you see lofty predictions about RPA in specific business functions: Gartner, for example, has predicted that 73 percent of corporate controllers will implement some form of RPA in their finance departments by 2020, up from 19 percent in 2018.

Other traditional business units, like customer service and HR, offer their own examples of data-intensive, rules-based, and repetitive processes. Specific industries such as insurance and financial services also fit the bill.

Edwards, the COO at Eggplant, offers this specific use case as an example: Returns processing. Think about the last time you returned a purchase you made online, and what that entails not only for you but also the company from which you purchased. Those “free” returns are really anything but.

“Traditionally, returns processing has been carried out manually and has been a costly endeavor. With RPA, companies can manage returns without adding to the cost or causing a delay,” Edwards says. “The RPA software can now handle the return, which includes a series of repetitive steps: sending a message confirming receipt of the return, updating the inventory system, making the payment adjustment to the customer, ensuring that the internal billing system is updated, and so on.”

The steps involved in returning a pair of shoes that didn’t quite fit, let’s say, map quite nicely to Landreman’s criteria above, for both customer and business. It’s a rule-based process that has a particular trigger and is repeatable; it has specific inputs (such as initiating the return and returning the product) and outputs (such as your refund); and for retail businesses, especially, there’s certainly significant volume.

It’s a necessary process with plenty of “opportunities” for inefficiencies, errors, and other issues. And let’s face it: It’s boring. It’s the kind of process that RPA exists to improve.

“The ability to automate [with RPA] allows workers to switch their focus to more thoughtful and meaningful work while also eliminating data-entry errors that can damage processing times, compliance, and the overall customer experience,” Huff from Kofax says.

[ Want lessons learned from CIOs applying AI? Get the new HBR Analytic Services report, An Executive’s Guide to Real-World AI. ]

Kevin Casey writes about technology and business for a variety of publications. He won an Azbee Award, given by the American Society of Business Publication Editors, for his story, "Are You Too Old For IT?" He's a former community choice honoree in the Small Business Influencer Awards.

7 New CIO Rules of Road

CIOs: We welcome you to join the conversation

Related Topics

Submitted By Abel Sanchez
July 10, 2020

At a time when technologies and market conditions can change on a dime, it doesn’t make sense for companies to craft five-year strategic plans. Here’s what they should do instead

Submitted By Pete Sosnowski
July 10, 2020

DevOps engineers and managers are in high demand. To land a role, showcase curiosity and past achievements

Submitted By Kevin Casey
July 09, 2020

Just because you automate a process doesn’t mean you’ve secured it. If you're considering RPA, make sure you understand the security implications


Email Capture

Keep up with the latest thoughts, strategies, and insights from CIOs & IT leaders.