liveBook · Manning

Chapter 2: Framing and scoping the evaluation

What you will learn in chapter 2 of Evaluating AI Systems

The introduction explains why an AI evaluation needs a shared purpose and scope before a team chooses how to measure it.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction explains why an AI evaluation needs a shared purpose and scope before a team chooses how to measure it.

Key terms: evaluation goals, metrics, benchmarks, toolkits, framing and scoping, success, tasks and scenarios, evaluation dimensions

2.1 One room, many expectations

A hospital chatbot scenario shows that stakeholders can agree an AI system needs evaluation while expecting the evaluation to serve different purposes.

Key terms: evaluation plan, adoption, unsafe advice, defensible evidence, diagnostic, performance degrades, single pass–fail answer, safe to deploy

2.2 Defining evaluation goals

This section explains why evaluation goals should be made explicit and prioritized before an evaluation is designed.

Key terms: evaluation goals, information need

2.2.1 Setting expectations

This section explains how evaluation can establish realistic, shared expectations about an AI system’s capabilities and limitations, and when that goal is especially useful.

Key terms: setting expectations, capabilities and limitations, stakeholders, first working prototype, key milestones, external stakeholders

2.2.2 Comparing

This section explains when to evaluate an AI system by comparing it with a reference point and why outperforming that reference does not establish suitability for use.

Key terms: reference point, human baseline, industry benchmark, performance target, functioning baseline, realistic alternatives, competitive positioning

2.2.3 Deciding go/no-go

This section explains how go/no-go evaluations use context-specific minimum requirements to make deployment or continuation decisions, and when those evaluations are most useful.

Key terms: go/no-go evaluation, minimum requirements, explicit thresholds, decision criteria, concrete decision points, initial deployment, potential regressions, early development stages

2.2.4 Assessing risk

This section explains why risk assessment goes beyond average performance, how to look for consequential failures, and when that evaluation matters most.

Key terms: assess risk, accuracy, effectiveness, risk-focused evaluation, vulnerabilities, high-risk scenarios, safety- and trust-critical contexts, before deployment, external audits

2.2.5 Ensuring compliance

This section explains how compliance evaluation produces evidence that an AI system meets applicable requirements, how that evidence is checked, and why it matters for trust.

Key terms: compliance evaluation, regulatory, legal, and organizational requirements, evidence, test cases, controls, verification procedures, formal audits, formal checkpoints, trust, accountability

2.2.6 Diagnosing and debugging

This section explains how evaluation helps diagnose AI system failures and why academic benchmark results alone may not establish real-world readiness.

Key terms: diagnosis, root causes, error distributions, data segments, logs, benchmark datasets, controlled experimental conditions, baselines, real-world use

2.2.7 Negotiating and prioritizing evaluation goals

This section explains why evaluation goals must be prioritized and shows how stakeholder concerns and deployment context shape those priorities.

Key terms: evaluation goals, prioritizing evaluation goals, risk assessment, go/no-go evaluation, compliance, diagnostic evaluation, deployment readiness

2.3 Determining the objects of the evaluation

The section uses a medical RAG chatbot to show that evaluation objects can range from the whole system to individual components, and that the right choice depends on the evaluation goal.

Key terms: retrieval-augmented generation (RAG), external knowledge source, language model, retrieved context, end-to-end-system, retrieval module, generation module, external knowledge, evaluation goal, object of evaluation

2.4 Defining the task to be evaluated

This section explains why an evaluation must specify the AI system’s exact task before deciding how to assess it.

Key terms: task definition, exact task, ill-defined, evaluation dimensions, metrics, risk assessment

2.4.1 Problems with AI task definitions

This section explains three ways unclear AI task definitions can undermine an evaluation: scope mismatch, equivalence mismatch, and vague criteria for success.

Key terms: intended task, system task, scope mismatch, equivalence mismatch, health education, medical triage, criteria of correctness and success, correct, incorrect, acceptable

2.4.2 Defining an AI task well

This section turns a vague AI task into an evaluable definition by clarifying its inputs, ground truth, boundaries, risk, and expected autonomy.

Key terms: inputs, outputs, allowed input, expected input, ground truth, intensional definition, extensional definition, out of scope, task exclusions, risk level

2.5 Choosing evaluation dimensions

This section explains what evaluation dimensions are, how they differ from metrics, and how to choose a focused set for a particular evaluation decision.

Key terms: evaluation dimensions, metrics, safety, accuracy, robustness, fairness, explainability, efficiency, societal impact, evaluation scope

2.6 References

This section lists references cited in the chapter on framing and scoping AI evaluation.

2.7 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 1: The importance of AI evaluation Chapter 3: Picking evaluation metrics →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.