There is a specific kind of busyness that feels exactly like learning: the accumulation of material, the filling of folders, the growing archive of articles saved for later, highlights exported to Readwise, PDFs filed under labels that seemed meaningful in the moment of filing. It is not learning. It is the performance of learning directed at a future self who will do the actual work — a future self who, in practice, almost never arrives.
I had, at one point, 2,300 items in my read-it-later queue.
I know this because I checked, during a period when I was attempting to bring some order to what had become an archive of accumulated intention. 2,300 articles, essays, threads, and links, collected over roughly three years, each one saved with the genuine conviction that I would return to it, that it contained something worth knowing, that the act of saving was the first step in a process of engagement that would follow shortly after.
Most of them I had forgotten I had saved. A significant portion were on topics I was no longer interested in, or had resolved in the intervening time through other reading, or were simply no longer relevant in ways I could not have anticipated when I saved them. Some were genuinely interesting, and I read a few of them during the cleanup, and they were good. But the experience of encountering them was almost identical to the experience of encountering something I had never seen before. Saving them had not brought me any closer to the ideas they contained.
What it had done, I realised, was give me the feeling of having done something with them — a feeling that was almost as satisfying as actually reading them, and that was purchased at the cost of about three seconds and a tap.
What Christian Loff Named
The phenomenon has a name. It was coined, or at least popularised, by Christian Loff in a 2014 post on zettelkasten.de, where he called it the Collector's Fallacy: the belief that collecting material on a subject is equivalent to learning about it, and the behavioural pattern that follows from that belief — the hoarding of sources, the filling of archives, the accumulation of reading lists that grow faster than they are read.
Loff was writing specifically about the habits of Zettelkasten practitioners, the note-taking system based on Niklas Luhmann's method of writing atomic notes and connecting them by reference. He observed that many people who discover the system immediately begin collecting sources to process — articles to summarise, books to note, ideas to file — and that this collecting becomes its own activity, disconnected from the processing it was supposed to precede. The Zettelkasten remains empty while the inbox fills.
The fallacy is not that collecting is useless. Collecting is a necessary first step. The fallacy is in treating it as a sufficient step — in experiencing the collection as the accomplishment rather than as the starting condition. The collector feels, at each moment of saving, that something has been done. The reading list grows; the archive expands; the folders multiply. The feeling is of increasing readiness, increasing resource, increasing preparedness for the intellectual work that is always, in this mode, about to begin.
The Zeigarnik Effect and the Premature Close
The psychological mechanism underlying the fallacy was partially described in 1927 by Bluma Zeigarnik, a Soviet psychologist who made an observation at a restaurant in Vienna. She noticed that waiters who were currently serving customers could recall the details of active orders — who had ordered what, what remained to be brought — with impressive accuracy, but that their memory of orders that had been completed and paid for was considerably worse. The uncompleted task, Zeigarnik hypothesised, maintained a kind of cognitive activation that the completed task did not. The open loop stayed alive in memory; the closed loop was released.
Subsequent research confirmed the effect and extended it: unfinished tasks occupy mental resources that finished tasks do not, and the completion of a task — or even the performance of an action that signals task completion — releases that occupation. The loop closes, the resources are freed, and the cognitive weight is lifted.
This is where the Collector's Fallacy finds its fuel. Saving an article, bookmarking a resource, filing a link into a folder — each of these actions performs task completion. The loop that was opened by encountering something interesting is closed, not by the reading and processing that the encounter was supposed to trigger, but by the act of archiving. The saving says: done. The mind registers the completion. The cognitive weight is lifted. The article joins the queue and is, for most practical purposes, finished.
This is not a character flaw. It is the mind's task-management system functioning exactly as designed in a context for which it was not designed. The system was useful for uncompleted tasks that would be physically revisited — the unfinished meal, the incomplete hunt, the project set aside for tomorrow. It is poorly calibrated for tasks that are "completed" by filing into a digital archive that the cognitive system cannot distinguish from actual completion.
The Social Dimension of Collection
The Collector's Fallacy has a dimension that the psychological accounts tend to underweight, and that I think is worth examining because it is increasingly visible in public PKM culture.
There is now a genre of content — on YouTube, on Twitter/X, on productivity podcasts — that consists almost entirely of the display of knowledge management systems. People share their Obsidian vaults, their Notion databases, their Readwise setups, their Roam research graphs. The number of nodes in the graph, the elegance of the folder structure, the density of the connections — these are the metrics by which these systems are evaluated and admired. The sophistication of the collection is the subject of the content.
What is almost never shown — what is structurally excluded by the genre — is the thinking the system is supposed to produce. The output of the Zettelkasten is not the Zettelkasten; it is the books and papers and ideas that the Zettelkasten makes possible. Luhmann's slip-box is not interesting because of the slip-box; it is interesting because of the seventy books. But the slip-box is what can be photographed and shared and admired. The books require having read and thought and written, which takes decades and produces nothing shareable during the process.
The social incentives of PKM culture, in other words, reward the collection for the same reasons that the psychological incentives do: collecting produces visible output immediately, while processing produces visible output only eventually and only if the processing succeeds. The person with an impressive Notion setup has something to show today. The person who spent today actually thinking with their notes has, today, nothing but a page of thinking that may or may not come to something.
This is not an indictment of the PKM community; the problem is structural, not personal. But it means that the cultural representations of good knowledge management systematically overweight collection and underweight processing — which reinforces exactly the confusion that the Collector's Fallacy produces. The aspiration becomes the beautiful system, not the thinking the system was supposed to enable.
The Ratio Problem
Here is an uncomfortable number: research on reading behaviour, combined with self-reported data from productivity tools like Instapaper and Pocket, consistently suggests that somewhere between five and fifteen percent of saved articles are ever read. The estimates vary by tool and user, but the general finding is stable: the overwhelming majority of material saved for later is never processed later.
This ratio has implications that go beyond the waste of time spent curating archives that will not be consulted. It means that the primary function of most read-it-later systems is not the reading of things later — it is the closing of cognitive loops opened by encountering interesting material. The system is largely a mechanism for managing the anxiety of potentially missing something, not a system for engaging with the things that are saved.
The same ratio applies, in different forms, to other collecting behaviours. Kindle highlights: how many of the passages you have highlighted have you returned to, synthesised, or used in any way? Notion databases: how many of the items in your resources folder have been opened more than once? Roam or Obsidian: how many of your fleeting notes have been processed into permanent notes, and of those permanent notes, how many have been revisited and connected?
I am not raising these questions to induce guilt — guilt is not the productive response to the Collector's Fallacy. I am raising them because the numbers reveal that what most PKM systems are actually doing is quite different from what their users believe they are doing. They are providing the infrastructure of intellectual engagement without requiring its substance. They are creating conditions under which thinking could occur, and then being used primarily to defer the occurrence.
Why More Makes Understanding Harder
There is a second mechanism at work in the Collector's Fallacy, distinct from the Zeigarnik effect, that operates at the level of the collection itself rather than at the level of individual saving decisions.
Cognitive load research — most closely associated with John Sweller's work in the 1980s and 1990s — has documented the ways in which the volume of information presented to a learner affects their capacity to process any of it. Working memory is limited, and the effort required to navigate, evaluate, and select from a large set of resources competes with the effort required to actually engage with any individual resource. A large archive is not a larger version of a small archive. It is a more cognitively expensive one.
This shows up in practice in a specific way: the larger the reading list, the harder it becomes to start reading. Not because any individual item is more difficult, but because the act of choosing which item to begin with becomes a task in itself — a task that consumes the cognitive resources that reading was supposed to use. The 2,300-item queue is not 2,300 articles I could read; it is a decision problem of 2,300 options, and the first thing it requires of me is not reading but choosing, which is exhausting in a way that reading is not.
This is the paradox at the heart of compulsive collecting: the behaviour is motivated by the desire to have more material available for learning, but the accumulation of material actively degrades the conditions under which learning can occur. The collector, surrounded by an ever-growing archive, finds it increasingly difficult to begin, increasingly paralysed by optionality, increasingly likely to save one more thing rather than engage with anything already saved.
The Substitution Problem
There is a more subtle version of the Collector's Fallacy that operates not through quantity but through category. It involves collecting information about a subject as a substitute for developing understanding of that subject — treating the archive as a proxy for competence.
I have seen this in myself most clearly in topics where I felt anxious about my ignorance. Philosophy of science was one; I spent a period saving every significant paper, every relevant SEP entry, every podcast episode and lecture and book recommendation I could find, assembling what felt like a comprehensive resource — and which served, functionally, as a way of managing the anxiety of not knowing without requiring me to actually engage with the difficulty of learning. The collection was reassuring in exactly the way that understanding would have been reassuring, and considerably easier to produce.
The distinction between collecting about a subject and developing understanding of it is not always obvious in practice, because both involve genuine engagement with material. The collector reads things. They encounter ideas. They find some interesting and some less so. The difference is in what happens after the encounter: whether the idea gets integrated into an evolving understanding, tested against prior beliefs, used to generate questions or connections — or whether it gets archived, tagged, and released from active cognitive engagement.
Understanding is always in active construction. It is not a possession; it is a process. An archive is a possession. It can be inherited, duplicated, backed up, and handed to someone else. Understanding cannot. The confusion between the two is the core of the Collector's Fallacy — the belief that by accumulating the material of learning, you have accomplished something of the same kind as the learning itself.
What Collection Is Actually For
None of this is an argument against saving, bookmarking, or maintaining a reading list. It is an argument for being clear-eyed about what collection is for, and for building the practice around that clarity rather than around the feeling that collection produces.
Collection is useful as a buffer — as the first station in a processing pipeline, not the last. The article saved is a commitment to return to it with attention, not a record of having engaged with it. The reading list is a queue, not an archive. The distinction is practical: a queue has a manageable size, a processing rate that can be compared with an input rate, and a clearing mechanism that removes items that are no longer relevant. An archive has none of these properties; it simply accumulates.
There is also a legitimate use of collection that is distinct from processing and that should not be collapsed into it: the collection of references. A bibliography is not a reading list. It is a record of sources that might be needed for a specific purpose — a paper being written, a project being undertaken — and its value lies in the specificity of the purpose rather than in the generality of the interest. A reference collected for a specific use is not in a queue to be read in full; it is in a file to be consulted when the specific use arises. This is a different relationship to material than the read-it-later relationship, and it does not generate the same psychological dynamics. The reference does not need to be processed; it needs to be findable.
The Collector's Fallacy operates specifically in the space between the reference and the processed insight — in the large middle category of material that is interesting enough to save, too interesting to discard, and not specific enough to be held as a reference. This is the material that accumulates in queues, in inboxes, in databases with promising names and growing item counts. This is the material that the fallacy converts from a processing obligation into a possession — from something that needs to be engaged with into something that has already been engaged with, sort of, in the minimal sense of having been noticed and filed.
A useful heuristic that several PKM practitioners have arrived at independently is the constraint of processing before collecting: before saving a new item, process one already saved. This does not work as a strict rule — the friction it introduces is too high for casual reading — but as an occasional practice, it forces the recognition that the queue is longer than the processing rate can manage, which is precisely the information that compulsive collecting is designed to suppress.
The deeper adjustment is a shift in the identity of the activity. The question is not "have I saved this?" but "have I engaged with this?" — and the distinction between those two questions is the distinction between the Collector's Fallacy and the practice it falsely mimics.
A Personal Reckoning
I cleared the 2,300-item queue. Not by reading everything in it — that would have taken years — but by changing the criteria. I asked, of each item, not whether it might be useful someday, but whether I intended to engage with it in the next two weeks. If the answer was no, I deleted it. If the answer was yes, I moved it to a shorter list with a specific processing date.
This was uncomfortable in the way that all genuine confrontations with accumulated avoidance are uncomfortable. Some of what I deleted I will probably need someday. Some of what I thought I would engage with in two weeks I did not. The list is longer now than it was then, and I have not yet found a system that prevents it from growing.
What I have found is the ability to distinguish, in the moment of saving, between the genuine intention to engage and the performance of that intention. The feeling is the same; the distinction is in what I do after. Collection that leads to processing is a first step. Collection that leads to more collection is the Fallacy — the comfortable, satisfying, intellectual-seeming activity that substitutes for the thing it claims to prepare you for.
The measure of a knowledge management system is not the size of its archive. It is the quality of the thinking its owner does with it. These are not correlated in the way the Collector's Fallacy assumes. They may be inversely correlated — the larger the archive, the greater the confidence that the work is being done, and the less urgently the actual work needs to begin.