Backlog rot is what happens when a team keeps creating work without forcing any of that work to prove it still matters. The backlog gets longer. The context gets thinner. The trust gets weaker. Eventually the board stops being a plan and starts being furniture.
I have seen teams with two hundred open items where everyone privately knows only five of them are real. The rest are ghosts: bug reports nobody can reproduce, feature ideas from customers who churned, tech debt tickets written by people who left. The backlog still looks impressive. It just does not help anyone decide what to do next.
How backlog rot starts
It usually starts with good intentions. Someone notices a bug but cannot fix it right now, so they file a ticket. A founder hears a customer request and drops it into the backlog. A developer spots cleanup work during a refactor and writes it down for later. None of those actions are irrational on their own. The problem is that most systems make adding work frictionless and removing work emotionally expensive.
That is how rot sneaks in. Preservation feels responsible. Deletion feels reckless. So the list grows, the team stops trusting it, and real priorities move somewhere else: Slack, someone’s notes app, or the founder’s head.
Why backlog grooming does not solve it
Backlog grooming is usually presented as the cure. It is not. It is maintenance for a design problem. If your system needs recurring archaeology sessions just to stay readable, the system is already broken. You are bailing water from a boat with a hole in it.
The deeper problem is that the backlog has no natural decay. Items can stay alive forever without new evidence, new urgency, or new ownership. That is why teams end up having the same conversation every quarter: should we clean this whole thing out and start over?
The alternative
The healthier model is to make work expire unless someone actively keeps it alive. If it matters, it will surface again with fresh context. If it does not, the team should be allowed to stop carrying it. That is not irresponsibility. That is focus.
The backlog cannot rot if there is no backlog. That is why Paperwork treats unfinished work as something that either earns attention now or loses active status. Teams do not need a bigger warehouse for good intentions. They need a shorter list they actually believe.