Image: (modified)
All the Way with RPA

All the Way with RPA

Coming soon - a multi-part paper on getting the most from your investment in RPA

Here's a peak!
Robotic Process Automation (RPA) is exciting technology that appears set to gain widespread use, as did other software solutions such as ERP, CRM, HRMS and more. As with those applications, some RPA projects have been disasters and there will be further failures as adoption continues.

But this does not have to be case, not if prospective adopters consider four (4) key questions:

1. Why build anything?
2. What is the right thing to build?
3. How do I build it right?
4. How do I use it right?

To answer the first question, organisations must employ rational decision-making and consider the full gamut of options – from better use of existing technology, through to total disruption of the existing metaprocess.

Building the “right thing” requires sound understanding of: the diversity of stakeholder groups (from users, through IT, to finance); their diversity of functional requirements; and, the range of capabilities they require.

Any piece of software requires some logic development (“coding”) and it is during this “build it” stage that things often go wrong – in terms, of cost, schedule and quality. Critical to “building it right” are: shifting from spending on finding and fixing problems to investing in preventing them; use of a development approach that is aligned with overall project goals; and, use of a broad set of methodologies to support the approach and avoid the “failure” of defects and their detrimental impact on project budget and schedule and solution quality.

Finally, “use it right” means more than operating the software. The whole organisation, the user team(s) in particular, will be affected by the new solution and this change must be very carefully managed to ensure all emergent opportunities are seized.