Discussion
Pegasystems Inc.
US
Last activity: 1 Mar 2021 13:44 EST
What comes after RPA? Rethinking Automation to support true Digital Transformation
A challenging post from Francis Carden (@cardf) that affirms the value of Robotic Process Automation (RPA) while arguing that "Thinking about RPA should always be accompanied by the question ‘What’s next?’ Or, put differently, every RPA investment should come with a strategy for eliminating it. Band-Aids work because they heal in a way that makes their future unnecessary. RPA that doesn’t work to make itself unnecessary is like a Band-Aid that prevents an open wound from healing."
What do you think? What do you think is the rightful place of RPA in a long-term digital transformation strategy?
Pegasystems Inc.
US
@TimothyHarfield I definitely would like feedback on this discussion. There is no one size fits all in the world but we have customers that fall into many or some of these categories
* building in end-of-life RPA bot strategies (replace the old process with low-code/case or with new API's)
* Using RPA to fulfill integration / mashup stop gaps whilst rolling out new a new CRM
* Evaluating the use case for RPA v LOW-CODE (automate OUTLOOK or use Pega Email bots to replace OUTLOOK!)
What have you seen?
Pegasystems Inc.
GB
Very interesting topic @cardf and agree with you completely and would extend the thought - there is an old proverb - "There is nothing more permanent than a temporary solution" - in IT I find this particularly true!
RPA has its challenges in DT/IA for well documented reasons and there are lots of other 'tactical' parts of a development that may make it in the release(s) - the key for me is to have a broader continuous improvement/development strategy at the enterprise level which is in itself a considered part of the pipeline methodology of a Pega CoE.
This process and group would then have the responsibility and accountability to work on the improvement of the process for all its 'tactical' parts, giving ownership to the problem.