Mirror

I Was Never Unmotivated. The Task Was Underspecified.

Every time I could not get started on something for a year, I wrote down what the next action actually was. In most cases there wasn't one yet, which is a different problem.

For a year, every time I found myself unable to start something, I wrote one line: what is the literal next physical action. Not the goal, not the project — the thing my hands would do in the next sixty seconds. Sixty-three entries. In forty-four of them I could not answer.

a to-do card reading a vague area of responsibility

That ratio reframed the whole experience for me. I had been treating an inability to start as a motivational state — something about my energy, my discipline, the time of day. In seven cases out of ten it was that the task, as it existed in my head, did not have a first move, and I had been trying to summon enthusiasm for an object that was not yet actionable.

The typical shape was a to-do entry like “sort out the insurance.” There is no action there. There is a research question, then a decision, then probably a phone call, and the reason I could not start is that starting requires choosing which of those it is, and that choosing is itself a small piece of work I was not counting. Motivation was never the missing input; a decision was.

Writing the next action out loud resolved twenty-nine of those forty-four on the spot — not because the task became appealing, but because “find last year’s policy document” is something I can do without wanting to. The remaining fifteen did not resolve, and those turned out to be the interesting ones.

Of the fifteen, most had a hidden dependency on someone else, or on information I did not have and could not easily get. In other words they were genuinely blocked, and had been sitting on a list as though they were available. Discovering that a task was blocked was a relief every single time, and in several cases the next action turned out to be a message to someone that took two minutes and that I had been avoiding for weeks under the impression that I was avoiding the whole project.

The nineteen cases where I could name the action and still did not do it are, I think, the actual motivation problem, and they were a much smaller category than I would have guessed. Looking at them together, most involved a specific anticipated unpleasantness — a conversation likely to go badly, a number I did not want to see, a piece of work I expected to be bad at. That is not a motivational deficit either. It is anticipated cost, and the honest response is either to accept it or to change the task, not to try to feel differently about it.

What I do now is mechanical. Nothing goes on a list unless it is phrased as a physical action. Anything phrased as an area or an outcome goes in a different place, explicitly labelled as needing to be broken down, and breaking it down is itself a scheduled activity rather than something I expect to happen at the moment I want to work.

This is not new advice — it is roughly the core of a well-known productivity method — and I had read it years earlier and not applied it, because it is presented as an organisational technique and I did not have an organisational problem. I had what felt like a motivational problem. It turns out to have been the same problem, and the reason the advice did not land is that it was filed under the wrong heading.