Field notes / KLYRFOCUS

What not to automate in a production shop

Keep judgment, unstable processes, and irreversible actions under human control. A practical decision framework.

Get your free automation audit ↗

Which production tasks should stay with people?

Keep work with a person when the cost of a wrong decision is high, the inputs are ambiguous, the process changes frequently, or the work rarely repeats. Automation can still collect evidence and prepare a draft. The decision to release a machine file, settle a dispute, or commit money remains separate.

Is the process stable enough to encode?

If two experienced operators disagree about the correct result, first clarify the production rule. A model can imitate whichever example it sees last without resolving the disagreement. Write a product profile and an exception policy before automating a judgment that is currently undocumented.

Does the volume justify the upkeep?

Measure actual repetitions and hands-on time. Subtract review and exception work from any expected saving, then include maintenance and subscriptions. An occasional five-minute task with a fragile integration may be cheaper to leave alone. Removing the task entirely is often better than building a bot for it.

Which actions are too consequential for unattended release?

ActionUseful automationHuman boundary
Complex logo repairPrepare trace and geometry reportConfirm exact text and visual identity
Color-critical printCheck file profile and separationsApprove physical color expectations
Production writeStage checked files and instructionsRelease to the client’s live system
Quote or proposalCalculate and draft from approved ratesAccept scope, price, and timeline
Credit or refundMatch records and assemble evidenceAuthorize and execute money movement
Customer complaintSummarize history and classify issueDecide remedy and send response

What does a good refusal look like?

A useful audit says why the workflow is a poor candidate, identifies any small reversible improvement, and shows what would need to change before automation made sense. “Keep this manual” is a valid result. The free audit is not obliged to justify a build.

Written for KLYRFOCUS · Updated 2026-09-06 · Estimates are labeled; measured results require source records.

Start with one workflow

Show us where
the work gets stuck.

Get a written audit of what can be automated, what should stay manual, and the first useful step. No pitch deck required.

Get your free automation audit
Get your free automation audit