So, where do I start?

Targeted Deployment of Process Automation

Successful use of robotic process automation depends on knowing why and where process automation is to be deployed.  To answer this you need consider what level of change you would like to implement, why and where.  The decision you make will fundamentally affect your strategic approach and expected outcomes.

RPA deployment target

  1. Process – will robotic process automation focus on a single or group of related processes, within one business function?
  2. Operational – will RPA be deployed across teams where data, systems and tasks require integration?
  3. Service – will process automation be deployed to address specific client service objectives or even to integrate with client processes?

Process, Operational, Service

For each target area, there will be differences in, amongst other things, the business case and approval route, the type and number of resources to implement and manage, process ownership and governance.

To help you decide, here are some of the contextual factors that will guide the way that a process automation project is run.

Typical Drivers
  • Uneven demand
  • Loss of skills
  • Release staff from mundane & repetitious task
  • Inefficient resource utilisation
  • New products
  • Enhanced management information and analytics
  • One-off business events
  • New products & services,
  • Straight through processing
  • Improved level of service, and a need for value-based pricing
Business Case
  • Specific
  • Direct benefits
  • Process effectiveness
  • Reduce or sustain headcount
  • Reduce re-work
  • Improve accuracy
  • Reduce overtime
  • Specific
  • Direct benefits
  • Indirect benefits such as improved cash flow, enhanced compliance, more capacity
  • Specific
  • Defined benefits
  • Indirect benefits such as improved customer satisfaction or higher client win rates
  • Local process owner
  • Corporate governance
  • Functional process owners
  • Corporate governance
  •  Functional process owners
  • Corporate governance
  • Stakeholders include customer facing & product development staff
  • Client governance
  • Data inputs
  • Standard outputs
  • Systems and cross-business processes
  • Redesign of processes & organisation structures
  • Client systems
  • Cross-industry processes
  • Straight through processing
  • Local, incorporated into existing roles
  • Process automation roles & responsibilities established
  • Continuous improvement & identification of further automation opportunities
  • Process automation roles & responsibilities established
  • Continuous improvement & identification of further automation opportunities

Whatever the intended deployment target, the project implementation steps from the Virtual Operations VOLT methodology will be the same but the time taken, the expected benefits, the stakeholders involved and the impact on service delivery will vary according to where on the target the automation will take place.

Within your overall automation strategy it’s important to ensure that each project is properly targeted so that the project has a defined scope, expectations are met, and the benefits can be measured and realised.

We hope this has given you some insight into the deployment decisions you need to consider when embarking on a robotic process automation project for the first time.  If you would like to learn more contact us on +44 2035 891 549.

thumbnail of rpa-champions-guide-v1

Wondering how to rate an RPA opportunity?
Take a look at Part 1 in our RPA Champions Kit.

C-Suite Guide - Part 1

Want to make the most of the automation ‘goldrush’?
Read our 10 point guide to success.