Automation is the most seductive promise in the digital world: let the machines do the boring work for you. And in principle, it’s a legitimate promise. But in practice, most personal automations create more problems than they solve. Not because the technology fails, but because the wrong things get automated, in the wrong way, at the wrong time. In a minimalist system, automations should follow the same rules as tools: few, simple and with a clear purpose.
Automating With Judgement
The temptation is to automate everything. Have emails classify themselves, tasks create automatically, files move without intervention, notifications filter, data sync between twenty services. It’s technically possible — and it’s a trap.
Every automation is an invisible piece of your system. It runs silently, without you seeing it, without you remembering it. And when it fails — which it will — the failure is also silent. Emails stop being classified without warning. Tasks don’t get created when they should. Files move to the wrong place. And you don’t discover it until you search for something that isn’t where it should be.
The criterion for automating isn’t “can I do this?” but “should I do this?” And the answer is only yes when three conditions are met:
The task is genuinely repetitive. Not something you do once a month — something you do multiple times a day or a week with the exact same steps.
The task is predictable. The steps are always the same, with no exceptions or judgements requiring human discretion. If the automation needs increasingly complex “conditions” to cover edge cases, it’s too complex.
The cost of failure is low. If the automation fails, the result isn’t catastrophic. A misclassified email is corrected in seconds. A file that gets lost because the automation stopped working can be a disaster.
Automations Worth Building
In a minimalist system, the automations that deliver real value are few and simple:
Cross-device sync. What you capture on your phone appears on your computer without you doing anything. This isn’t a sophisticated automation — it’s a basic function of the tool you choose. But if it works well, it eliminates one of the most common sources of friction.
Automatic backup. Your information backs itself up without you having to remember. A cloud backup service configured once and forgotten. It doesn’t need to be complex — it just needs to be reliable.
Basic email filtering. Simple rules that classify the most repetitive emails: newsletters to one folder, automated notifications to another, everything else to the inbox. Three or four rules. Not thirty.
Quick capture. A shortcut that lets you add something to your capture inbox from any application with a single gesture. A configured share button, a keyboard shortcut, a widget. The goal is that capturing is so fast you never look for an alternative.
Review reminders. A recurring task in your task manager reminding you to do your weekly review, monthly clean-up, quarterly audit. You don’t automate the review — you automate the reminder to do it.
These automations have something in common: they’re simple, stable and fail obviously. If sync isn’t working, you notice immediately. If backup fails, you get an alert. There are no silent failures accumulating for weeks.
Automations Not Worth Building
The automations that generate more problems than they solve also share patterns:
Long chains. “When I receive an email from X, create a task in Y, add an event in Z, notify in W.” The more links in the chain, the more points of failure. And when an intermediate link breaks, everything downstream breaks without warning.
Complex conditional automations. “If the subject contains this word AND the sender is from this domain AND it has no attachments AND it’s not a reply…” Each additional condition makes the automation more fragile and harder to debug when something goes wrong.
Automating decisions. Automatically classifying an email as important or unimportant is delegating a decision that requires context. The machine doesn’t have your context. The result is erroneous classifications that make you lose things or waste time reviewing what the machine decided for you.
Automating what you’d do better manually. Moving a file to a folder takes three seconds. Creating an automation to do it for you takes thirty minutes — plus the maintenance, plus the debugging when it fails. If the manual task is quick and doesn’t bother you, don’t automate it.
Automating to impress. Creating a dashboard that connects six services and shows real-time metrics is technically impressive. But if you only look at it once a month, the time invested in building and maintaining it doesn’t justify itself. The most productive automation is the one nobody notices because it simply works.
Keeping Automations Simple
If you decide to automate something, these rules keep you on the right side:
Maximum five active automations. If you have more than five, you’re probably over-engineering your system. Each automation is an invisible piece to maintain — the fewer, the better.
Review quarterly. Every three months, review your automations. Are they still working? Are they still needed? Has any stopped being useful because something changed in your flow? Forgotten automations are the most dangerous.
If an automation breaks twice, delete it. One failure is an accident. Two failures are a pattern indicating the automation is too fragile to be useful. Better to do that thing manually than maintain something that needs constant repair.
Document what you automate. Note what automations you have active, what they do and how they work. When one fails in six months’ time and you don’t even remember it exists, that document will save you hours of confusion.
Automation used well is a productivity multiplier. Automation used badly is a source of invisible complexity, silent fragility and a false sense of control. In a minimalist system, the question isn’t how much you can automate but how much you should — and the answer, almost always, is less than you think.
