Everyone loves adding to the backlog. Few people enjoy removing from it.

The Accumulation Problem

Backlogs grow by default. Every conversation spawns an idea. Every code review surfaces a “wouldn’t it be nice if.” Every debugging session reveals adjacent problems that technically should be fixed too.

This is fine for a while. A healthy backlog contains options. It’s a menu of useful work you could do next.

But menus have limits. A restaurant with three hundred items isn’t offering choice — it’s offering confusion. And a backlog with a hundred items isn’t a plan — it’s a landfill.

Why Items Stay

The reason backlogs only grow is emotional, not logical.

Every item on the list represents a moment when someone cared about something. Deleting it feels like dismissing that moment. What if we need it later? What if the person who added it asks about it? What if it turns out to be important?

These fears are real but almost never justified. If something is truly important, it will come up again. If it doesn’t come up again, it wasn’t important — it was interesting. There’s a difference.

Interesting items are the most dangerous backlog residents. They’re plausible enough to survive every grooming session but never urgent enough to actually get done. They accumulate quietly until the backlog is more aspiration than action.

The Gardening Metaphor

A garden doesn’t work by adding plants indefinitely. You add, yes. But you also prune. You pull weeds. You remove plants that aren’t thriving to give space to the ones that are.

The backlog works the same way.

Pruning means asking: “If this appeared for the first time today, would I add it?” If the answer is no, remove it. The fact that past-you thought it was worth doing doesn’t obligate present-you to agree.

Weeding means removing items that have been superseded. The task to “add caching” that was created before the architecture changed. The bug fix for a module that got rewritten. The feature request that a different feature already solved.

Spacing means recognizing that a full backlog crowds out new ideas. If every slot is taken by old work, there’s no room for the insight you’ll have next week.

The Grooming Session

Effective backlog grooming isn’t about prioritizing — it’s about discarding. Prioritization is easy when the list is short. It’s impossible when the list is long, because the combinatorial space of “what should we do next” explodes.

My approach to grooming:

  1. Delete first — Remove anything that’s been sitting for more than a month without movement. If it survived a month of not being important enough to start, it’s not important enough to keep.

  2. Merge second — Look for items that overlap. Three separate tasks about “improve error handling” are really one task with three entry points. Combine them.

  3. Sharpen third — For items that survive, rewrite them so they’re actionable today. Not “investigate performance issues” but “profile the API endpoint that times out on large payloads.”

  4. Prioritize last — With a clean, sharp, short list, prioritization becomes obvious. The most impactful, most actionable item floats to the top without much debate.

The Fear of Loss

The hardest part of pruning is accepting that you’ll occasionally lose something good. It will happen. You’ll delete an item and three months later realize it would have been useful.

This is acceptable. The cost of occasionally losing a good idea is far lower than the cost of maintaining a backlog full of mediocre ones. A clean list with one missing gem outperforms a cluttered list where the gems are buried.

If you’re worried about permanence, keep an archive. But don’t look at it during grooming. The archive exists to quiet the fear, not to influence the decision.

Small Lists Ship

The teams and individuals I’ve seen ship the most consistently share one trait: short backlogs.

Not because they have fewer ideas. Because they’re disciplined about which ideas earn a place on the list. The backlog isn’t a record of everything that could be done. It’s a curated set of things that will be done, soon, by someone specific.

Treat your backlog like a garden. Visit it regularly. Pull more than you plant. And notice how much easier the remaining work becomes when it has room to grow.