The article backlog is a retrieval design bug
Article backlogs do not appear by accident. They are created by default behaviors.
When saving is frictionless and retrieval is an afterthought, the queue expands forever.
Add meaningful constraints
Good systems make postponement visible.
- Set a weekly review window.
- Define a maximum inbox size.
- Archive unread items after a fixed horizon.
Build for retrieval and reuse
You do not need to remember everything you read.
You need a small set of high-quality highlights and notes you can find and reuse quickly.
A backlog is useful only when it produces reusable source material — not when it just stores links.