In the last article What is Robotics and how does it work? we briefly described what Robotics (or RPA – Robotics Process Automation) is and how it works. In short, a software which behaves like a robot takes over the operation of other programs so that users do not have to be robots themselves.
We at WorkAnizer are naturally very positive and open to the use of robotics. But are all users so enthusiastic about robotics?
In our experience, there is a lot of scepticism and concern from employees when robotics is first discussed. It usually expresses itself in various ways, as we know it from change management processes. Above all, one notices skepticism rather than direct resistance or a negative attitude. Statements like:
„We certainly don´t need that“
„Our processes are running well anyway“
„We have a lot of customized applications, that will not work“
„I can´t thing of any use case“
„We do not have repetitive tasks that often“
„What we know a software will never be capable of“
This list is certainly not complete, but in most cases such scepticism is based on one problem. Users don’t know how robotics work and often they lack the imagination of what robotics can do. This fear can be minimized by showing videos about sample applications or general information videos as they can be found on various video platforms. Since this does not always resolve scepticism, it may also be a good idea to implement a small use case in the sense of a mini pilot project.
How do you notice the scepticism if it is not addressed directly?
When you are dealing with robotics and you have identified initial potential for automation, it is often difficult to find promising and suitable processes. On the one hand, this is due to the fact that there is little or no experience available and thus there is uncertainty as to which processes per se could be suitable for robotics. On the other hand, it can also be an indication that passive resistance is being encountered. This may be due to a lack of imagination or to an inner attitude towards the topic. Who would potentially want to be replaced by a robot?
It is important to address the resistance here and tell the employees what you and they themselves would like to do with the time gained. For example, which activities can be done instead of tedious copy and paste tasks, such as customer contacts, telephone calls, project work or other higher value activities. A pilot project can also help here, because nobody likes to do robotic activities on the computer.
What happens in such a pilot project?
In a pilot project a software is installed, a (simple) process is implemented directly and can be viewed live. Everyone can then see how their own software is being operated, most likely even on their own computer, and what the final result of robotics will be. It is an impressive experience when you have implemented a process with Robotics and then just press “Play” and a computer is operated fully automatically. If you also sit back and watch others doing their stupid routine tasks automatically, you will see the “wow” effect in the eyes of the audience and the initial skepticism will be gone. After that, in our experience, you will no longer need to look for further tasks and processes for automation. These will then be applied by your employees themselves. Together, you and your employees will take a huge step forward on the way to a more efficient and effective working environment!
As always, if you have general questions about robotics, its implementation, integration into your IT-landscape, or how to deal with overt and covert resistance when introducing robotics, please contact firstname.lastname@example.org and we will be happy to help.
We will also be happy to support you in the implementation of a pilot project, the selection of suitable software, or assist you in selecting suitable process candidates for automation.
Your WorkAnizer Team