liveBook · Manning

Human-in-the-loop

As explained in The Art of AI Product Development

Human evaluation is the assessment of model outputs by people using qualitative or task-specific judgments.

A hiring recommendation may look convincing and still be wrong or biased. Human-in-the-loop (HITL) design gives a person a defined point to review, approve, modify, or support an AI outcome before it affects a consequential decision. The goal is not to keep a person busy; it is to place judgment where errors matter and automation is not yet reliable enough. section 11.4.3 section 9.5

Human involvement takes different forms. In product evaluation, people judge outputs against user needs that benchmarks may miss: tone, creativity, coherence, accuracy, and brand alignment. In a live workflow, they may check an uncertain result, supply missing information, express a preference, or approve an action. Human evaluation measures quality; HITL oversight also controls what the system is allowed to do. section 5.4.2 section 9.1.2 section 11.4.3

Design the handoff around the task and its risk:

  • Decide what can be assisted, augmented, or automated. Routine, high-confidence work may benefit from automation; decisions that depend on expertise or stakeholder preferences need more human judgment. section 3.3.2
  • Specify when to ask for help: low-confidence outputs, missing data, subjective preferences, complex requests, or actions whose errors could have severe consequences. section 9.1.2 section 5.2.1
  • Make the review actionable: show the proposed outcome and let the person approve or modify it. Record AI decisions and interventions so responsibility remains traceable. section 11.4.3
  • Check whether review still saves effort. If generated tables need full manual validation while drafts need only light editing, the draft may be the better first opportunity. section 10.1.1

A biased hiring recommendation

An HR manager reviews an AI-generated recommendation before it influences a hiring decision. Without that check, an overlooked biased recommendation could be accepted as a positive example for later fine-tuning, reinforcing the bias. Review is one safeguard alongside fresh data and alerts that flag shifts for investigation; the reviewer is not assumed to be free of bias either. section 11.3.3 section 11.3.4

Oversight need not have one fixed intensity. HITL requires approval before execution; human-on-the-loop lets a person monitor autonomous actions and intervene; human-out-of-the-loop removes direct intervention for suitable low-risk, high-frequency work. Choose among them by confidence, impact, and risk, then revisit the interface as reliability improves. For evaluation, a hybrid of human review and LLM-driven scoring can scale checks, but automated judges introduce their own biases and still need scrutiny. section 11.4.3 section 9.1.2 section 5.4.2

How The Art of AI Product Development covers it

How deep it goes
Defines approval-based oversight and gives review triggers, evaluation trade-offs, and risk-based alternatives without prescribing an implementation.
Examples
Uses hiring recommendations, customer-request escalation, product-prioritization preferences, and human ratings of tone and creativity.
What it assumes
Assumes familiarity with generative AI for agent workflows, while spelling out when agents should request human input.
What you can do after
Apply it via risk-based review gates, human escalation, and evaluation checks while accounting for oversight cost and accountability.
How it connects
Connects human evaluation, agentic AI, automation levels, feedback-loop bias, and AI governance.

Also explained in

Compare how 17 books explain human-in-the-loop →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Art of AI Product Development. The section links point to the parts of the book it draws on.