Technology
How to spot what's worth automating and the tools to do it — text expansion, email rules, built-in OS shortcuts, and no-code connectors — without overcomplicating things.
The fantasy of automation is a machine that runs your whole life while you sip coffee. The reality is more modest and more useful: small, dull tasks you do over and over, handed off to your computer so you stop spending attention on them. You don't need to be a programmer, and you don't need to automate everything. You need to automate the right things.
I've built plenty of automations that saved me hours and a few that quietly broke and cost me more time than they ever saved. The difference came down to choosing the right candidates and starting small. This guide is about how to make those choices, and which tools to reach for first.
Not every repetitive task should be automated. The good candidates share three traits, and a task really needs all three to be worth the effort.
Renaming files into a consistent format, sorting incoming email, filling in the same form fields, or resizing a batch of images — these tick all three boxes. Writing a thoughtful reply to a client does not. Be honest about which is which, because automating a judgment task usually means producing fast, confident, wrong results.
The best automation candidate is something you find slightly tedious, do the same way every time, and could explain to a new hire in two sentences. If you'd have to say "well, it depends," leave it manual.
The easiest place to start, and the one I'd recommend to anyone, is text expansion. You define a short trigger — say @@addr — and the tool instantly types out your full address, or an email signature, or a paragraph you send constantly. It sounds trivial. It isn't. If you type the same things repeatedly, this saves more cumulative time than almost anything else, and it essentially never breaks.
Both major operating systems include basic text replacement in their settings, free of charge. Dedicated tools go further with placeholders, dates, and fill-in-the-blank fields, but the built-in version is plenty to start. Spend ten minutes adding your five most-typed snippets and you'll feel the benefit the same day.
The same spirit applies to templates generally: a reusable document skeleton, a saved email draft, a checklist you duplicate. It's not glamorous automation, but removing the "start from scratch" step is exactly the kind of small friction that quietly drains a workday.
The next tier is automation that's already sitting inside the apps you use, waiting to be switched on. The classic example is email filters.
Your email client can sort, label, archive, and forward messages automatically based on who sent them or what they contain. Newsletters skip the inbox and land in a "Read later" folder. Receipts get labeled and filed. Notifications from a particular service route straight to a folder you check on your own schedule. Twenty minutes setting up filters can keep your inbox calm indefinitely, and it pairs well with the broader goal of a distraction-free workspace.
The same pattern shows up everywhere once you look: calendar rules, photo album auto-sorting, banking alerts, document-folder rules. Before reaching for any external tool, check whether the app you're already in can do the job. It usually can, and built-in features are the most reliable kind because nothing extra can fall over.
When you want to chain several steps together, your operating system probably has a tool for it already. On Apple devices, Shortcuts lets you build sequences — visually, by dragging blocks — that can run a series of actions with one tap or on a schedule. macOS has Automator for similar file and app workflows. Windows has Power Automate and, for the more adventurous, scripting built in.
These are genuinely capable and cost nothing. A single Shortcut might resize and rename a folder of images, then move them where they belong. Another might, at a set time each evening, mute notifications and open your planning app. You assemble it once from premade building blocks, no coding required.
The learning curve is real but gentle. Start by copying an existing shortcut someone shares and tweaking it, rather than building from a blank canvas. Understanding the building blocks on a small example is far easier than designing a big workflow from nothing.
The top tier for most people is a class of services that connect different apps together — Zapier, Make, and similar tools. They work on a simple model: when something happens in app A (a trigger), do something in app B (an action). A new file in cloud storage gets logged to a spreadsheet. A form submission becomes a calendar event and a notification. A saved article gets sent to your notes.
These are powerful and bridge apps that otherwise wouldn't talk to each other. The trade-offs are worth knowing before you commit:
Reach for these when the simpler levels genuinely can't do the job — not as a first move.
Here's the caveat that separates automation that helps from automation that hurts. Every automation is a small machine you now have to maintain. Apps update, your needs change, an edge case appears that the rule never accounted for. A broken automation can be worse than no automation, because you've stopped paying attention to the task and trust it's handled.
So my rule is to automate the boring, predictable 80% of a task and leave the messy edge cases to a human — you. Don't try to handle every exception in code; you'll spend more time on the rare cases than you ever saved on the common ones. Start with one small automation, live with it for a week, and only build the next once the first has proven it actually saves time and doesn't quietly misbehave.
Done this way, automation isn't a grand project. It's a habit of noticing the dull, repeated things you do and gradually handing the right ones to your computer. The payoff isn't a self-running life. It's a steady trickle of reclaimed attention you can spend on the work that genuinely needs you.
Daniel is a writer and former IT consultant who has set up more laptops, backup routines, and password managers than he can count. He explains technology the way he wishes someone had explained it to him: plainly, with the trade-offs left in. He reviews every tool on his own devices before recommending it.
Keep reading
What two-factor authentication actually is, why SMS codes are the weakest option, and how passkeys are quietly replacing passwords altogether in 2026.
Daniel Okafor
Phishing runs on urgency and misplaced trust, not technical wizardry. Here are the concrete red flags to check, a quick checklist, and what to do if you clicked.
Daniel Okafor