What it is
Backlog rot is the progressive decay of a task list that is never forced to justify its own existence. Items get created with good intentions, sit untouched for weeks or months, lose their original context, and eventually become noise that the team scrolls past without reading. The backlog stops being a plan and starts being a liability. It costs cognitive overhead every time someone opens it, and it quietly undermines trust in the system because everyone knows most of those items will never get done.
How it starts
It starts innocently. Someone files a ticket for a bug they noticed but cannot fix right now. A PM adds a feature idea from a customer call. A developer stubs out a tech debt item during a refactor. Each individual item is reasonable. But the system has no natural pressure to resolve them. There is no expiration date, no cost to keeping them open, no mechanism that says "this has been sitting here for 60 days and nobody has touched it, so it probably does not matter." The accumulation is frictionless. The cleanup is not.
The symptoms
You know you have backlog rot when grooming sessions feel like archaeology. When new team members ask about items and nobody remembers why they exist. When the backlog has 200+ items and the team ships from a mental list of 5. When "backlog bankruptcy" becomes a recurring conversation every quarter. When the act of opening the project board triggers a small, familiar dread. These are not signs of a lazy team. They are signs of a system that creates without expiring.
Why grooming doesn't fix it
The standard answer to backlog rot is "just groom the backlog." Schedule a recurring meeting, go through the items, close what is stale. In practice, grooming is the ceremony equivalent of bailing water out of a boat with a hole in it. The hole is still there. Items keep accumulating between grooming sessions. The meeting itself becomes another ceremony tax on the team. And nobody actually enjoys doing it, so it gets skipped or rushed, which means the rot returns faster than the grooming can address it. The fix cannot be another meeting. It has to be structural.
The alternative
The alternative is a system where work expires by default. Where keeping something alive requires a deliberate act, not passive neglect. Where the daily triage forces you to confront what is on your plate and decide whether it still matters. This is the core idea behind Paperwork's Visible Work Method: instead of building a backlog that rots, you maintain a feed that flows. Active work stays visible. Finished work is recorded. Everything else decays unless someone chooses to keep it. The backlog cannot rot if there is no backlog.