Every professional has a version of the same afternoon: copy a name out of an email, paste it into a spreadsheet, paste the spreadsheet row into a document, rename the document, upload it to a shared folder, then write a message telling someone it's there. None of it is hard. All of it is theft — small, recurring theft of the hours you were hired to spend on judgment, not clerical relay work.
The good news is that the five most common time sinks are also the five easiest to hand off to software, and none of them require writing code. Here's where to start, in the order of effort-to-payoff.
1. Email triage
If you begin the day by sorting what arrived overnight, you're doing a machine's job. Every major email client — Gmail, Outlook — supports rules that label, file, or forward messages based on sender, subject, or keywords. Spend twenty minutes building three rules: one that files notifications (receipts, alerts, newsletters) out of your inbox, one that flags messages from your manager or top clients, and one that auto-archives anything you've been cc'd on but not addressed in. That alone typically reclaims the first half hour of the day.
AI assistants inside email go further: Gmail's summaries and Outlook's Copilot will condense a long thread before you decide whether it deserves you. The rule of thumb: read summaries for context, read originals before you commit to anything.
2. Meeting notes
Nobody's actual job is transcription. Tools like Otter, Fireflies, or the recorders built into Zoom, Meet, and Teams will transcribe the call, extract action items, and email the summary to attendees. The setup takes ten minutes; the payoff is compounding, because searchable transcripts also end the "what did we decide three weeks ago?" archaeology.
Two cautions. First, always announce recording — in many places it's a legal requirement, everywhere it's basic respect. Second, review the extracted action items before they go out; transcription models still mishear names and numbers, and a confidently wrong summary travels fast.
3. Scheduling
The back-and-forth of finding a meeting time is the purest example of work that feels like work but produces nothing. A booking link (Calendly, Cal.com, or the scheduling pages built into Google and Microsoft calendars) ends it: you define your available windows once, and other people pick a slot. Add buffer times so calls can't stack back-to-back, and set a daily cap on meetings if focus time keeps evaporating.
If your role involves coordinating groups rather than one-on-ones, polls (When2meet, Doodle, or your calendar's built-in polling) beat reply-all threads every time.
4. The copy-paste bridge between apps
Most repetitive work is really the same move: something happened in app A, so something must be updated in app B. A form submission becomes a spreadsheet row. An invoice email becomes a bookkeeping entry. A new CRM deal becomes a Slack announcement. No-code connector tools — Zapier and Make are the best known — exist precisely for this bridge and need nothing more than an if-this-then-that recipe.
Start with exactly one bridge: the one you perform most often. Build it, watch it for a week, then add the next. The common failure mode is building ten fragile recipes in a burst of enthusiasm and abandoning all of them the first time one misfires. One reliable bridge that runs five times a day beats ten you don't trust.
5. First drafts of routine writing
Status updates, meeting agendas, polite follow-ups, the third variation of the same client email — routine writing is where AI assistants genuinely earn their subscription. The workable pattern is draft-then-edit: let the model produce the skeleton from your bullet points, then spend your two minutes making it accurate and making it sound like you.
The boundary matters more than the tool. Anything involving numbers, commitments, or feelings — pricing, deadlines, performance feedback, apologies — gets written by you, or at minimum verified line by line. The model provides speed; you remain the source of truth.
How to actually start
Don't audit your whole week; that's a procrastination format. Instead, the next time you catch yourself doing something for the third time — the third rename, the third identical reply, the third copy-paste between the same two tabs — stop and spend fifteen minutes setting up a rule, a recipe, or a template for it. Three occurrences is a pattern, and a pattern is a candidate.
One task handed off per week is fifty per year. By March you'll wonder what you used to do all afternoon; the answer, it turns out, was relay work — and machines take relay work.
