A key success factor, in addition to openly addressing the concerns and fears of employees, is transparency. This requires both the before mentioned communication (see„Help, the robot is coming!“) and effective reporting of robotics itself.
Why is robotics reporting useful?
You have already held talks, possibly already implemented and presented your own small pilot projects and the first robotics applications have already gone live. It is in the nature of things that an automated solution geared towards efficiency is increasingly taking a back seat. On the one hand, this is certainly desirable, but on the other hand it also hinders the efficient and effective use of robotics in your company. Robotics will make the work of your employees transparent and efficient that it will become a matter of course.
In this case, however, you are giving away valuable potential of robotics in your company. Robotics reporting is a way to keep the topic present, identify further potential processes for robotics and monitor and optimize the efficiency of the robotics process already in operation. In addition, ongoing reporting offers the opportunity to do project marketing for all robotics projects.
How you communicate the robotics reporting in your company strongly depends on your current practices. It is less important whether you only discuss the results in a team meeting, include them in your periodic reporting or set up a separate intranet site for robotics. There are many possibilities – choose the one that suits your organization and your corporate culture.
The crucial point is that the robotics reporting is updated and visualized at regular intervals. Ideally, all employees should be able to see the status and progress of the automated processes in your company, even if they are not directly affected by these processes. Being able to suggest additional processes for automation is another way to identify additional robotics processes.
What should be reported regularly?
The type of content can be divided into the following main areas
• Robotics pipeline
• Robotics development
• Robotics monitoring
The robotics pipeline should contain all future potentials regarding the implementation of robotics projects. It does not matter whether these have only been entered in the pipeline, already evaluated or already prioritized. This makes it clear which processes are to be implemented in which order. If other key figures are also collected (for example, in the course of the evaluation), further statements can be made, such as the time required for implementation. For a before-and-after comparison, it is advisable to at least record the current process duration of the respective process before automation. Robotics makes these processes more efficient and faster. It is not uncommon to find that a process that took one or more days before automation is finished in a few minutes after automation. Key figures such as error rates and the like also show the increase in process quality after conversion to robotics.
Robotics development contains key figures such as the duration of programming, the number of systems/software used per process, and the number of reworking in the sense of versioning. It is important to show the complexity and the underlying personnel deployment, since not every process is suitable for automation, or if so, then possibly only with very complex implementations. Communicating the limits of robotics (or those for an initial roll-out) not only increases the credibility of the entire program, but also makes it much easier to determine and communicate the ideal areas of application for automation.
Robotics monitoring answers questions such as, does the automated process run error-free, how many runs have already been performed, what is the cumulative runtime of the individual processes, what is the number of processes currently implemented and, above all, the utilization of existing services. In a sense, with a bot you have a virtual employee who is available 24/7, and based on his or her workload you can easily show further potential.
We hope to have given you ideas for the content of robotics reporting and how you can increase transparency. We would be happy to support you in the implementation of a pilot project, the selection of suitable software, accompany you in the selection of suitable process candidates for automation, and help you set up effective reporting.
As always, if you have general questions about robotics, its implementation, integration into your process landscape, or how to deal with open and hidden resistances when introducing robotics, please contact firstname.lastname@example.org and we are happy to help you.
Your WorkAnizer Team