Most automation projects don't fail because the technology can't do the work. They fail because the project never survives contact with the operation that has to run it.
Why does automation fail in production?
Automation fails in production because it was built for the work as described, not the work as run. A strategy deck describes the work as it's supposed to happen. The desk is where it actually happens, with the exceptions, the workarounds, and the tribal knowledge that never made the slide. Automation built for the deck breaks on the desk.
Why does automation need a Study phase first?
Studying first is what keeps automation from breaking on the exceptions nobody documented. The first phase of STAR is Study for a reason. You trace the real flow, name the leak points, and find the exceptions before you automate around them. Skip it and you automate the happy path while the operation lives in the edge cases.
Why keep an operator in the loop?
Durable automation keeps a human on the decisions that need judgment, so the system stays reliable when reality drifts from the training data. The system handles volume; the operator handles ambiguity. That division is what survives a Monday morning the model never saw in training.
Why does automation need ongoing refinement?
Automation needs refinement because the work it models keeps changing, and an untuned system decays. An automation that doesn't get tuned every operating cycle drifts out of fit. The last phase of STAR, Refine, is what turns a launch into a system that compounds.