Research note
Why saving more doesn't make you more organized
Saving something produces a small, immediate feeling of having dealt with it. The cost of that save, the searching, scrolling and failing later, arrives months afterwards and is never attributed to the original act.
That's a reward structure that reliably produces overcapture.
01 · The loop
Immediate reward, deferred and invisible cost.
Bookmarking an article closes the loop your curiosity opened, which is why it feels like reading. The article remains unread, but the discomfort is gone.
Because the cost never gets connected back to the cause, nothing corrects the behaviour. The pile grows, and each addition makes every retrieval slightly worse.
Capture pays now. Retrieval pays later, and nobody sends you the bill.
02 · Signal loss
Volume dilutes the things that mattered.
In a hundred saves, the important ones are visible. In four thousand, they're statistically invisible, and there's no marker distinguishing the thing that changed your mind from the thing you glanced at.
Most tools record no engagement signal at all, so ten seconds and two hours of attention are stored identically.
- No weighting
- A skim and a deep read look the same in the archive.
- No decay
- Nothing loses prominence with age or irrelevance.
- No revisit signal
- The things you return to aren't treated differently.
03 · Breaking it
Don't save less. Make the archive able to speak.
Advice to be more selective misreads the problem: you can't know at save time what will matter. Selectivity throws away the thing whose value only appears later.
The workable move is to raise the quality of what's recorded per save, content, moment, description, connections, so volume stops being the enemy, and to let old material resurface so the archive stops being write-only.
If this idea interested you…
Shelf V3 is out now
Shelf V3 is the current build. Shelf does not use automatic updates, so download the latest build here and install it over your current version.
This is intentional. Shelf is built around a local-first, privacy-focused philosophy. An automatic updater requires additional background processes, network connections, update infrastructure, and another system with permission to modify the app. We prefer to keep Shelf’s network footprint and background activity as small as possible.
Manual updates keep the process explicit: Shelf only checks the internet when a feature actually needs it, and you decide when a new version is downloaded and installed.