Would you like to implement RPA company-wide? People are crucial for that. The success of RPA requires interdisciplinary teams. At the same time, the range of RPA specialists on offer is still manageable. So which roles and competences do you really need? We have compiled the most important RPA roles for you.

For a successful rollout, you need different competencies and expertise. Especially, of course, specialists for the development and operation of RPA. But do remember to involve everyone else in your organization, too, when it comes to automation: This includes topics such as internal communication and mobilization, change management, and training. The goal is not only the success of an individual project, but also the successful transition to an automated organization.

6 “Central Roles” for RPA

  1. The Business Sponsor – a Strategic Key Role
    To be able to implement RPA on a company-wide scale, you need the appropriate “management buy-in”. This is best done by a C-level person who is responsible for digitalization/automation and establishes it as a strategic priority. The business sponsor is also an overarching, strategic communicator for automation. In practice, it has been shown time and again how crucial this role is for success.
     
  2. The Business Analyst – Combining Process and RPA Knowledge
    This person has to understand the process, business, and technical requirements in detail. Together with the subject matter expert on the business side, they model the processes in detail and optimize them if necessary. The business analyst evaluates whether processes are suitable for automation and plans the automation in detail.
     
  3. RPA Developer – the RPA Techie
    This person is responsible for the development and implementation of process automation. This includes the design and testing of automation processes as well as support for the implementation of the RPA solution. Even though RPA products can often be operated without extensive programming knowledge, you should always have someone with an in-depth knowledge of RPA technology in your team.
     
  4. RPA Solution Architect – the Complete Solution Visionary
    You need a solution architect who thinks in larger contexts – the RPA solution architect. They are the one who define the architecture of the RPA solution, provide holistic support, and accompany the individual projects both during development and implementation phases. They select the appropriate technological tools and features and ensure that the solution meets the applicable security and compliance requirements.
     
  5. RPA Infrastructure Manager – Your Infrastructure Specialist
    This person is responsible for all IT infrastructure and network issues as well as server installations. On the one hand, they work together with the RPA solution architect on the RPA solution architecture and implementation (with a focus on IT infrastructure issues). On the other hand, they also act as a technical support for these topics in the event of corresponding incidents.
     
  6. RPA Admin & Support – the Technical First-Aid
    The RPA administrator is responsible as soon as the process execution is running. This includes monitoring, altering, and maintenance of the RPA technology and bot landscape. Clarify who is responsible for the operation/support of the infrastructure and servers. Either the RPA admin, too, or the infrastructure engineer or another RPA admin/technical support.
     

Other Roles: Communication, Training, Project Management & Business Experts

  1. Communication & Change Manager – the Central Communicator
    This role is responsible for project communication and management of the change process. The goal is to mobilize the affected employees and quickly build acceptance for RPA. This person informs and communicates company-wide about RPA and paves the way for the organization’s “automation journey”. The central task is, for example, content development for internal communication channels, especially for success stories.
     
  2. RPA Trainer – the Automation Fitness Trainer
    Your RPA trainer is responsible for the topic training & education. A lot of RPA providers also have a consulting team to accompany the kick-off of RPA projects. Your RPA trainer is an important internal ambassador for RPA. In addition to technical aspects, they should definitely talk to the communications manager in order to use the training phase for active communication as well.
     
  3. Project Manager – the Project Conductor
    It is worthwhile to have a project manager who manages the RPA projects with the business departments to ensure the project’s success “in time and budget”. You can fill this role on the business side too, it doesn’t have to be part of the RPA core team. Some organizations have competence centers for project management. In such cases, you should enquire here.
     
  4. Subject Matter Expert – the Business or Process Expert
    This is a common term for a person who is an expert on a specific topic or area and who you need for the project in question. This could be the technical or process expert of a department.
     
  5. Citizen Developer – RPA Implementer on the Business Side
    The citizen developer is a term coined by Gartner. It describes a business user who actively automates processes but has no programming knowledge at all. This makes them a team member in a business unit that implements automation on a project-by-project basis. If necessary, this can be the subject matter expert.
     

Which other roles – and how many – you need depends, of course, on the size of your organization, the scope of your RPA projects, and your goals. Think about which competencies and experts you already have “in-house” and whether you can inspire and acquire them for RPA. Some roles can be merges or responsibilities shifted, depending on your requirements and your internal structure.

in-5-steps-to-the-rpa-center-of-excellence

In this e-book, we present a framework for the successful and structured planning of a Center of Excellence. In just five steps, you can plan your CoE or even just your RPA implementation.