Notes / Workers
Approvals are the feature, not the friction
An AI worker that acts without checkpoints can create risk. The teams getting value design the oversight first.
By Rich Hill III. Published Jun 15, 2026. 6 min read.
The most dangerous version of an AI worker is not the one that fails loudly. It is the one that is allowed to act confidently in a workflow nobody has bounded. A message gets sent too early. A CRM field changes without context. A lead gets routed wrong. The output might look small, but the trust cost is real.
That is why approvals are not a tax on automation. They are the feature that makes automation usable. The point of a managed worker is not to remove judgment from the business. It is to put judgment in the right places so the repeatable work can move faster around it.
The wrong question
Teams often ask, how much can the AI do by itself? That question pushes the design toward autonomy before the workflow is ready for it. The better question is: where does a human decision actually change the outcome?
Once that is clear, the worker can act freely in low-risk areas and pause at the moments where context, taste, relationship, or money matter. That is not less advanced. It is more honest engineering.
Approval is product design
An approval step is not just a yes-or-no button. It is a product surface. It has to show the human what changed, why the worker recommends it, what risk is attached, and what will happen after approval. A vague approval screen is only a slower version of blind automation.
Show the proposed action in plain language. Expose the source or reasoning that led to the recommendation. Make edits faster than rejection and rework. Log what happened so future drift can be caught.
Key takeaways
- Approval steps are not friction when they protect judgment, trust, and customer relationships.
- A good approval surface explains the proposed action, reasoning, risk, and next step.
- Autonomy should expand after reliable behavior is observed in a narrow workflow.
- Approval data becomes a feedback loop for improving the worker.
Frequently asked questions
Does every AI worker need human approval?
Not for every action. The approval level should match the risk of the workflow, the quality of the inputs, and the cost of a mistake.
When can a worker act without approval?
When the action is low-risk, reversible, well-bounded, and monitored. Even then, the system should log activity and surface exceptions.
What makes an approval step effective?
It should be fast, clear, editable, and specific about what the worker is about to do and why.
Explore Workers