RPA - Let's stop putting lipstick on a pig

I suspect that Process Improvement methodologies increase productivity and save money more than RPA ever does. At General Electric Six Sigma famously gained $700 million in corporate benefits in just two years, in the first five years the benefits were in the order of $10billion. Here is a good article about it: Why Six Sigma Certification and Training Reduces Company Costs (sixsigmadaily.com).

If all the main RPA software vendors added up all the benefits from all their customers globally, would it come close to this $10 billion benefit in one US company?

Is it time to stop talking about RPA and related IA technologies without also always talking about Process Improvement? My view is that RPA works best when it is an enabler for a Lean Six Sigma (LSS) team and using RPA without process improvement just leaves us 'putting lipstick on pigs' by automating tasks that are part of broken business processes.

No alt text provided for this image
Figure 1: RPA without process improvement


As part of the ‘Managing Change’ pillar in my last article (How to scale an RPA capability (also titled 'It's not rocket science!' ) | LinkedIn) I talked about the importance of both ‘Process Improvement’ and ‘Standardisation’ to be able to truly scale RPA.?The banking customer I mentioned found far greater benefit when it redesigned a business process for the robots rather than automating as-is.

Another favourite customer of mine was one of the UKs largest online retailers.?Their RPA COE was based within a Process Improvement team where everyone was Six Sigma qualified.?Their use of RPA as part of LSS methodologies was eye opening to me about how our world should look.?For one project they designed a brand-new anti-fraud process utilising robots that saved the company £13 million per year. ??One RPA project, led by Six Sigma, a £13 million saving.?For this retailer RPA was part of Process Improvement rather than being something separate, last I knew they had 190 robots doing the work of 600 people.

I also remember a business process we were going to automate for a telecom customer, while looking at improving the process for automation, something the business-based COE always did, they discovered the downstream need for the process could be provided in a better way so this six FTE process was no longer needed at all (the offshore team that had been blindly working the process had not been needed for years).?If we had automated the process as-is without putting it through a process improvement filter we would have automated a process with zero benefit.

We all have stories like these in our back pockets.?We also know stories of RPA project failures where we were trying to automate flawed processes.?If all experienced RPA people have such stories then why is my Linkedin feed that is mostly RPA and IA contacts and companies almost totally devoid of any process improvement content? ?Why are we not articulating LSS + automation as what we do rather than just pushing the tech?

There has been a large increase in Process Mining being discussed as part of Intelligent Automation in the last 12 months which is an encouraging move in the right direction. UiPath have their own Process Mining tool, Blue Prism partnered with Abbyy Timeline,?Celonis seems to be getting far more traction. ?This is really promising but a word of warning, these process mining technologies need to be seen as a process improvement enabler, not as a straight to RPA shortcut.?It fills me with dread the idea of these mining tools recording broken business processes as-is and spitting out inefficient automations.?Process Mining belongs to LSS Analysts, not RPA developers. ?The route to automate with these tools should be Mining->Process Improvement->RPA (if robots are part of the re-designed solution).

My recommendation is that every Intelligent Automation business analyst on the planet becomes a LSS trained (I did a designing for Six Sigma course to help me as an RPA consultant 15 years ago).?If we are in the productivity improvement and transformation business we need to be process change experts.?The same is true of the LSS experts out there, they need to also be RPA solution design experts because RPA should be a key part of the business processes they re-design.

RPA should be part of the Process Improvement industry and we should talk about it as such.?Let’s stop putting lipstick on pigs.

Sandip Das

Technical Account Manager | Intelligent Automation |AIOPS Specialist | Pre-sales at Digitate

1 年

RPA should not even be practiced…. if something is programmable then why not to add the same capabilities in the original software/ process itself?

J. Michael Stahl, P.E., PMP

PMO Manager, SencorpWhite & Owner, 6042 Ventures LLC

1 年

I completely agree, process improvement methodologies are crucial for successful automation. Too many companies are trying to apply automation to processes haphazardly. Without improving the underlying processes, automation will only magnify existing inefficiencies and errors.

?? Andrzej Silarow

Automations Team Lead @ The Manchester Metropolitan University | RPA Architect | Blue Prism MVP 2024 | Power Automate | ABBYY | SQL | Ms Access | Azure

1 年

I wouldn't put lipstick on lean six sigma either. There are things that it excels at, and things that it is absolutely not designed for... however some see it as a holy grail, and try to wedge it in by all means. Totally agree with the premise though - RPA is a toolkit very much like CI is. Both can be used separately to fix issues, but when put together, they compliment each other and drive much more efficiencies. The problem here is about smart management and long term planning for company improvement, rather than addressing the "here and now" year on year.

Simon Carter

Global Partner Solutions - GSI's - Microsoft

1 年

Having lived through most of this id say do the following 1) Process Mining for digital process clean up 2) lean Six Sig to eliminate unecessary labor effort 3) Automate or API 4) sync GPT to better interface humans to systems

Kevin Mckenna

Transformation Automation Manager (RPA) at BNP Paribas Personal Finance

1 年

Really good piece, Denis - and completely agree. I find it is nearly always best to firstly review processes using both a "top down, bottom up" approach which should help to fully understand where you need to optimise/re-design...with a view to then decide what you can/want/need to automate. Sometimes RPA might not be needed at all which is fine! Robotic optimisation is also just as important as the human time you save, because building an "inefficient" robotic process will then lead to increased and unnecassary licence consumption in the long run. RPA should be used a fantastic tool to leverage upon as part of an overall Transformation "tool-kit'...to be used in the right way as & when needed ??

要查看或添加评论,请登录

社区洞察

其他会员也浏览了