Practical guide
How to manage a growing reading backlog
Give every saved item an expiration and a purpose. Read what serves a current project, file true references, subscribe to recurring sources, and delete the speculative remainder without demanding closure.[1][2]
Why this gets difficult
A reading backlog grows because every saved item is treated as equally durable. In reality, some items support a current decision, some are references, some recur through a source, and most were merely interesting in the moment.[1][2]
A practical way through
- Sort the backlog into current decision, durable reference, recurring source, and no clear use.[1][2]
- Schedule the small current-decision set and attach each item to the work it supports.[1][2]
- Move references into the appropriate project or knowledge system with descriptive titles.[1][2]
- Delete the no-purpose set and set a shorter expiration for future saves.[1][2]
An example
The situation: A product manager has six hundred saved articles collected across jobs, launches, and past research questions.[1][2]
What changes: Only items tied to the active discovery work are scheduled, durable standards move to reference notes, and recurring publications become a curated source list.[1][2]
What you get: The backlog stops pretending to be a syllabus and becomes a small queue connected to current work.[1][2]
What to watch for
Sources worth keeping
How Scottie helps
Scottie addresses recurring sources before they become saved-item debt; selected originals remain linked for deliberate deep reading when the brief surfaces them.[3]