Human-in-the-Loop
Putting a person at the decision point — the only reliable safeguard for agents, and it fails quietly when the person becomes a rubber stamp.
When not to use it
- At high volume. Ninety approvals a day is a clicking exercise, not a review.
- When the reviewer can't tell good from bad. You've added cost and a false sense of safety.
- On reversible, low-stakes actions. Save the attention for the decisions that need it.
- As the whole safety argument. "There's a human in the loop" should start the conversation, not end it.
Reach for something else instead
- Capability restriction — don't grant the action. More reliable than reviewing it.
- Post-hoc sampling — audit a fraction, if actions are reversible.
- Automated verification — a test is a better check than a tired person.
- Escalation on genuine uncertainty — if you can calibrate it, which is the hard part.
Sources & further reading
- Parasuraman & Riley (1997), Humans and Automation: Use, Misuse, Disuse, Abuse — automation bias, from decades before anyone needed it for this.
- Bansal et al. (2021), Does the Whole Exceed its Parts? The Effect of AI Explanations on Complementary Team Performance — human-AI teams often underperform the AI alone.
- Amershi et al. (2019), Guidelines for Human-AI Interaction — the practical design guidance, and it's specific.
Primary sources, listed so you can check the claims on this page rather than take them on trust.
Where people go wrong
- Reviewing everything, so nothing is reviewed. Rare and informative beats frequent and reflexive.
- Showing "Approve?" without the information needed to decide. You've asked for a reflex.
- Making rejection harder than approval. You've built a yes machine.
- Assuming a human improves the system. Bansal et al.: teams often underperform the AI alone.
- Treating high reliability as reassuring. It's what makes the reviewer stop looking.