Digital Transformation Journey

As we all know RPA takes the robot out of the human. In general terms, RPA is a type of software that mimics the activity of a human being in carrying out a task within a process and freeing them to do other tasks requiring human strengths. RPA projects follow Robotics development life cycle (RDLC), very similar to software development life cycle (SDLC), like any IT project. After the process prioritization and requirement gathering stages, the most important phase of RPA development is solution designing. We should give a sufficient amount of time to solution design before any implementation/coding happens because the success & failure of the deployment heavily depends on it. Also let’s make sure that each identified automated process should have a solution design document. While designing the solution we should always keep note of these few points… Trigger Point: Before any real coding or development happens, think about how the BOT will be triggered in the future. It is importa

Someone said very rightly – “Automation is good, so long as you know exactly where to put the machine.” In all my previous blogs I wrote about BOT failure, ROI Modelling, Cost saving, RPA Governance, CoE, POC, POV etc. But then I realized that before taking a deep dive into any of these subjects, first we need to have a right RPA process identification & prioritization methodology in place. Everybody across the industry agrees that Robotic process automation (RPA) can make a big difference for organizations tormented by repetitive routine processes – the kind that suck up the productivity of people whose time would be better put toward more important work. But many are confused by what seems to be a deceivingly simple question — which are the right processes for RPA? The poor choice of process for initial pilot is the leading root cause for failure to meet customers’ expectations. Robotic Process Automation (RPA) doesn’t suit every process and in majority of cases we don’t have

We keep reading and as business leaders claim that Robotic process automation (RPA) has made great strides in fulfilling its promise to the marketplace. RPA has positioned as a no-code end-user computing tool, owned, and operated by many business functions, that automates routine work tasks with quantifiable business results. Now, businesses have a digital workforce in the form of powerful new end-user computing tools positioned and priced attractively to operations and finance leaders. It has the power to reduce the dependency on traditional automation delivered by IT, improve productivity and accuracy, reduce operational risk, and enable redeployment of expensive human resources to tasks that add more value. But how far this claim is true or close to the reality need to be rechecked... We all know that RPA maturity model is designed across industry around two key components - the first one around RPA strategy or RPA operations and second is the levels of RPA Maturity that can be used

The Robotics Process Industry is known for introducing & adopting several terms in its journey so far like - AI, IA, CoE, CV, CNN, DL, ML, NLP, NLG, iOCR, POV, POC, RNN etc. One term that is quite high in the list is “Proof of Concept”, or POC. POCs are not special to Robotics Process Automation, but very unusual if the RPA project doesn’t start with a POC. In general, a proof of concept (POC) serves as a stimulant for those businesses looking to leverage the RPA technology to improvise their business process outcomes. A POC can be built for one entire process or a small part within the process. Now a days the most surprising thing is that every company that is planning to use RPA technology believes religiously that they must start the work with a POC so that they can ensure and can see themselves that BOT software is working before full blown deployment. To a large extent this is justified, given the exceedingly high failure rate of the RPA projects. But it is bit difficult to ac

A Center of Excellence (CoE) is essentially the way to embed RPA deeply and effectively into the organization, and to redistribute accumulated knowledge and resources across future deployments. This is actually a shiny penny term that is used heavily in the RPA world. But unfortunately, the CoE is yet another item of absolute dogma in the RPA world that, as defined and currently implemented, directly and significantly contributes to the ongoing failure of RPA initiatives. Nearly every organization selling and supporting RPA claims that CoEs are critical to success. A Center of Excellence is NOT critical to the success of an RPA initiative. It prevents the success of the initiative and is completely opposed to what has been the unified hue and cry of the RPA world for the last decade. How could it be that consultants, vendors, pundits and analysts all be wrong about having an RPA CoE? The following points lay out my case. CoE misconception: Excellence should be centralized   The most im

These Days if you look around the RPA led business world, you will find that nearly every business leader regardless from which experience background he is coming is attempting to implement BOT's and that as well without the help of IT but surprisingly with a very technology focused approach. There is a strong acknowledgment that BOT's are just a software, and they require few things like specifications, process maps, mockups, configurations, hardware, software, and the like.  But if you take a deep dive into the system, you will find that this is a big mistake. BOT’s are not a software; they’re a new workforce pool or workforce having strengths and weaknesses, abilities and constraints, values and needs, and they must be managed as such for them to be successful. This is even more relevant when BOT’s interact with human co-workers, which occurs often.  True enough, RPA is software and it’s typical to manage an RPA project like a technology project.  This sort of works keeps in

If you closely look at Robotics Process Automation and listen what people talk about “robotization of processes”. You will find that everybody agrees that RPA can be realized in any of the chosen operating model- centralized, decentralized or hybrid manner. And it is critical that there is a well-defined governance overseeing the development and operation of BOT's. This governance will provide assurance of the quality of that automation, minimizing risk and avoiding rework.  But if you go few steps back and relook at this Governance, you will find that we all talk very high about this governance, and surprisingly it is there in the system from decades but is one of the most undervalued modules of running an RPA business model. This is considered as unnecessary overhead cost. Someone said very rightly that this module is treated a bit like toilet paper in a public toilet; no one wants to pay for it but feels that it better be there when you need it. If you look closely at RPA; you w