Your productivity system is procrastinating

Your productivity system is procrastinating. It has been doing so quietly, in the form of an afternoon spent on tags, and it looks so much like work that neither of you has noticed.

The setup

Somewhere between the colour-coded tags and the third app migration, the actual work left the building.

You know the scene. It is a Tuesday, and there is a report due Thursday. You open the task manager to add the report, and the report needs a project, and the project needs a label, and the label scheme doesn’t quite work anymore. Two hours later you have a better label scheme. You have also found a template someone swears by, so you start moving everything into it. The report is still where it was, which is nowhere.

None of this is stupid. Each step is reasonable on its own, and the new scheme probably is a little better. That is what makes it so hard to catch.

Same sensation, zero output

Tweaking a system feels identical to working. It is focused, because there are decisions to make. It is effortful, because the decisions are fiddly. It is satisfying, because they get resolved, and you can see the board looking tidier than it did an hour ago.

Real work often feels worse. It is vague at the start, you can’t tell whether you’re doing it well, and the satisfaction arrives late or not at all. Given a choice between a task that feels like progress and a task that is progress, an afternoon will pick the first more often than you would like to admit.

So the sensation is the same, but the output is not. At the end of the afternoon the report is the same length, and the system is slightly more elaborate. It is also more expensive to maintain, which means tomorrow it will ask for more of your time.

None of this leans on research. Plenty has been written about procrastination, but this is an observation about how one particular afternoon goes, and you can check it against your own calendar.

A system’s job is to disappear

A good system is one you stop thinking about. You write the thing down, it is there when you need it, and you get on with the thing itself. The best ones are almost embarrassing to describe: a list, a page, a place to put tomorrow.

If you are admiring your system, it isn’t working. You are working, on the wrong project.

This is not an argument against tools, or against ever changing them. Setups do break. A list that has grown to 300 items has stopped doing its job, and cutting it is maintenance, not procrastination. What separates the two is what the change is for. Maintenance removes something that is in the way of the work. Fiddling adds something because adding it is pleasant.

A short plan is a decent place to start from. Three lines for the day leaves very little to organise, which is rather the point.

The test

At the end of the day, ask one question: did you touch the work, or only its container?

The work is the report, the draft, the call, the sanded shelf. The container is everything that holds it: the board, the tags, the template, the app. Time in the container is not always wasted, but it should be the smaller share, and you should be able to say so.

Be specific when you answer. “I reorganised my projects for 90 minutes and wrote 0 paragraphs” is an honest answer, and a useful one. It is not a verdict on you. It tells you where the afternoon went, and the next one can go somewhere else.

If the answer is container, try this the next day. Pick the one change you were about to make, write it on a single line, and leave it until the work is done. Most such changes are still there in the evening, and a good number turn out not to matter.

The concession

Yes, tools matter. We’d know: we make one. It is a productivity app called ogoria. That is exactly how we learned where fiddling goes to hide. It hides in the features that feel like progress, such as another view, another field, another way to sort. We have spent real afternoons in our own container, and we still do, on bad days.

What we try to do about it is the subject of the features we refuse to build.

For tomorrow, then: leave the setup alone until the first piece of work is done, and ask the question again at the end of the day.