Where automating makes it worse
When automation makes operations worse, not better.
These are not edge cases. They account for a large share of the automation projects that get quietly turned off within six months of launch.
Situation 1
When the relationship is the product
Some follow-up exists not to move a process forward but to maintain a relationship. A check-in that says "I am thinking about you and your situation" is a different kind of message from "your trial expires in three days." Automating the first produces a message that technically arrives on schedule but communicates the opposite of the intended meaning: that nobody is actually thinking about this person.
The test: does the value of this follow-up depend on the recipient believing a human sent it for human reasons? If yes, the automation fails even when it works correctly.
Situation 2
When exceptions outnumber the standard case
Automation works well when the standard case happens most of the time and exceptions are well-defined and handleable. It works poorly when every third record has something unusual about it that the automation does not know how to handle, a paused relationship, a special arrangement, a sensitivity the system cannot detect.
When the exception rate is high, the cost of managing exceptions often exceeds the value of automating the standard case. The automation saves time on 60 percent of records and creates cleanup work on 40 percent. That is not a good trade.
Situation 3
When the underlying process is broken
Automating a broken process produces broken outcomes faster and at scale. A follow-up sequence built on a CRM with inaccurate data sends the wrong messages to the wrong people at the wrong time, reliably. A reporting automation built on inconsistent source data produces inconsistent reports automatically, every week, without anyone making the error manually.
Fix the process before automating it. Automation is a force multiplier. It multiplies problems as readily as it multiplies efficiency.
Situation 4
When accountability needs to stay human
Some actions should not be automated not because the rule is unclear but because the accountability for the outcome needs to belong to a specific person. A payment collection message. A decision to close an account. A communication during a difficult client situation. These may follow a pattern, but the person who sends them should be aware they are sending them and own the consequence if something goes wrong.
Automation removes awareness. In situations where awareness and accountability are part of what makes the action appropriate, removing them changes the nature of the action, not just the delivery mechanism.
