| No, the pitch is: > automate things in a project/environment/client/process that otherwise would wait until heat death of universe to be automated Which is to say "things no one else cares about or thinks are important enohgh to spend time automating." RPA isn't for major corporate priorities. RPA is for that thing that takes up 25% of a 3-person team's week. Or 15% of every contact center agent's time. Neither of which are ever going to be prioritized. Or, to put it another way, RPA is the answer to "That has value, but it isn't important enough to spend software developers' time on." Which is why "but these people aren't software developers" or "but they didn't use git" or etc simplify to "If we had more software developers, this wouldn't be needed." Yes. But that's not true. Nor will likely ever be true. So it is needed. PS: And fundamentally, it's taking corporate computing back from the "ask IT for anything" to "do it yourself" hacker ethos. Computers exist to do work for you. When did we forget that? |