When Not to Automate
Keep people in charge of decisions about people, and see what happens when automation goes wrong at scale.
What you will learn
By the end of this lesson, you can identify which steps in a workflow must stay with a person, and explain why.
Automation repeats mistakes fast
A person who makes a mistake makes it once. An automated workflow with a mistake makes it every time it runs, often without anyone noticing. Speed is the point of automation. It is also the risk.
A national example
Keep a person in the loop
Human in the loop means a person reviews or approves a step before it takes effect. Use it for:
- Decisions about people: who qualifies, who gets flagged, who gets removed.
- Messages that carry bad news: a denial, a warning, a missed payment.
- Anything involving a child's safety or records.
- Anything you cannot easily undo.
Automation can still help in these cases. It can gather the information and prepare a draft. A person makes the call.
Signs a task should stay human
| Sign | Example |
|---|---|
| It needs care or context | Calling a family whose student stopped coming |
| The rules have many exceptions | Waiving a requirement for a special situation |
| A wrong result causes real harm | Cutting off services |
| It builds trust | A thank-you call to a long-time volunteer |
Creative work is different
Admin work (reminders, data entry, reports) is often a good fit for automation. Creative and relationship work (writing to a donor, mentoring a student) usually is not. Automation can handle the setup so people have more time for the human part.
Go deeper: Automating Administrative Workflows vs. Creative Workflows
Quiz: Module 4 Quiz: Automated Workflows
Discussion
Ask. Answer. Build together.
Loading…