In this series, we’ll discuss how to choose the best processes for Robotic Process Automation (RPA), including everything from starting small to laying out the final path before development.


For many companies, unprecedented change is taking place, from greater acceptance of remote work to investments in technology that can help an organization be more efficient.

One of those technologies “taking the world by storm” is Robotic Process Automation (RPA). RPA takes routine, repeatable and rules-based processes and automates them, replacing a human actor with a digital worker, so the human actor can focus on more value-add activities.

Many organizations that begin their RPA journey are not as successful because they do not take the time needed upfront to review and assess processes that are viable for automation. They feel everything can or should be automated without determining return on investment (ROI) versus cost to build and maintain (in addition to licensing costs for the software). As we like to say, “automating a bad or non-viable process just gets you the same bad results faster.”

Over the course of four blogs, we will walk you through those areas that you should address as part of your RPA intake and analysis process. We will begin with Analysis and Ideation, followed by Feasibility and Priority, Discover and Document, and finally, Design and Approval.

Read the Blog Series:

Our four-part series will cover the following:

Analysis and Ideation In part one, you’ll learn how to start small with one team or department. You’ll also start on your process intake methodology so that you can find the best process ripe for automation.

Feasibility and Priority We’ll cover why you need to establish a scoring template for choosing processes in part two. We also examine how to prioritize processes for automation, and a bonus in this phase: discovering processes that need optimization.

Discover and Document During part three, we discuss what to do after you’ve chosen your process for automation. It starts with engaging with subject matter experts and ends with starting an important document: the process definition document (PDD).

Design and Approval — Lastly, you’ll learn about the final steps for creating the PDD and how to create the solution design document (SDD) so you can move into development and deployment.

Final Thoughts

Over the next four weeks, we will go into greater detail on each part of the intake and analysis process for RPA. Return for each one so your first steps on the RPA journey can lead to a long, successful engagement.