DEV Community

Mejzun
Mejzun

Posted on

Your game backlog is not a to-do list. Stop treating it like one.

In 129 real game backlogs, 84% of games never leave "Backlog". Maybe the list is doing a different job than you think.

You will never finish your game backlog, and the data says that's fine. I run a free game backlog tracker and looked at 129 real accounts (25,276 games, 2026-11-10): 84% of games are still marked Backlog, 11.5% are Done. The median backlog is 64 games and would take about 1,091 hours.

A to-do list is supposed to reach zero. A backlog doesn't, and it was never going to.

What the list is actually doing

  • It is a menu, not a queue. You don't read a whole restaurant menu before ordering.
  • It is a memory aid: "I wanted to play this" is worth saving even if you never do.
  • It is a wishlist with a receipt: 44% of Steam games in these backlogs have 0 minutes played.

Where the guilt comes from
You feel behind only if the number is a deadline. Mean backlog is 196 games, median 64, p90 537, max 2,690. The few huge libraries pull the average up and make everyone else feel small.

What to track instead

  1. How many games you started this month.
  2. How many you moved to Done or Dropped (3% of games are Dropped; most backlogs never use it).
  3. The five you want to play next. In these backlogs only 113 games out of 25k are marked high priority.

Tracking the size of the pile is the one number that always looks bad. Track movement.

Do you count your backlog, or do you ignore it on purpose?

Top comments (1)

Collapse
 
jes_p_d4f61f7aa2ec405a418 profile image
Dev_PJS •

The menu/queue distinction is one I enforce with real machinery on the work side, and your data is the mirror image of why. My agent task queues have a hard rule: an item leaves only when a completion, closure, or postponement decision is recorded against it — never by silent omission during a reshuffle. We lost a contest entry that way once; it sat in the queue, got quietly dropped across six list updates, and stayed ownerless for 38 hours. But the opposite error is just as real: my idea pool is a menu, hundreds of entries, and the week I started reporting 'pool completion rate' it turned into a guilt instrument and the entries got worse — people (and agents) pad queues they are graded on clearing. Queues are promises and must drain or be formally discharged. Menus are memory and must not. Most backlog pain is one list being graded by the other's rules.