Specify the operating boundary of an autonomous task.
About 45 minutes, including the exercise.
Learning objectives
Specify the operating boundary of an autonomous task.
Distinguish a meaningful intervention from ceremonial approval.
Companion reading in Better Answers, Worse Decisions: Chapter 4. The book is for separate purchase. This course does not provide the manuscript or chapter downloads.
The lesson
Delegate a defined decision, not a vague capability
“Use AI in the department” is not a decision boundary. Specify the input, permissible output, affected population and conditions in which the system must decline or escalate. A tool suited to a narrow routine decision may be unsuitable for an irreversible judgement with ambiguous evidence. The same model can occupy different roles in different workflows.
Identify the realistic alternative and the consequence of delay. Requiring an expert to approve every trivial decision can consume scarce expertise without improving outcomes. In other settings, removing independent judgement can eliminate the only path by which a consequential error is detected. The useful question is which arrangement improves service while preserving a proportionate route to correction.
Separate a veto from a signature
A person is not an effective safeguard merely because a screen asks for approval. Can that person inspect the grounds, obtain contrary evidence, decline the recommendation and bear the time cost of doing so? Does the organisation permit disagreement without treating it as a performance failure? These are operational questions about authority and resources.
Use an escalation rule with a destination and a response time. “Refer difficult cases” is incomplete if no competent recipient is available or if the original decision takes effect before review. A review pathway may also be inaccessible to the person affected. Include the practical cost of invoking it, not just its existence in a policy document.
Test the boundary
Before expanding a deployment, test cases near its limits: missing data, contradictory evidence, unfamiliar populations and a failed upstream service. A refusal or escalation can be the correct output. Do not count every abstention as a system defect while simultaneously claiming the benefits of a bounded operating domain.
Write down who may change the boundary. A quiet change in a threshold, input field or default can expand the consequences of a system without changing its brand name. Version the decision rule and the operating conditions. Review the deployment when the environment changes, not only when a calendar reminder arrives.
Invented for this course
Automatic reimbursement
A fictional organisation considers automatically approving small expense claims. Routine claims have a valid receipt, an approved category and an amount below a fixed limit. Exceptional claims include missing receipts and disputed business purpose.
Define the routine boundary using observable fields and preserve a route for correcting rejected or misclassified claims.
Escalate disputed purpose rather than pretending that a text classifier resolves the underlying policy question.
Test duplicate receipts, changed tax treatment and unavailable records. Assign authority to suspend automated approval when those tests fail.
What follows: Automation can be appropriate for the bounded routine while exceptional judgement remains a separate, staffed process.
Attempt before opening feedback
Write a delegation charter
For a fictional service, write permitted decisions, exclusions, escalation triggers, response times and the authority to suspend the system. Include one reason not to require human approval on every case.
Review criteria
The boundary can be tested against actual inputs.
Escalation has a competent destination and a time limit.
The plan compares the costs of intervention and non-intervention.
Worked feedback
A charter should say what happens when the designated reviewer is absent. It should also distinguish a pause of the automated process from a pause of the whole service: a manual or limited fallback may preserve access. No universal threshold is correct without the service’s evidence and consequences.
Formative practice
Check your reasoning
This is an open self-check, not a secure examination or certificate. Answers and explanations are available below. Nothing you enter is sent to a server.
Keep your working notes
These notes remain only in this tab. They are not submitted or saved automatically. Download a copy before leaving. Use fictional or public information, not confidential personal or client details.