How to stop doing things that could do themselves.

There is a category of work that almost every digital team leader does every day and that none of them should be doing: repetitive, predictable activities that always follow the same pattern. Answering the same question for the fifteenth time. Manually sending the same type of message to different people. Updating by hand data that already exists somewhere else.

These activities share one characteristic: they are automatable. Not in the abstract sense of "in theory it could be" — in the concrete sense of "with the right tools, this stops requiring your presence within the next week".

The problem is that automating requires an initial investment of time and attention. And that investment competes with everything that seems urgent now — which is always a lot. The result is that automatable activities remain manual for months, sometimes years, consuming a little time and attention every day that could have been free.

The cost of inertia is invisible but real. Every hour you spend doing something a system could do is an hour you did not spend building something that did not exist before.

How to identify what to automate: the three-question method

For every activity you do regularly, ask yourself three questions:

Question one: does this activity always follow the same pattern? If yes — if every time you do it the steps are substantially the same, even if details change — it is a candidate for automation.

Question two: if I did not do this myself, what would happen? This separates necessary activities from those done out of habit or control. If the answer is "nothing significant, or someone else could handle it", that activity is a candidate for delegation or automation.

Question three: how much time does it take each time, and how often do I do it? Multiply time by frequency. A five-minute activity done every day is thirty hours per year. Those hours, freed by automation, can go towards something that truly makes a difference.

The five categories of automatable activities almost nobody automates

1. Answers to frequent questions. Every team has questions that always come back. These, collected and systematised, can have ready answers that arrive automatically at the right moment. You are not ignoring the person — you are giving the best possible answer, the one you built carefully, instead of the rushed one.

2. Welcome and onboarding messages. Every new member deserves the same quality welcome. If that welcome depends on your availability when the person joins, quality varies enormously. If it is automatic, every person receives exactly what they should receive, in the right order, at the right time.

3. Team activity tracking. How many times a week do you manually check who is working and who is stopping? That check, if done on defined numbers and behavioural signals, can be automated. Instead of you looking for problems, the system brings them to you when they exceed a relevant threshold.

4. Content and update distribution. You created a video, wrote a document, prepared an update. If the distribution process depends on you — a message you send, a notification you give — there is a failure point every time you are busy or forget. If the system distributes automatically, the content always arrives.

5. Post-conversation follow-up. You had a call with someone. There is interest. In the following days, that person should receive deepening materials, answers to doubts that emerged, a reminder of the next step. If this depends on you remembering, it happens sometimes and sometimes not. If automated, it always happens.

The objection I always hear

"But people notice it is automatic and feel treated like a number."

True in one specific case: when automation is poorly designed, generic, obviously mechanical. But a well-written automatic message, sent at the right moment, using the person's name and referencing the specific context of the relationship — that does not feel automatic. It feels attentive. It feels more caring than many manual messages written in a rush.

The quality of automation depends on the quality of design. A well-written automatic message sent at the right time is more human than a poorly written manual message sent late.

Where to start this week

Identify the single repetitive activity you do most often. Build the template, the process, the automatic sequence that handles it. Test it. Refine it. Then move to the second.

In three months you will have automated five or six things you are currently doing manually. The freed time accumulates. And that accumulated time, invested in activities only you can do, produces something those manual hours would never have produced.

The system does not build itself in a day. But every automation you add is a permanent piece — you do not need to redo it tomorrow, you do not need to remember to do it next week. It is done. Forever. For everyone.