The forty-second task: how small tools quietly remove repetitive work

The tasks that waste the most time are almost never the ones people complain about. Nobody builds a tool for something that takes forty seconds, because forty seconds does not feel like a problem. It feels like the cost of doing business, and it is over before you have finished being annoyed by it.

That is exactly why it survives. A two-hour task gets noticed, escalated, and eventually fixed. A forty-second task done nine times a day gets done nine times a day, for years.

Nine times forty seconds is six minutes. Six minutes a day is half an hour a week, and about 25 hours a year — three working days, spent on one small thing that never seemed worth fixing.

Finding yours

The difficulty is that these tasks are invisible from the inside. They are habits, and habits do not announce themselves. Two methods work reasonably well for surfacing them.

The three-day note. Keep a note open for three working days. Every time you catch yourself thinking "again?", write down what you were doing. Not a description of the whole workflow — just the specific action. "Reformatting a pasted list." "Looking up the same conversion." "Renaming a downloaded file so I can find it later."

Three days is deliberately short. A week of self-observation is a project you will abandon on day four. Three days is enough to catch anything genuinely daily, and daily is what matters.

The friction sentence. After the three days, look at your list and write each item as a single sentence with a number in it: "I reformat a pasted list about six times a day, and it takes roughly thirty seconds."

If you cannot put a number in the sentence, the task is not frequent enough to be worth automating yet. That is a useful result — it saves you building something you will not use.

What actually qualifies

Not everything repetitive should be automated. The tasks worth removing share three properties, and all three have to hold.

It has a predictable shape

The task is the same every time, or the variation is small and rule-based. Reformatting a list of names is predictable. "Replying to customer emails" is not — the shape changes with every message, and the part that takes the time is the judgement, which a tool cannot do for you.

A quick test: could you write down the steps such that someone else could follow them exactly, without asking you a question? If yes, it has a shape.

The cost is in the doing, not the deciding

Some tasks are slow because they involve a decision. Others are slow because your hands have to perform a sequence. Only the second kind is worth automating, because the first kind still requires you afterwards — you have only moved the decision, not removed it.

The clearest sign that a task is mechanical: you can do it while thinking about something else, and you are mildly irritated the entire time.

It happens often enough to repay the effort

The honest maths, which is worth doing before you build or install anything:

• Time saved per run × runs per day × working days = annual saving.
• Compare that to the time to build or find and learn the tool.

Thirty seconds saved, six times a day, over 250 working days, is roughly 12.5 hours. A tool that takes three hours to build pays for itself in about ten weeks. Ten seconds saved twice a day is about 1.4 hours a year — the same three hours of building would take more than two years to repay, and the tool would probably be obsolete first.

This is not a reason to never build small things. It is a reason to be honest about which category a particular annoyance is in, because the annoyance you feel is not proportional to the time it costs.

Three concrete examples

Abstract advice about "identifying repetitive tasks" is not very useful, so here are three real shapes that come up constantly.

Reformatting pasted content. You copy something from a document, a spreadsheet, or a webpage, and it arrives with the wrong line breaks, smart quotes, tabs where you wanted commas, or invisible formatting that fights your document. You fix it by hand. This is the most common forty-second task there is, it is perfectly predictable, and it is entirely mechanical.

Assembling the same reference. You need the current page's title and URL together, in a specific format, to paste into a note or a message. Doing it by hand is: select the URL, copy, switch, paste, switch back, select the title, copy, switch, paste, then fix the formatting. Six or seven actions for something that could be one.

Converting between two units or formats you always mix up. Whatever yours is — timezones, currencies, image dimensions, date formats. The task is short but requires a lookup, and the lookup is where the time goes. Usually the search result is a page carrying six ad units and a cookie wall between you and a number.

Each of these is a good candidate for exactly the reason it seems too small to bother with: predictable shape, mechanical cost, high frequency.

Choosing the right shape of solution

Once you have a task worth removing, the next mistake is reaching for a tool that is too big for it.

A keyboard shortcut or text expansion handles a surprising amount, costs nothing, and is built into most operating systems already. Try this first; it is free and instant.

A single-purpose web page works when the task is occasional, involves pasting something in and getting something out, and does not need to touch the page you are on. Bookmark it and forget it.

A browser extension is right when the task involves the page you are currently looking at, or when it happens often enough that opening a separate tab is itself the friction. Extensions are the heaviest option — they carry permissions, they update automatically, and they cost something on every page load — so they should be reserved for tasks that genuinely need to live in the toolbar. There is more on judging that trade-off here.

A script is right when the task involves your own files or a system a browser cannot reach, and when you are the only person who will ever run it.

The failure mode is skipping straight to the heaviest option because it feels the most like a solution. A text expansion that removes a task in one keystroke is better than an extension that removes the same task in one click, because the expansion costs nothing on every other page you visit.

The part nobody mentions

Removing a small task does not feel like anything. That is the strange thing about this whole category of work. You do not experience the twelve hours you got back — you experience nothing, because nothing happens. The irritation simply stops occurring, and within a week you have forgotten it was ever there.

This is why these tasks go unfixed for years despite being trivially fixable, and it is a genuinely good reason to write down the friction sentence with the number in it before you start. The number is the only durable evidence that the problem existed. Without it, three weeks later, you will not be able to tell whether the tool was worth building — you will just have a browser extension you no longer notice, doing a job you no longer remember hating.

That is the goal, incidentally. Software you stop noticing is software that worked.

TabVault came out of exactly this exercise. The friction sentence was "I lose my place about a dozen times a day, and finding it again takes thirty seconds" — predictable in shape, entirely mechanical, and frequent enough to be worth removing. The fix was to save the scroll position alongside the tab, so closing one stops costing anything.

The projects page lists what exists, and how a project gets from idea to shipped covers what happens between noticing an annoyance and publishing something for it.