During a recent conversation Rudy Kuhn, Celonis’ Lead Transformation Evangelist, told me that, “transformation only succeeds when processes are continuously monitored, improved, orchestrated and harmonized.”
Automation projects are complicated because they often touch numerous, interrelated processes that span systems, departments and workstreams.
According to EY, as many as 30-50% of initial robotic process automation (RPA) initiatives fail because organizations, among other reasons, target the wrong processes, automate an already inefficient process or don’t consider what happens after processes have been automated. In Deloitte’s Global RPA Survey 2018, the authors emphasized that organizations must focus on processes as part of their RPA journey. “Put simply, process complexity drives robot complexity: it increases the cost and difficulty to design and implement RPA, increases operating costs, and increases business disruption,” wrote the authors.
So what does a process-first approach to enterprise automation look like?