Why Half Your List Never Gets Done: How to Write Tasks You'll Actually Start
"Car." "Sort out insurance." "Mum." Five weeks on the list - while "email Jonas the invoice number" took four minutes.
Three lines have been on your list for five weeks: Car. Sort out insurance. Mum.
In the same period you wrote email Jonas the invoice number from the March file and did it in four minutes, on a day that was otherwise a write-off.
The difference is not importance and it is not motivation. It is that one of those lines is executable and the others are topics. Learning how to write tasks properly - so that the first physical action is already decided before you read the line - removes most of what looks like procrastination, because an unfinished sentence on a list quietly asks you to do the planning at the exact moment you have the least capacity for it.
The test: could a stranger start it?
Hand your list to someone competent who knows nothing about your life. Which lines could they begin in the next ten seconds?
Ring the garage on 01234 567890 and book the service - yes. Car - no, because it requires knowledge only you have, and at four in the afternoon you are functionally that stranger. The line has to carry its own instructions.
Start with a verb that describes a physical action
Good verbs are ones you could film: ring, open, print, send, write, put, find, pay, ask.
Bad verbs are categories of feeling: sort out, handle, deal with, look into, get on top of, organise. Those describe an outcome you want, not a movement you can make, and starting is the expensive part precisely because the movement is missing.
Sort out insurance is a mood. Open the renewal email and write down the current price is a task.
Put the missing information in the line
Every piece of information you leave out is a place to fall out of the task: the phone number, the file name, the person's surname, the reference, the link.
Write them in. Ring the dentist becomes ring the dentist, number in contacts, ask for a Tuesday. It takes eight extra seconds now and saves the four-minute lookup later - and the lookup is where the task dies, because opening a browser at that moment is how you end up somewhere else entirely.
One decision per line - and if the decision is the work, write that
Many stuck items are not stuck because they are hard. They are stuck because there is an unmade decision hiding in them.
Insurance is stuck because you have not decided whether to renew or switch. So write the decision as the task: decide: renew or switch - fifteen minutes, compare two quotes. Once a decision is named, it can be done. Left implicit, it just sits there radiating vague weight.
Size it to one sitting
A task should be the smallest version that changes the state of things - one sitting, no dependencies, finishable.
If it needs three sessions, it is a project rather than a task, and the list needs only its first step. That is what breaking work down actually produces: not a smaller feeling, but a line you can execute without thinking.
Write for the person you will be at four in the afternoon
This is the whole discipline, and it is a genuinely different way to write.
The person writing the list has all the context: they know what "mum" means, which insurance, what the next step is. The person doing it, three days later, tired, has none of that - and the gap between the two is where lists die. Writing while holding the context is a kind of trap, because everything obvious to you now will be a small research task by Thursday.
So write it slightly over-explained. You are not writing notes, you are writing instructions for someone who will arrive with less than you have.
Add when and where, when it matters
For anything you keep intending and never doing, attach it to a moment and a place rather than a day: after lunch, at my desk, ring the garage.
That is an implementation intention, and it converts "sometime today" - which competes with everything - into a specific slot that a specific cue can trigger.
Rewrite anything you have skipped three times
Here is the most useful habit in the article. When you notice a line you have passed over three or four times, do not move it again. Assume it is badly written and rewrite it.
Nine times out of ten the problem is one of the four above: no verb, missing information, a hidden decision, or too big. Rewriting takes twenty seconds and turns a five-week resident into something you do the next morning. And if you rewrite it and it still does not move, that is useful information too - it may belong on the list of things you have decided not to do.
Two things that are not tasks
Feelings. Be better at email. Stop being late. Get organised. Those are not tasks, they are verdicts, and they cannot be finished. If you want them on paper, convert them: unsubscribe from ten newsletters is a task; be better at email is a mood with a to-do box next to it.
Other people's actions. Hear back from the council is not something you can do. It belongs on a waiting-for list with a date to chase, so that it is being tracked without pretending it is yours to execute.
Capture fast, rewrite later
None of this means you should compose careful sentences at eleven at night. Capture is for speed: car is a perfectly good thing to write down in the moment, because the alternative is losing it.
The rewriting happens later, in a weekly pass over the list, where you turn the brain dump into executable lines. Two different jobs, two different modes - and the second one is the one most people skip, which is why their list is full of topics.
The short version
Half your list is not tasks, it is topics - and a topic asks you to plan at the worst possible moment. Write lines a stranger could start: a physical verb, the information included, one decision per line, and a size that fits one sitting. Write for the tired version of you rather than the informed one, attach a where and when to anything you keep avoiding, and rewrite - rather than move - anything you have skipped three times. Keep capture fast and messy, and do the rewriting in a weekly pass.
Keep reading
Frequently asked questions
Why do some tasks sit on my list for weeks?
Usually because they are topics rather than tasks. "Car" or "sort out insurance" require planning before they can be started, so reading them asks you to do that planning at the exact moment you have least capacity. A task you can start is one where the first physical action is already decided - "ring the garage on this number and book the service" - and the difference is not importance or motivation, it is executability.
How should I word a task so I actually do it?
Start with a verb you could film - ring, open, print, send, write, find - rather than a category of feeling like sort out, handle or deal with. Put the missing information in the line itself: the number, the file, the person, the reference, because every lookup is a place to fall out. Keep it to one decision and one sitting, and write it slightly over-explained for the tired version of you.
What do I do with a task I keep skipping?
Do not move it again - rewrite it. Nine times out of ten the problem is one of four things: no physical verb, missing information, a hidden decision, or it is too big for one sitting. Rewriting takes twenty seconds. If it still does not move after a rewrite, that is useful information too, and it may belong on a list of things you have deliberately decided not to do.
Should I write tasks carefully when capturing them?
No - capture and rewriting are two different jobs. In the moment, speed matters more than quality: writing "car" at eleven at night is fine, because the alternative is losing it entirely. The rewriting happens in a weekly pass over the list, where you turn a brain dump into executable lines. Most people skip the second job, which is why their list fills up with topics.
