There is a predictable arc to working alone. For the first few months a list is enough. Then the list gets long, then it gets old, then you stop trusting it — and at that point you keep the real work in your head and use the list as a decoration. The head version is faster right up to the week it fails, which it does at the worst moment.
The instinct at this stage is to look for a better app. That is the wrong move, and it is why most people have tried four. The problem is structural: your list contains two completely different kinds of thing and treats them identically.
A task and a project are not the same object
"Email the invoice" and "redesign the client's website" both sit on the list as one line each. One of them takes four minutes. The other is thirty things, half of which you have not thought of yet, and at least two of which depend on somebody else.
Once both are lines on the same list, the list becomes useless in a specific way: you cannot look at it and pick. Every glance requires you to re-derive which items are actually doable right now, which is exactly the work the list was supposed to do for you.
Capture in one place, sort later
Most disorganisation is not a filing problem, it is a capture problem. Work arrives by email, in a call, in a message from a client's colleague, and as a thought in the shower. If each of those lands somewhere different, no list can be complete, and an incomplete list is one you will stop trusting.
So separate capture from organising. One inbox that everything gets dropped into, unsorted, in five seconds. Then sorting happens once a day, as its own activity, when you have the context to decide what things actually are. Trying to file at the moment of capture is what makes people stop capturing.
Write the task so your tired self can start it
A task that gets skipped repeatedly is usually not hard, it is vague. "Website" is not a task. "Tax" is not a task. Both are subjects, and a subject requires you to do the thinking again every time you read it.
- Start with a verb. "Draft", "send", "call", "decide" — the verb tells you what kind of energy the thing needs.
- Be specific enough to start without a decision. "Send the phase-2 quote to Marek" needs nothing else; "quote" needs a whole conversation with yourself.
- One task, one action. If it contains "and", it is two tasks or a small project.
- Put the deadline in the date field, not in the title. A title reading "URGENT!!" is a note to yourself about a feeling, not information.
The test is simple: could you start this in the last twenty minutes of a bad Friday? If the answer requires a decision first, the decision is the actual task.
The state that everyone leaves out
Client work has a state that personal productivity systems rarely model: blocked on somebody else. You sent the draft, asked the question, requested the access. It is not done, and it is not something you can do.
Left on your task list, it clutters every review and slowly trains you to skim past things. Deleted, it disappears until the client asks about it three weeks later. It needs its own state.
| State | Means | You look at it |
|---|---|---|
| Next | Doable now, by you, in one sitting | Every day |
| Waiting | Blocked on a named person since a date | Weekly, and it is the list you chase from |
| Scheduled | Cannot start before a date, or is fixed in the calendar | When the date arrives |
| Someday | Real, not now, deliberately parked | Monthly, mostly to delete things |
The waiting list is the one that pays for the whole system. Every item on it is something you are owed, with a date attached, and going through it once a week is how you stop discovering a two-month-old blocker at the moment it becomes urgent.
Twenty minutes a week is what makes it survive
Every system decays. What separates the ones that last from the ones abandoned in month two is a scheduled moment for putting them back in order — not more discipline during the week.
- Empty the inbox. Everything captured this week becomes a task, a project, a calendar entry, or deleted.
- Read the projects list and check each one has exactly one next action. A project without one is a project that is quietly stalled.
- Read the waiting list. Anything older than a week gets chased today, not thought about.
- Look at the coming fortnight, not the coming week. This is the step that catches the deadline you were going to notice too late.
- Delete something. A list nobody prunes becomes a list nobody reads.
What makes client work different
Two things break a purely personal system once you have clients. Your deadlines are set by other people, and your work has to be reportable — somebody will eventually ask what happened on their project and when.
That is what pushes people from a notes app to something that groups work by client and keeps a history. Not the features: the fact that "what did we do for this client in March" is a question you will be asked, and reconstructing it from a personal list is an afternoon you do not get paid for.
When a list is no longer the right shape
The buying guide covers what to ask when the notes app stops holding it: how tasks attach to projects and clients, what the tool does with waiting states, and where reporting comes from.