Chapters · 4 of 8
- 01 · Choose the Level of Automation
- 02 · Respect Permissions, Consent, and Ownership
- 03 · Preview Before Changing Important Data
- 04 · Decide Where People Approve
- 05 · Add Volume, Spend, and Time Limits
- 06 · Plan for Stop, Undo, and Recovery
- 07 · Test Unsafe Requests
- 08 · Capstone: Approve a Safe Automation Plan
About 14 min · Lesson and activity
Chapter 4 of 80 complete
Decide Where People Approve
Approve the few things worth approving, and use forbidden states for everything else.
3b · decide where people approve
Decide which changes need human approval
Start with the example, then try it yourself. The last case is optional practice.
See the situation
Start with the situation below. Next, we will work through an example together before you try the activity.
The case
An approval queue, three months in
Approval can authorize an action or separate duties. It does not automatically override a forbidden state.
- Items approved
- Effectively all of them
- Median time on an item
- Under two seconds
- What the approver checks
- The same fields the system checked
- Information the approver holds that the system does not
- None
- What it is now
- A delay, with a story about oversight attached
Your place saves as you go.
Chapter 4 of 80 complete