Automate One Boring Task This Week: Your First AI Workflow

Find your one repeated chore

Don't try to automate your whole role in one ambitious weekend — that's how these projects die before they start. Look instead for one narrow task that is repetitive, mostly rule-based, and mostly text: sorting enquiry emails into categories, drafting the same kind of reply to the same kind of question, turning messy meeting notes into a clean summary, or cleaning up a list that arrives in a slightly different format every week.

The best first automation is small, boring, and unmistakably yours — something you personally do often enough to feel the tedium of it. If you do it every week and it follows a recognisable pattern, it's a strong candidate. If it's different every single time and needs real judgement, it's not ready for automation yet, and that's fine; there are plenty of other chores that are.

Write the task down in one plain sentence before you touch any tool at all: "every Monday I go through new enquiries and reply with our standard pricing info." That one sentence is doing more work than it looks like — it forces you to notice the actual shape of the task, which is exactly what you'll need for the next step.

Describe it like a recipe

Every workflow, no matter how sophisticated the tool behind it, is really just three things: a trigger (what starts it), a few steps (what happens in between), and an output (what you end up with). "When a new enquiry email arrives → pull out the name and the question → draft a friendly, on-brand reply → save it to my drafts folder for me to glance at and send." That's a complete workflow description, and it's barely two lines long.

AI and no-code tools follow recipes like this far better than they follow vague wishes such as "handle my inbox better," which means nothing concrete to a human assistant either, let alone a piece of software. Once you can say your chore out loud as trigger, steps, output, in plain everyday words, you're most of the way to actually automating it — the hard conceptual work is already done.

This is also the moment to decide what should never be fully automatic. If a step genuinely needs your judgement — deciding whether to offer a refund, say, or how to phrase something sensitive to an upset customer — keep that step as "flag for me to decide," not "decide automatically." A good workflow knows exactly where the human belongs in it, and drawing that line clearly up front saves you from ever having to explain an automated decision you didn't actually make yourself.

Most people skip this recipe step and go straight to a tool, which is exactly why so many first automation attempts fizzle out after a week. Writing the trigger-steps-output sentence down first means you can spot the gaps — what happens if there's no name in the email, what happens if the enquiry doesn't match any of your usual categories, what happens on a public holiday when the reply shouldn't promise a same-day response — before you've built anything, when fixing each gap costs you a sentence instead of a rebuild.

Wire it up with what you already have

You almost certainly have the tools you need already sitting open in another browser tab. Start with the simplest thing that actually works, rather than the most technically impressive thing you could theoretically build:

• A chat assistant as a drafting machine — paste the input, get a draft output, and keep the exact prompt that worked so you can reuse it tomorrow instead of re-explaining the task from scratch every time.
• A spreadsheet plus AI — clean, categorise, or summarise rows of data without needing to know a single formula, by describing in plain words what you want done to the data and letting AI write the formula or the summary for you.
• A no-code agent — connect your inbox or a web form so a draft reply is already waiting for you when you open your laptop, and your only remaining job is to glance at it, approve it, and hit send.

Measure the hour you got back

Time the task honestly, before and after you automate it — not a rough guess, an actual number, even if it's just a stopwatch on your phone for a week. When you can say with a straight face "this used to take ninety minutes every Monday, now it takes fifteen," you've genuinely proved the idea to yourself, and you've also earned yourself a concrete, specific line for your CV and your next performance review.

One rule matters more than any of the others: keep a human in the loop on anything that reaches a customer or a client directly. Let AI draft the reply; you decide whether it actually goes out. Automate the typing, never the judgement — that distinction is exactly the part of your job that stays valuable no matter how good the tools around you get.

Once this first workflow is running quietly in the background, resist the temptation to immediately automate five more things at once. Let it run for a couple of weeks, notice what breaks or what you'd tweak, and only then move on to the next boring chore on your list. Automation that's rushed tends to create new small messes faster than it clears old ones.

It's worth saying out loud to your manager or your team once this is working, rather than quietly running it in the background forever. Most workplaces reward the person who visibly improved a process far more than the person who just happened to have some spare hours — and if nobody knows the ninety-minute task now takes fifteen, nobody can give you credit for it, promote you for it, or learn the trick themselves and free up their own week too.