RPA Project – Week 1 – What To Do
RPA is different in many ways.
- It has a fast impact on the business.
- The cost is relatively low.
- The payback can be very quick.
So, I am amused when it takes weeks to engage consultants, more weeks to get real traction in the project, and even longer to get the proof of concept up and running.
Here is what Week 1 should look like:
There are two potential scenarios here. Either you have executive sponsorship already or you don’t.
Even if you don’t have the C-level driving this forward, you have to act as if you do. While that means you may feel that you are going rogue, who is ever going to criticise you for leading the organisation into RPA?
When I say “act as if you do”, you need a bit more tact and subtlety than if you have top-down sponsorship, but the objectives are exactly the same:
- Build and grow knowledge across the organisation about the opportunities proffered by RPA
- Build awareness that this is the start of the journey, an exciting journey
- Create a central team that will address and evaluate all the issues (the Centre of Digital Expertise – CODE)
- Identify functions and processes to start the journey with
Read the whole article here https://www.linkedin.com/pulse/rpa-project-week-1-what-do-edward-brooks