Few ideas in everyday business attract as many strong opinions as automating repetitive work. One camp insists that anything done twice should be scripted immediately. The other insists that real professionals do things by hand and that automation is for people who cannot be bothered. Both camps are repeating myths. Looking at how routine tasks actually behave over time, a more measured picture emerges, and it is one you can test in your own week without buying anything.
Below are six myths, each followed by what the evidence of ordinary working life suggests. The common thread is a sequence: do the task by hand a few times, watch what never changes, template or script that part, and keep a person on the decisions.
Myth 1: If you do something twice, automate it
It sounds efficient, but two repetitions rarely reveal the shape of a task. The second time you invoice a client, the first client’s quirks may still be fresh in your mind and you mistake them for the rule. Automating after two runs often bakes in assumptions that fall apart on the fifth.
A more reliable threshold is three to five manual runs, with notes. After that many repetitions you can usually name the steps that stayed identical. Those steps are the safe ones. Anything that varied every time deserves another few manual passes or should stay manual.
Myth 2: Automation always saves time
Automation saves time only when the time saved across all future runs exceeds the time spent building and maintaining it. A weekly task that takes ten minutes may not justify an afternoon of scripting, particularly if the inputs change often. Meanwhile a small template that takes twenty minutes to build and is used daily pays back fast.
The honest test is a rough sum. How often does the task occur, how long does it take now, how long would a template or script take to build, and how often will it need fixing? If the arithmetic is close, choose the simpler tool, which is often a checklist or a pre-filled document rather than code.
Myth 3: Automating a task means removing the person
The best routine automation removes typing, copying and remembering, not thinking. A reminder that tells you a supplier payment is due does not decide whether to pay it early. A template that pre-fills your standard reply does not decide whether the customer deserves an exception.
Business writers have often pointed out how small, repeated spending leaks and payment habits go unnoticed precisely because nobody looks at them each month. Standing reminders and tidy templates make the routine visible again, and that frees a person to ask the useful question: is this still the right thing to be doing at all?
Myth 4: You need special software to begin
Most first automations are embarrassingly low-tech. Think of a shared folder with a fixed naming pattern, a document with the headings already in place, a calendar entry that repeats, or a spreadsheet with the formulas locked. These are all legitimate forms of taking the repetitive step off your mind.
Software becomes worthwhile when the same low-tech routine has proven itself and the volume has grown. By then you also know exactly what you need from a tool, which makes choosing one far easier than shopping in advance. If you are still mapping what a business actually needs from its digital setup, a walkthrough of how to think about business technology solutions can help frame the questions.
Myth 5: Once it is automated, it is finished
An automated routine is a small piece of equipment, and equipment needs attention. Prices change, forms are redesigned, a supplier switches the format of an attachment, and the quiet routine starts producing wrong answers. The danger is that the output still looks tidy, so nobody notices.
A simple safeguard is to sample. Once a month, run one instance by hand and compare it with what the automated version produced. Put the sampling date in your calendar alongside the task itself. If the two disagree, the automation has earned a repair, not a defence.
Myth 6: Only technical businesses benefit
The routine chores of a clinic receptionist, a travel planner, a tutor or a market stall holder are just as repetitive as a developer’s. Answering the same five enquiry questions, sending the same document checklist, confirming the same appointment details: these are all template territory.
Even industries with very specific needs lean on structured requests. Take the medical tourism platform HipHospitals, which organises hospitals and doctors by country and lets international patients send free-quote and appointment requests through forms, shows how a repeated enquiry step can be turned into a consistent form while people on the other end handle the individual conversations. The takeaway for any small business is that consistent intake is not impersonal; it just makes sure the right details arrive the first time.
A practical way to test the myths yourself
None of this has to be accepted on faith, because a fortnight is long enough to test it with one ordinary chore.
- Choose one task you perform at least three times a week.
- For the first week, do it by hand and write down every step and how long it takes.
- Circle the steps that were identical every time.
- In the second week, replace only those steps with a template, checklist or reminder.
- Compare minutes spent, errors noticed and how you felt about the task.
If the numbers improve, keep the change and pick a second task. If they stay flat, nothing expensive was built, and you now know something concrete about how that chore behaves, including why it resisted tidying.
The pattern behind all six
Every one of them treats automation as a single switch: on or off, good or bad, everything or nothing. In practice it is a dial that you turn gradually. You start with attention, move to notes, then to templates, and sometimes to scripts, always keeping the person who understands the task close enough to notice when something looks off. That approach avoids both extremes: the endless manual chore and the premature machine nobody understands.
So the next time someone tells you that real professionals never automate, or that anything repeated should be scripted at once, you will have a calm answer. Do it by hand a few times, learn what never changes, take the repetitive part off your plate, then put the hours you recover into the decisions that really do need a thoughtful person.

