Before I ever automated an outbound campaign, I was automating a manufacturing line. The lessons transfer more directly than I expected.
Instrument before you automate
On the plant floor, you don't automate a process you haven't measured. You put sensors in, watch it run manually for a while, and only then decide what to control and what to leave alone. The same applies to outreach: you don't automate a campaign you haven't run manually first and watched for what actually gets replies.
Automate the repeatable part, not the judgment call
A controls system handles the repeatable, well-defined part of a process: a valve opening at a set threshold, a motor running at a set speed. The judgment calls (is this batch within spec, should we stop the line) still go to a person. Outreach pipelines work the same way: signal detection and copy generation can run continuously, but deciding which lane to double down on stays a human call.
Failure modes are still failure modes
A stuck sensor gives you false confidence the same way a broken tracking pixel gives you false confidence that emails are sending. Building an automated system means building the instrumentation to know when it's actually broken.
I've since written up the broader version of this: Everything I Build Is a Control Loop.
Yours Truly