Optimise Before You Automate

Optimise before you automate because automation amplifies whatever design it is given. Simplify the flow, controls, data and exception handling first, then automate. The principle works best applied together with other guiding principles rather than as a slogan used in isolation.

• Remove unnecessary steps. In the article's example, a team removes a duplicate approval before automating fulfilment, avoiding a faster version of the same delay.
• Standardise inputs and decisions, documenting decision rights and escalation paths where several functions or suppliers contribute.
• Design exception routes before automating, and keep that information concise with an owner to maintain it.
• Automate with outcome monitoring. Measure manual effort removed, automation exception rate and end-to-end lead time as a set, and after the first cycle ask whether lead time moved for the intended reason and whether any group experienced a worse result.
• Avoid automating waste, hiding poor data behind integration, and measuring bot activity instead of service outcomes. Make assumptions explicit, identify early warning signals, give someone authority to intervene, and review results with both delivery teams and affected consumers.