Before automating, first exploit (remove waste) then subordinate (ensure clean inputs) — automation amplifies everything it touches, including waste
Before automating any process, first exploit it (remove waste) and subordinate it (ensure clean inputs), because automation amplifies whatever it touches including waste and mistakes.
Why This Is a Rule
Goldratt's Theory of Constraints prescribes a sequence: Exploit (maximize output from the constraint as-is) → Subordinate (align everything else to feed the constraint cleanly) → Elevate (invest in increasing constraint capacity, including automation). Automating before exploiting and subordinating makes a wasteful process faster — you produce waste at higher speed. Automating before ensuring clean inputs makes an error-prone process produce errors at higher speed.
"Automation amplifies whatever it touches" is the key principle. A manual process with 20% waste, when automated, produces waste 10x faster. A manual process receiving dirty inputs, when automated, processes dirty inputs without the human judgment that previously caught and corrected them. The automation didn't create the waste or the dirty inputs — it amplified them by removing the human bottleneck that was coincidentally also a quality filter.
The exploit-then-subordinate-then-automate sequence ensures you're automating a clean, lean process: waste has been removed (exploit), inputs are reliable (subordinate), and now speed increases through automation without amplifying problems.
When This Fires
- Before automating any recurring process (Four-category automation triage: automate now / automate later / assist / keep manual — classify by judgment requirement and frequency's "automate now" category)
- When automation produces errors or waste faster than manual processing did
- When Automate the single highest-frequency manual data transfer first, verify for one week, then iterate — sequential automation prevents fragile webs's sequential automation needs the quality prerequisite
- Complements Four-category automation triage: automate now / automate later / assist / keep manual — classify by judgment requirement and frequency (automation triage) with the pre-automation quality sequence
Common Failure Mode
Automate-first: "This process is slow, let's automate it!" The process includes 3 unnecessary steps, receives inconsistent inputs, and has no error checking. The automation makes it 10x faster — producing 10x more unnecessary outputs from inconsistent inputs with no error checking. Speed increased; value didn't.
The Protocol
(1) Before automating, exploit: can any steps be eliminated? Simplified? Combined? Remove all waste from the process first. (2) Then subordinate: are the inputs to this process clean and consistent? If the process receives variable-quality inputs, standardize them before automating. (3) Then automate the lean, clean process. The automation now amplifies value rather than waste. (4) After automation, monitor for new problems: the speed increase may reveal issues that manual pacing previously masked (Sovereignty check before automation — if the automation produces wrong output, will you notice? Automate only when the answer is yes's sovereignty check). (5) This sequence takes longer than immediate automation but produces a system that works reliably rather than one that produces garbage at high speed.