EY claims robotic process automation (RPA) project failure rates can go as high as 50%. It appears that for all the experiences we’ve had from the days of ERP (72%), CRM including Salesforce (70%) SCM (70%), and MRP (76%), it is still as much about missed expectations and excessive hyperbole (on the part of vendor sales teams), as well as the inability to create a framework for deploying a solution based on how a company operates.
Most of these systems are built by programmers, systems analysts and engineers who may have some sense of how things are done in the outside world – I mean outside of the development labs of the software companies building these products – but few would likely understand – outside of focus groups and second-hand information passed on to them by product managers – of the unique properties and circumstances by which a business operates.
At this juncture, we asked Vinayak Mohan, associate director, Cognitive Automation and AI, KPMG China, who uses the analogy of cooking to illustrate the elements that would translate to a successful RPA project.
Watch the video to hear more of what he has to say about RPA projects done the right way.