3 ms·
At my work we are leaning heavily on RPA to automate away drudgery and ultimately reduce expendature. However it has been immensely frustrating, prone to errors
by afarviral 6y ago
At my work we are leaning heavily on RPA to automate away drudgery and ultimately reduce expendature. However it has been immensely frustrating, prone to errors and garnered endless suspicion. The experience has been that bots written by the service desk staff doing the job function better and are much more under our teams governance, which the official "automation" teams within our org are painful to deal with due to their lack of availability and not having first hand knowledge of the things being automated. I think the RPA approach requires dedicated people developing and monitoring the bots who have an active part in the process being automated. The difference in approach determines the result.
- tyingq 6y agoI've experienced the same. Centralized RPA teams tend to, for example, do web scraping when they could easily use an existing REST API. Because they either don't know it exists, or don't have that skill set. Similarly, seen things like using a email as a trigger, when the source application has configurable web hooks. Feels like there's an RPA culture of sorts to assume the things being automated only have human based interfaces.