To pick your first automation, list every repetitive task, score each one on frequency, annoyance, and setup time, then build the task with the highest total. This replaces the stuck feeling of “I don’t have time to figure this out” with a number you can trust in about one afternoon. No tool decision required yet.
- The reason none of your tasks get automated is that you never ranked them, so every option feels equally urgent and equally skippable.
- A simple score built from frequency, annoyance, and setup time turns a vague wish into one obvious winner.
- Frequency times annoyance divided by setup time gives you a number, and the highest number is where you start.
- You do not need to know which tool you will use before you score the tasks.
- A wrong first pick still teaches you more than a perfect plan you never build.
- One weekend of scoring beats months of waiting for the perfect moment to figure it out.
You know the task. The one you do every week that makes you sigh before you even open the tab. You have thought about automating it. You have also thought about automating four other things. And because you cannot decide which one matters most, you build none of them. That is the trap. You are too busy doing the work to build the thing that would do the work. So let me hand you a way to pick your first automation that takes one weekend and some fifth grade math.
To pick your first automation, you score every repetitive task on three numbers, frequency, annoyance, and setup time, then multiply and divide to get a ranking that tells you exactly where to start. A pick-your-first-automation score is a plain number that compares your repetitive tasks so one of them wins and the rest wait their turn. No gut feeling. No tool shopping. Just arithmetic you learned before middle school.
The stuck feeling has a name. It sounds like “I don’t have time to figure this out.” What is really happening is that you have no way to rank the options, so your brain treats all of them as equally important, which means none of them ever reach the front of the line. The fix is not more time. The fix is a tiebreaker.
Why does knowing which task to fix first matter so much?
Knowing which task to fix first matters because the stall is not caused by laziness or lack of time, it is caused by the absence of a ranking, and without a ranking every task competes for the same attention and loses to the daily grind. When every option feels equal, the urgent beats the important every single time. The email you have to answer right now wins over the system that would answer a hundred emails for you.
The thing that stops most automation projects is not difficulty. It is the lack of a way to decide what comes first.
This pattern of urgent crushing important is old and well documented. The Eisenhower Matrix, a tool for sorting tasks by urgency and importance, points at the same thing. If you want the history behind why busy people never build the important stuff, the write-up on the Eisenhower Matrix at Todoist covers the “mere urgency effect” plainly. The point for us is simpler. You need a score, and the score has to be easy enough to do on a Saturday.
What is the scoring math, exactly?
The scoring math is three ratings and one calculation, you rate each task from one to five on frequency, one to five on annoyance, one to five on setup time, then compute frequency times annoyance divided by setup time, and the highest result is your first build. That is the whole thing. Three numbers in, one number out.
Here is what each term means so you rate them the same way every time.
- Frequency is how often the task happens. Many times a day is a five. Once a month is a one.
- Annoyance is how much you dread or resent doing it. Soul-draining is a five. Mildly dull is a one.
- Setup time is how long you think it would take to build the automation. A quick job is a one. A multi-week build is a five.
Notice the divide. Frequency and annoyance push the score up, because those are the pain. Setup time pushes it down, because effort is the cost. The formula rewards the tasks that hurt a lot and are cheap to fix. Those are your quick wins, and quick wins are exactly where you want your first build to live.
Frequency times annoyance divided by setup time turns a pile of equally annoying tasks into one ranked list with a clear winner.
A worked example you can copy
Say you have four tasks you keep meaning to automate. Here is how the math plays out.
| Task | Frequency | Annoyance | Setup Time | Score |
|---|---|---|---|---|
| Sending the same client intake email | 5 | 4 | 2 | 10.0 |
| Copying form entries into a spreadsheet | 4 | 5 | 2 | 10.0 |
| Posting the weekly update to three places | 2 | 3 | 3 | 2.0 |
| Reformatting the monthly report | 1 | 5 | 4 | 1.3 |
Two tasks tie at the top. The monthly report feels like the worst one when you are doing it, a full five on annoyance, but it happens once a month and takes a while to build, so it sinks to the bottom. That surprise is the whole value of the math. The task you dread most is often not the task you should automate first. Score it and the truth shows up.
Breaking a tie
When two scores match, pick the one with the lower setup time. You want a finished build this weekend, not a half-finished one. A win you can see makes the next build easier to start. Momentum is real, and the fastest path to momentum is a task you can actually complete.
How do I list the tasks without missing any?
To list the tasks without missing any, work a normal week with a notepad open and write down every repetitive thing the moment you catch yourself doing it, because the tasks that drain you most are the ones you have stopped noticing you even do. You will not remember them from a chair on Saturday. You have to catch them live.
Keep the list loose for a few days. Anything you type the same way twice, anything you copy from one place to another, anything that makes you sigh. Write it down. You are not scoring yet. You are collecting. By the weekend you will have a messy list, and a messy list beats a blank page every time.
- Open a note on Monday morning and leave it open all week.
- Every time a task repeats, jot it down in a few words.
- On the weekend, cross out duplicates and keep the ten that sting most.
- Score those ten. Build the winner.
This idea of starting from how your time actually splits across tasks is not something I made up. When researchers look at what work is automatable, they break jobs into individual activities and weigh each by the time spent on it. The McKinsey analysis on where machines can replace human work finds that predictable, structured activities are the most automatable. Your intake email is predictable. Your dread is not a good ranking tool. Frequency is.
What if I pick wrong?
If you pick wrong, you still come out ahead, because a built automation teaches you how the tools behave, how long builds actually take, and how to score the next one better, while a perfect plan you never start teaches you nothing at all. Mistakes are part of the process here. Welcome them.
The first build is the one where your setup-time guesses were probably off. That is fine. Next time you score, your numbers are sharper because you have real experience instead of a guess. The math gets more honest the more you use it. A finished wrong pick beats an unfinished right one, every weekend of the year.
A wrong first automation still teaches you more than a flawless plan you never build.
If you want a more formal version of this same quick-wins logic, the impact-effort approach lives in project work too, where simple scoring surfaces the fast, high-value tasks first. Our method is a stripped-down cousin of that. You do not need a workshop. You need three columns and twenty minutes.
The urgent-over-important problem is often credited to a line Dwight Eisenhower quoted from a university president, that he had two kinds of problems, the urgent and the important, and the urgent were rarely the important. The phrasing has shaped productivity thinking ever since, which is why the matrix still carries his name.
Almost every time I open a client’s task list, I find the thing they are most eager to automate is the thing that happens least often. They want to kill the monthly report because it ruins one day a month. Meanwhile the ten-second copy-paste they do forty times a week never makes the list, because it is too small to resent. When we score it, the small repetitive one wins by a mile. That flip, from the loud rare task to the quiet frequent one, is the moment the math earns its keep.
How do I pick my first automation when everything feels important?
Score each repetitive task on frequency, annoyance, and setup time, then rank them. The one with the highest frequency times annoyance divided by setup time wins. The ranking removes the paralysis because you are no longer choosing by feel. You are choosing by number, and numbers do not argue back.
What tasks should I automate first in my small business?
Automate the task you do most often that also annoys you and is quick to build. High frequency plus high annoyance plus low setup time equals your best first project. Rare tasks, even painful ones, should wait. The time you save adds up through repetition, not through drama.
How long does it take to figure out which task to automate?
Collecting the tasks takes one normal work week of jotting them down as they happen. Scoring and picking takes about twenty minutes on the weekend. So the deciding is fast. The watching is what takes a week, because you cannot score tasks you have forgotten you do.
Why do I never get around to building automations?
Because you have no ranking, so every option competes for the same attention and loses to urgent daily work. Without a tiebreaker, your brain treats all tasks as equal and stalls. A simple score breaks the tie and gives you one clear place to start.
Do I need to know which tool to use before I score tasks?
No. Score the tasks first, pick the winner, then choose the tool that fits that one job. Deciding the tool before the task is backwards and adds a second stall. Make.com and a bit of help from Claude or ChatGPT cover a lot of first builds.
What if my top two tasks tie on score?
Break the tie with setup time and build the faster one. A finished automation this weekend beats a bigger one left half-built. The quick win gives you momentum and real numbers, which make your next scoring round more accurate. Speed to a finished result matters more than ambition here.
Pick one normal week. Keep a note open and catch every repetitive task as it happens. On the weekend, score your top ten on frequency, annoyance, and setup time, do the math, and build the winner. One finished automation beats four you keep thinking about.
When you are ready, save the scoring math for the weekend you finally sit down to build, so the formula is right there when you open that note.
… and see more of my posts in your Google results.
