Most task lists are an accumulation problem without management. Each week more things are added than are done. The list grows. After months there are hundreds of tasks that nobody will ever do, mixed in with the ones that actually matter. The result is a list that generates anxiety instead of clarity.
The backlog is the solution to that problem: a place where things live that do not fit this week, managed in a way that does not produce stress.
The infinite list problem
An unlimited task list creates several simultaneous problems. The first is cognitive: seeing a long list of pending items activates the feeling that there is too much to do, which in turn produces paralysis or the selection of the easiest tasks rather than the most important ones.
The second is signal degradation: when there are two hundred tasks on the list, the importance signal for each one is diluted. Everything seems equally urgent or equally deferrable. The list loses its main function — guiding attention towards what matters most.
The third is honesty: many of those two hundred tasks will never be done. They are on the list out of habit, to avoid losing them, in the hope that someday there will be time. Keeping them active consumes mental energy without producing anything.
What a backlog is
The backlog is a list separate from the current week’s task list, where all the things live that might be relevant but have not been selected for the current week.
The difference from the task list is intentional: the backlog is not what you are going to do. It is an inventory of what could be done if there were capacity. It has a different status: it does not produce the pressure of “this must be done” but rather “this could be done if the occasion arises.”
This status change is what eliminates the anxiety. Tasks in the backlog are not forgotten: they are stored. If they are important, they will appear in the weekly review. If they do not appear week after week, that is information: they were probably not as important as they seemed.
How to manage the backlog
The backlog needs periodic maintenance. Not daily: weekly or monthly. In each review, three things happen:
Clean out what is no longer relevant. Tasks that have been in the backlog for weeks or months without being selected are candidates for deletion. If a task has not been prioritised for two months, it is unlikely to be in the next two. Deleting it is not giving up: it is being honest about reality.
Update priority. Circumstances change. What was secondary last month may be critical now, and vice versa. The backlog should reflect current reality, not the state when each task was added.
Select what enters the week. The weekly review includes looking at the backlog and selecting, if there is capacity, which backlog tasks deserve to enter the following week.
The backlog and the week
The relationship between the backlog and the week defines the quality of the system. The week has limited capacity; the backlog has space for everything that does not fit. The flow is: newly captured items go to the backlog, the weekly review selects from the backlog what enters the week, and at the end of the week what was not completed returns to the backlog.
This flow produces three benefits: nothing is lost, the week has a realistic size, and the backlog is honest about what exists.
The week’s task list should be short: between ten and twenty tasks for the whole week, depending on complexity. If it has a hundred, it is not a week list: it is the complete backlog with a different label.
