When Not to Automate
Recognise the tasks where automation costs more than it saves or puts people at risk
A taste of a lesson
Our monthly board pack takes me three hours to compile. Should I spend a week automating it?
Let us estimate. Three hours a month is about 36 hours a year. A week of building is roughly 40 hours, plus maintenance when a source changes and time checking each pack. So it might take more than a year to break even, and only if nothing changes. Before automating, ask whether parts can be removed or simplified, or whether a template would cut the three hours in half. Partial automation of just the data pulls might be the sweet spot. Which part of the three hours is pure copying?
Written by the teacher as an example. In your lesson the tutor answers your own questions, and like any AI it can be wrong.
What you will be able to do
- Estimate real time saved after build, maintenance and review costs
- Weigh error costs, process stability and human judgment before automating
- Choose alternatives such as checklists, templates or partial automation
- Explain a decision not to automate with clear, respectful reasons
Lesson plan
- 1 The full cost of an automation Estimate the true cost, including maintenance and review, not just build time. Start
- 2 Stability, errors and scale Recognise processes too unstable or risky to automate yet. Start
- 3 Judgment, people and dignity Identify tasks where human judgment and relationships are the point. Start
- 4 Better alternatives Choose simpler fixes that solve the real problem. Start
- 5 Making and explaining the call Decide clearly and communicate the decision well. Start
Try asking
About this tutor
For anyone tempted to automate everything: managers, freelancers, operations staff and builders. Automation has costs that are easy to overlook: building time, maintenance when tools change, errors at scale, lost judgment and worse experiences for customers or staff. This free tutor teaches a clear way to decide: estimate the real time saved, the cost of mistakes, how often the process changes and who is affected. You will study cases where the right answer was a checklist, a template or a better process instead, and learn to say no to automation with good reasons.
Reviews
4.7
3 ratingsSample
- Malik J.Sample
A good counterweight to all the automation enthusiasm. The maintenance cost point is something I now raise in every planning meeting.
- Ingeborg S.Sample
Saved me from a pointless project. A checklist and a better template did the job for our onboarding paperwork.
- Chiara V.Sample
The lesson on decisions about people was handled with real care. Free and worth more than some paid courses I tried.
About the teacher
I teach freelancers and small shops to automate repetitive work without writing code, and to know when not to
9 tutors 469 lessons taught Sample
I teach automation for people who run small operations: freelancers, shop owners, office managers and solo consultants. Before I taught, I ran the admin side of a small business, so I know the feeling of copying the same order details into three places every evening. My lessons begin with pen and paper. We map how the work really happens before...
See Isabela's profile and tutorsMore like this
Other tutors on the same or nearby topics.