Connecting work rather than systems.
WHAT THIS MEANS
Using interfaces to remove manual steps from how work actually happens.
WHAT TO LOOK FOR
Data typed into two systems Reports assembled by hand Notifications sent manually Files moved between places
WHAT TO ESTABLISH BEFORE AUTOMATING
Whether the process is correct.
WHY
Automating a bad process makes it fail faster.
WHAT TO DO FIRST
Document the process as it is.
WHAT TO AUTOMATE FIRST
The step done most often, with the clearest rules.
WHAT TO AVOID AUTOMATING
Steps requiring judgement Steps that vary every time Anything where a wrong action is costly
WHAT TO BUILD IN
A record of what was done A way to review before acting, for anything significant A way to stop it
WHY THE REVIEW STEP
It builds confidence, and catches mistakes while they are cheap.
WHAT TO REMOVE LATER
The review, once the process has proven itself.
WHAT TO MEASURE
Time saved, and errors avoided.
WHY
It justifies the next automation.
WHAT TO WATCH FOR
Processes nobody understands because they are automated.
WHAT PREVENTS THAT
Documentation, and an owner.
WHAT TO REVIEW
Whether the automation still matches how the business works.
