Module 03 — Automation without chaos
Do it by hand first
You'll pick one task that repeats every week, run it by hand for five days with a written process card, and find out whether it's ready to automate.
The problem
Automation copies whatever process you give it — including the gaps. Automate a messy follow-up and you get messy follow-ups, faster, sent to more people, with nobody watching.
Why it matters
Most broken automations in small businesses share a story: someone automated a process that only existed in their head. A week by hand shows you the exceptions, the missing information and the steps nobody wrote down — while they're still cheap to fix.
1 The method: run, write, decide
- Run itDo the task by hand, the same way every time, for one working week.
- Write itTrigger, steps, owner, and what “done” looks like — on one card.
- DecideAutomate only the steps that stayed the same all week.
2 Step by step
-
Pick one task that repeats at least five times a week
Good first candidates: the first reply to a new inquiry, a follow-up after a quote, a reminder the day before an appointment. Pick the one tied to the leak you measured in lesson 1.3.
-
Write the process card before you start
Use the template below. If you can't fill in the trigger or “done when”, that's your first finding — the task isn't defined yet.
-
Run it by hand for five working days
Follow the card exactly. Every time reality doesn't match it, write a line in the exceptions log: what happened and what you did.
-
Count the exceptions
If most runs were identical, the task is stable. If more than one run in five needed a judgment call, fix the process first — add a rule, a missing fact or an owner — and run it for another week.
-
Mark each step: machine or person
Sending the same message at the same moment is a machine step. Deciding on a discount is a person step. Lesson 3.2 turns the machine steps into an automation.
Example · illustrative
The day-before reminder
The cleaning company sent reminders by hand for a week: 14 bookings. Eleven reminders were identical. Three weren't: one customer had a new gate code, and two bookings were made the same day, so a “see you tomorrow” message made no sense.
What changed on the card: two new rules — “skip if booked less than 24 hours ahead” and “ask for access details in the reminder.” Automated a week earlier, it would have sent confusing messages and still missed the gate code.
Your exercise · about 20 minutes
Write your first process card
TASK: TRIGGER (what starts it): OWNER (one name): STEPS: 1. 2. 3. DONE WHEN (how you know it's finished): INFORMATION NEEDED (and where it comes from): EXCEPTIONS LOG (date · what happened · what I did): - - MACHINE OR PERSON (mark each step M or P):
Automate a process, never a habit.
Your next action
Write the process card today and run it by hand the next time the task comes up.
Saved in this browser only — nothing is sent to us.