Because they can’t go straight from A to B, because there are so many audited processes that are tightly coupled to A. So they replace A with B one step at a time, and keep A in sync with B using RPA. When the whole of A is replaced, you turn it off along with the RPA.
The problem comes when RPA stops being a short-term tactic, and starts being a long-term cottage industry. Unfortunately, RPA vendors have a vested interest in keeping A around as long as possible in order to maintain the necessity of their solution.
Well, they can’t because they usually don’t really try.
Most likely they have outsourced years ago and lost a lot of competency along the way.
They have invested heavily on in really crappy software and solving this with something like RPA seems to me like introducing a ginormous footgun/perpetual roadblock.
That RPA is not going anywhere soon... Or will it be replaced by the billion dollar, just a bit late, “phoenix project”? The ONE platform that promises speed and agility? That one? :)
The problem comes when RPA stops being a short-term tactic, and starts being a long-term cottage industry. Unfortunately, RPA vendors have a vested interest in keeping A around as long as possible in order to maintain the necessity of their solution.