Home › Product › Concepts
Collectors Fallacy
Product / Concepts · Added Apr 2026
Saving something is not the same as learning it.
The Idea
The collector's fallacy is the mistake of confusing gathering with understanding. Bookmarking an article, starring a repo, saving a course — each one feels like progress, but none of it is. The collection grows, the understanding doesn't. You end up with a library you've never read.
Why It Matters
- Research phases can become collection phases that never end.
- Teams hoard tools, frameworks, and reference material instead of making decisions.
- The feeling of productivity from collecting delays the harder work of thinking.
- In product work, gathering user feedback without synthesising it is the same trap.
How to Apply
- Process before you collect. Read the article before you bookmark it. If you won't read it now, you probably won't read it later.
- Set a rule: for every new thing saved, one must be processed or deleted.
- During research, timebox collection and force a synthesis step — "what did we actually learn?"
- Favour fewer, deeper sources over many shallow ones.
The Trap
Overcorrecting into never saving anything. Collections have value when they're curated and revisited. The problem isn't saving — it's saving without ever returning.
Related