How to keep a backlog without hoarding ideas

Every team has a backlog, even if it is not called that. It is the list of things you might do: ideas from customers, improvements somebody suggested, nice-to-haves from last quarter. It starts as a useful queue. Over time it grows into a graveyard of good intentions that nobody looks at, which means nothing in it ever happens and every new idea gets added to the pile.

A backlog only works if it is short enough to read.

A backlog is a queue, not a museum

The purpose of a backlog is to answer one question: what should we pick up next? If it has 300 items, it cannot answer that. You end up choosing whatever is newest or loudest, which is what you would do without a backlog at all.

Keep it to a size someone can read in five minutes. For most small teams, that is 20 to 40 items.

Separate next from someday

Two kinds of ideas live in a backlog:

• Next: things you genuinely intend to do soon, with enough detail to start
• Someday: interesting, but not now

On a 2D board, Next Steps is the queue: things that will move into Mine soon. Someday ideas belong somewhere else: a single parked row, a separate list, or nowhere. Mixing them makes the real queue impossible to see.

Write a reason for keeping each item

When something goes into the backlog, ask: why would we do this, and when? If you cannot answer, it does not go in. That question alone filters out most hoarding.

Prune on a schedule

Once a month, look at the oldest items in Next Steps:

• Still relevant and ready? Leave it, or move it up
• Still relevant but vague? Rewrite it as a concrete action. See how to write an action you'll actually do
• Not touched in three months? Delete it

Deleting feels risky. It is not. Good ideas come back, usually in better form.

Do not let the backlog become a promise

Teams sometimes keep items because someone asked for them and saying no feels rude. A backlog full of polite non-commitments misleads everyone. It is kinder to say "we are not going to do this" than to let a request sit for a year. See how to say no to tasks.

Limit what enters

If items enter faster than they leave, the backlog grows without limit. Two habits help:

• Only the project owner adds to Next Steps for their row
• Every new item has to beat the weakest existing item to get in

The test

Open your backlog and read it top to bottom. If you can do that in five minutes and every item makes sense, it is healthy. If not, prune. See the problem with growing task lists and the next steps trap.