How to keep a backlog without drowning in it
A backlog stays useful only if you visit it on a fixed, low-frequency schedule, roughly weekly, to delete what no longer matters and promote what has become timely. Left unvisited, it grows into an anxiety-inducing wall of old intentions. The fix is not keeping it shorter, it is keeping the visits regular so nothing rots there unnoticed for months.
What a backlog is actually for
A backlog exists to hold everything that is real but not urgent: someday projects, ideas worth keeping but not acting on this week, tasks with no deadline attached yet. Its entire value comes from being a safe place to put something so it stops occupying active attention. The moment it stops feeling safe, because it has become a huge, unreviewed pile of old guilt, it stops doing its job and starts doing the opposite, adding a low grade dread every time you glance at it.
The two failure modes
A backlog fails in one of two directions. The first is neglect: items get added and never looked at again, so the list becomes a graveyard of intentions you eventually stop believing you will ever act on. The second is over-visiting: checking it daily, which turns a holding pen meant for later into a second active list competing with today's tasks for attention, defeating the entire point of separating them in the first place.
The weekly review that fixes both
A single weekly pass through the backlog, aiming for speed rather than depth, solves both failure modes at once. Go through each item and make one of three calls: still relevant, no longer relevant, delete it, or has become timely enough to move up. Do not try to act on anything during this review. The review's only job is sorting, the same way sorting a fresh brain dump is a separate step from acting on it.
A worked review: twenty three items, Sunday evening
Scanning down, "look into a pottery class" has sat for four months with zero pull toward actually doing it. It gets deleted, not guiltily, just honestly. "Repaint the bathroom" still feels real, stays put. "Ask about switching insurance providers" was added when a friend mentioned a better rate, and this week you noticed your own renewal notice arrived, so it moves up into next week's tasks. The other twenty items get a quick glance and mostly stay exactly where they are. The whole review takes about twelve minutes and leaves twenty two items, one fewer, one promoted, the rest untouched but confirmed still worth keeping.
Why deleting from a backlog feels harder than it should
Deleting a backlog item can feel like admitting failure, especially if it represents a version of yourself you had hoped to become, the person who takes up pottery, who finally learns another language. It helps to reframe deletion as updated information rather than failure: the person you are now, with the actual life you actually have, does not want this particular thing enough to act on it after several honest chances, and that is a fact worth knowing rather than a flaw to feel bad about.
Keeping the backlog from swallowing today
Not every passing thought needs to become a backlog entry in the first place. Some ideas are worth a moment's consideration and then letting go of entirely, without ever writing them down at all. Reserve the backlog for things you would genuinely be upset to lose, since a backlog that captures every stray idea indiscriminately grows faster than any weekly review can keep up with.
The backlog should also never be the first place you look when deciding what to do today. Today's list comes first, built from real deadlines and a handful of chosen priorities. The backlog gets checked once a week, on its own schedule, specifically so it cannot compete with today's shorter, more urgent list for your attention every single morning.
This connects with a three list system that stays small, where the backlog is explicitly the "later" pile, and with what to do with a list right after a brain dump, since most backlog items start life as a dump before getting sorted here. If deleting things from any list feels harder than it should, how to tell when a task should be deleted covers that decision in more depth.
Where it lives in Drifta
Drifta's Backlog is built specifically for this purpose, a third list separate from Daily Tasks and Up Next, so someday items have a real home instead of cluttering the lists you actually check every day. It holds as much as you put into it, with no practical limit on length. The weekly review habit is still the part that has to come from you, since no list structure on its own prevents neglect or over-checking, no matter how well designed the list itself happens to be.
Common questions
How big can a backlog get before it is a problem?
Size alone is not really the problem, since a backlog is supposed to hold everything that is not today's business. The problem is an unvisited backlog, regardless of size. A hundred item backlog you review weekly is healthier than a fifteen item one you have not opened in two months.
Should I ever delete something from my backlog without ever doing it?
Yes, regularly. An item that has sat untouched through several reviews and still generates no motivation to act is honest information that it may not actually matter to you, whatever story you originally told yourself about why it was added.
Is it bad to add things to the backlog that I know I'll probably never do?
Not necessarily, as long as the review habit stays intact. The backlog's job is to get an idea out of your active attention, not to guarantee it happens. A regular review is what prevents "probably never" items from quietly taking over a list meant mostly for real intentions.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.