How to triage a task backlog that got out of hand
By The Serena Team
There is a size past which a task list stops functioning. The exact number varies, but the symptom is unmistakable: you stop opening it. Not because the work disappeared, but because opening it costs something. Every glance delivers a small dose of guilt and no useful information, so you begin keeping the real list in your head and using the app as an archive you feel bad about.
The instinct at that point is to reorganize: new projects, new labels, a better hierarchy. This rarely helps, because the problem is not structure. It is that most of the items are no longer real. Triage means making one decision per item, quickly, and accepting that a lot of them are going to be deleted.
Three rules before you start
These exist because every one of them is a way the exercise fails.
- One pass only. Set a timer for forty-five minutes. Whatever you do not reach stays untouched until the next session; do not extend, because a triage session that runs three hours does not get repeated.
- No reorganizing. Do not create projects, rename labels, or adjust structure. Reorganizing feels like progress and produces none. Structure is a separate job for a separate day.
- No doing the work. If an item takes two minutes, it still gets triaged rather than completed. Twenty two-minute tasks is the whole session.
Four destinations, one decision each
Every item goes to exactly one of four places. If a decision takes more than about five seconds, that hesitation is itself the answer, and the answer is usually the second destination.
Active
You will genuinely act on this within two weeks and you know what the first step is. Be strict. This bucket should end up uncomfortably small.
Deleted
It no longer matters, it was aspirational, or it has sat untouched long enough to have answered the question itself. This should be the largest bucket by a wide margin.
Someday
Genuinely valuable but not now. One list, no dates, reviewed monthly rather than daily. The rule that keeps this honest: if it has never been promoted out of Someday in six months, delete it.
Waiting on
Blocked on another person or an external event. Record who or what, and the date you started waiting. This list is short and worth reading weekly, because most of it is one nudge away from moving.
Why the delete pile is so large
Task lists accumulate several kinds of item that were never real work, and recognizing the categories makes the deletions faster and less uncomfortable.
- Aspirations recorded as tasks. "Learn Spanish" is a goal that would need a plan; as a checkbox it can only ever be a reproach.
- Ideas captured in enthusiasm. Worth having had, not worth carrying. The good ones resurface on their own.
- Work that was overtaken by events. The project changed, someone else did it, or the deadline passed and nothing bad happened.
- Duplicates in different words, which accumulate invisibly because they never sort next to each other.
- Things you are avoiding for a reason you have not examined. These are worth thirty seconds of thought. Sometimes the reason is that the task is genuinely a bad idea, and deleting it is correct rather than a failure of nerve.
Work oldest to newest
Sort by creation date ascending and start at the top. This is deliberate: the oldest items are both the easiest to judge and the most demoralizing to encounter, which is exactly why they should go first.
Age carries information that nothing else on the item does. Something created eight months ago and never touched has been tested by eight months of your actual priorities and lost every time. That is stronger evidence than whatever you thought when you wrote it. The first stretch of a triage session is usually fast for this reason, which builds enough momentum to get through the genuinely ambiguous middle.
Keeping it from regrowing
Triage without a change in capture habits buys about three months. Three adjustments do most of the work of keeping the list readable.
Separate capture from commitment
Keep capturing everything; the cost of a missed commitment is high. Just stop treating the capture list as the task list. Capture is cheap and generous, commitment is deliberate and scarce.
Write the next physical action
"Sort out the invoice thing" cannot be started and will be skipped indefinitely. "Email Dana the March invoice numbers" can be done in four minutes. Vagueness is the main cause of items aging.
Give Someday a real review slot
Once a month, ten minutes. Promote what is now relevant, delete what has aged out. A Someday list that is never read is functionally a delete pile with extra guilt attached.
Key takeaways
- One timed pass, no reorganizing, no doing the work.
- Every item gets exactly one of four destinations: Active, Deleted, Someday, or Waiting on.
- Deleted should be the largest bucket; hesitation is usually a signal to demote or delete.
- Sort oldest first. Age is real evidence about importance, and the early items are the easiest calls.
- Separate capture from commitment and always write the next physical action, or the list regrows.
Frequently asked questions
What if I cannot bring myself to delete things?
Move them to a single archive list instead. It gets the items out of your working view, which is the actual goal, and after a few months of never consulting it most people become comfortable deleting the whole thing.
How small should the active list be?
Small enough to read in one glance without scrolling. For most people that is somewhere between ten and twenty-five items. If you cannot see the whole thing at once, you will start avoiding it again.
Should I triage a shared team backlog the same way?
The four destinations transfer, but deletion needs a different owner. Do not unilaterally delete items that other people created. Run the pass, propose the deletions, and let the person who created each item confirm. The conversation is usually short and frequently reveals work that quietly stopped mattering to everyone.
Is it worth triaging if my list is only moderately long?
The useful signal is whether you avoid opening it, not the item count. A list of sixty items you read daily is healthier than a list of thirty you have not looked at in a month.