← Assignments and work

Organisational assignment · Automation

Building automation as a shared capability

An automated process needs people who can assess, improve and take responsibility for it.

Role
Product ownership and enablement
Context
Company assignment
Focus
Processes, roles, training

Organising automation

From a need to accountable use

  1. Which need do we address?

    Clarified process, requirements and open questions

    People involved

    Business team and product owner

  2. What do we implement first?

    Prioritised backlog, scope and acceptance criteria

    People involved

    Responsible management, business team and delivery

  3. Does the result work for the business?

    Test cases, feedback and agreed corrections

    People involved

    Users, business owners and delivery

  4. Who takes responsibility for continued use?

    Responsibilities, documentation and training needs

    People involved

    Business owners and operations, supported by enablement

Centre of excellence and enablement

Templates, shared knowledge and training support decisions across several initiatives.

A schematic guide to an automation assignment. It explains roles and work outputs, rather than a particular client’s internal process.

The question

Individual automations are not enough when requirements, operation and knowledge depend on a few people. How does automation become a capability that stays within the company?

My work

In a company assignment, I combined product ownership with RPA training and building a centre of excellence. Requirements, implementation and enabling the team were part of the same task.

For your project

Embed automation within the team

I analyse workflows, prioritise automation opportunities and support delivery. Roles, acceptance, training and handover are part of the assignment, so the team can assess and continue future initiatives itself.

Discuss an assignment