Chapter guide
Reviewers need evidence, time, skills, authority and an understanding of the consequences. Without these, clicking approve may be a formality. Count review workload and waiting time when planning the pilot.
Design rejection, correction, takeover, appeal and recovery alongside the normal workflow. Show uncertainty and let users reject unsuitable advice.
Design with the people who will use the system, then observe them. Defaults and automation bias may encourage approval without checking. Verify that rejecting a recommendation actually stops the external action.
Discussion question
When a user clicks reject, do subsequent actions actually stop?
Related exercise
Follow the related lesson below and try its exercise. Use the linked template to record your judgment, evidence and open questions, then revise with the checklist. With a partner, check which parts of each other’s work need clarification.