Small, Safe Automations
Teach a team to ship one small automation with a written guide and a plan to undo it.
Objective
By the end of this lesson, you can teach a team to write an SOP and a rollback plan for one small automation.
Small beats big
Teams often want one big system that does everything. Big systems take months, break in confusing ways, and depend on one person who understands them.
Teach the opposite: micro-automations. A micro-automation does one small job, like sending a reminder or adding a row to a spreadsheet. It is easy to test, easy to explain, and easy to turn off.
Every automation ships with two documents
The SOP
An SOP (standard operating procedure) is a short written guide that says how something works. For an automation, it answers:
- What starts it? This is called the trigger.
- What does it do? These are the actions.
- Who owns it?
- How do we know it is working?
The rollback plan
A rollback plan says how to turn the automation off and go back to the old way. If an automation sends wrong messages at 2 a.m., someone must know how to stop it fast.
Example: a reminder automation
Here is a sample SOP written as plain steps. It is not code to run. It is how you would describe the automation to a team.
Name: Session reminder text
Owner: Program coordinator
Trigger: 24 hours before each Saturday session
Action: Send a text to enrolled adults who opted in to texts
Message: "Reminder: tutoring is tomorrow at 10. Reply STOP to opt out."
Check: Coordinator reviews the send log every Monday
Rollback: Pause the automation in the tool. Send reminders by hand from the saved template.
Never: Text minors directly. Text only parents or guardians who opted in.
Draft an SOP with AI assist
Use the Prompt Lab to draft an SOP for one automation from your "automate" bucket. Use made-up names and no private data. Then check every line yourself.
Prompt Lab
Draft a one-page SOP and rollback plan for one small automation.
Your prompt
Act as an operations lead who writes short, clear SOPs for small teams.
How to teach shipping
Use the real task method from Module 1. Each person:
- Picks one task from the "automate" bucket.
- Writes the SOP and rollback plan first.
- Builds the automation in a free tool the team already has, with test data only.
- Runs it for one week while still checking by hand.
- Reports at the weekly review: keep, fix, or turn off.
Judgment: when to turn it off
A good automation can go bad. Teach the team to turn it off when:
- It sends wrong or confusing messages, even once to a real person.
- Nobody owns it anymore.
- It touches data it should not, such as information about minors.
- The old way was faster once you count the time spent fixing it.
Turning off an automation is not failure. Keeping a broken one running is.
Before you turn on an automation
0 of 6 doneGo deeper: Staff Training: AI Automation for GTM, From Playbooks to Production in 8 Weeks
Discussion
Ask. Answer. Build together.
Loading…