Process automation
The ability to see repetitive work, assess whether it is worth automating and implement a simple solution that reduces manual work without increasing fragility.
Definition
BT360 v2.0.0The ability to see repetitive work, assess whether it is worth automating and implement a simple solution that reduces manual work without increasing fragility.
What is it made up of?
3 INDICATORS- 01Finding tasks for automation
- 02Choosing a solution and estimating effect
- 03Implementing and supporting automation
Behavior levels 0–5
MANAGER'S GOAL - 3| Lv. | Label | Descriptor |
|---|---|---|
| 0 | Absent | Does everything manually; does not see repetitive operations; automation seems a matter for IT; does not support such solutions. |
| 1 | Poorly developed | Notices routine but does not act; tries macros or templates without a system; automation breaks; does not count the effect. |
| 2 | Underdeveloped | Automates simple operations; picks the obvious tool; does not assess the cost of maintenance; the result is unstable. |
| 3 | Normally developed leader's goal | Finds tasks to automate; assesses effect and risk; implements a simple solution; documents it; keeps it running. |
| 4 | Highly developed | Builds a portfolio of automations; assesses economics and fragility; selects technologies; involves IT; teaches the team; scales. |
| 5 | Overdeveloped | Automation for automation's sake: complex schemes for simple tasks; maintenance eats the benefit; processes become fragile and opaque. |
How is it measured?
coating BSJT - BT360 situational test: provides a hypothesis about judgments in work situations and does not replace observation, 360 and interviews.
InQ provides a thinking style, but not an automation skill. The level is confirmed by the implemented solution and its effect.
Development Actions
5 CATEGORIESPractical task: find a process, assess the effect, propose a solution and the risks.
Course 'Automation without a programmer': scenarios, off-the-shelf builders, effect assessment, maintenance.
Automate one routine operation and measure the time saved over a month.
Review with IT or an operations leader: maintenance cost and risks.
Introduce an automation register in the team and the rule 'process first, tool second'.