You've made the decision to implement RPA in your organization—awesome! Now, how do you choose the best process to begin with? How can you evaluate which ones will deliver the highest ROI? And what's the right approach to building an effective RPA implementation plan? Keep reading to find out.
Tech Lead and Solution Architect
We're living in the age of automation, and it's undeniable.
From simple Excel macros to the sophisticated algorithms powering Tesla's GigaFactory or Google X labs, countless scripts, software bots, and machines are being developed daily to make work faster, more efficient, and of higher quality.
However, automation is often just a buzzword. Startups sprinkle it into their pitch decks while operation executives include it in every other strategy plan. In many cases, these proposals lack substance—mere buzzwords without a deeper exploration of the subject.
But when done right, automation can work wonders! Boosting ROI, reducing payment cycles, eliminating repetitive tasks, and minimizing operational errors are just a few of the benefits. The potential is limitless.
So, how do you begin automating your business? Which processes should you prioritize? How do you avoid common pitfalls and ensure successful implementation?
You'll find the answers in this article. Keep reading!
To determine the most effective automation for your business, it’s important to assess the
complexity of the tasks you want to automate. Here are the main options available:
This approach is ideal for automating simple tasks within a specific application. It usually takes just a few days to deploy and is limited to one application. Common examples include Excel macros, Outlook rules, and SAP scripting.
Written in programming languages like PowerShell or Python, these scripts can automate more complex tasks but still have limited interaction with applications. Development and deployment usually take a few weeks.
Tailored specifically to your needs, these fully custom applications automate multiple complex processes and tasks all within one system. While the possibilities are endless, so are the costs. Full deployment can take months or even years.
When considering the question, “Which processes should I automate?” it's crucial to know how to select the right ones.
From my experience, most processes within an organization are ripe for automation. However, the key question at this stage is: is it truly worth automating? For instance, if a manual process takes only a few hours per month to complete, but automating it would take six months to develop, the question is: can it be automated? Yes. But should it be automated? Probably not.
The next section will guide you through the initial process selection, after which a thorough evaluation should follow. You may also find our article on RPA metrics useful to gain deeper insights into what you should prioritize.
Here are the key factors to consider before deciding which processes to automate:
When selecting and planning processes for automation, it's essential to avoid these three key mistakes:
It can be tempting to dive into high-impact projects, especially when new technologies promise quick results. However, without sufficient experience, you may discover that the process is far more intricate than anticipated. Often, employees may not be fully aware of all the underlying rules, and new requirements may emerge during development. This can lead to unforeseen challenges and delays. It's always wiser to start with simpler tasks where possible.
Many processes share similar applications or logic. By recognizing these common elements, you can reuse parts of the initial automation for subsequent tasks, making development faster and more cost-effective. For example, even if four processes don't seem worth automating individually, their shared components can result in a 40% cost reduction when developed together, turning the business case into a viable one.
Sometimes, automation projects are initiated simply to fulfill a KPI or out of frustration with a repetitive task, rather than being driven by genuine business value. However, automating processes without evaluating their cost-effectiveness or the ongoing maintenance required can waste resources and negatively impact your automation KPIs, leading to a poor perception of RPA in your organization.
To dive deeper into this topic, check out our article on common RPA failures and why it's crucial to work with experienced technical RPA developers.
As highlighted, there are many important factors to consider before diving into your first RPA implementation. This guide aims to provide clarity on the steps to take.
If you're still uncertain about which processes to automate or what the next move should be, don't hesitate to reach out to Destan. Our RPA consultants will audit your current processes and help you identify and automate those with the highest potential for boosting your ROI.
Krzysztof Szwed
Tech Lead & Solution Architect at Destan. Formerly with KPMG.
Made with love in Warsaw – the Centre of USA, by Destan
All rights reserved 2019-2025
