In 1962, NASA engineer Howard McCurdy faced a problem that had nothing to do with rockets. The agency was drowning in technical reports - thousands of pages generated each week across dozens of contractors. Engineers were spending more time searching for information they knew existed than solving new problems. McCurdy's solution was not a better filing system. It was a ruthless upstream filter: before any document entered the knowledge base, someone had to answer one question. "Will someone need this in six months?" If the answer was uncertain, the document did not go in.
Information capture has the same upstream problem, and you are probably skipping the filter entirely.
Most people treat capture as a reflex. Something looks interesting, you save it. A speaker says something clever, you highlight it. A thought arrives during a meeting, you jot it in whatever app is open. The result is a system that looks productive from the outside - full notebooks, a bloated read-later queue, dozens of highlights per book - and is functionally useless. You are not building a knowledge base. You are building a pile.
The cost of undiscriminating capture
There is a real psychological cost to saving everything. Every item you capture creates an implicit commitment: at some point, you have told yourself, this will be useful. The more you save without filtering, the larger that implicit debt grows. Eventually the debt becomes so large that the entire system feels overwhelming, and you stop engaging with it at all. Your notes folder becomes a place you add to but never visit - a graveyard of good intentions.
Researchers who study information overload call this the paradox of hoarding: the more you save, the harder it becomes to find anything, which means the value of each saved item decreases even as the total volume grows. You end up with more information and less access to it.
The fix is not a better app. It is a decision layer that runs before capture.
The three questions worth asking
Before you capture anything - an article, a quote, a meeting note, a shower thought - run it through three quick filters.
First: Is this surprising or does it contradict something I already believe? Information that confirms what you already know has low marginal value. Information that challenges or extends your mental models is worth keeping. If a piece of content just tells you what you already think, the main thing you gain from saving it is a feeling of validation, not a new capability.
Second: Is there a specific context where I would use this? Not "this is interesting in general," but "this applies to the project I'm working on" or "this would help me in conversations about X." If you cannot name a concrete use case, the item is probably not worth capturing. Generically interesting material fills your system without ever improving your thinking in a measurable way.
Third: Would I be able to reconstruct the core idea in my own words right now? If you cannot summarize what you just read in two sentences, you have not understood it well enough to capture it usefully. Saving something you do not yet understand is just outsourcing the thinking you should do now to a future version of yourself who will be equally confused.
Two out of three is enough. An item that clears two of these filters is worth capturing. An item that clears zero or one probably is not, even if it feels important in the moment.
Key Point: The problem with most capture systems is not the system - it is the absence of a filter that runs before capture. Every item that enters your notes is an implicit commitment to future attention. Filter ruthlessly upstream, and the whole system becomes lighter and more useful.
What gets past the filter
Once you have a filter, you also need a single place for raw captures - not the final resting place, just the intake. A physical notebook, one inbox app, a voice memo folder. The specific tool does not matter much. What matters is that there is one and only one front door. Multiple entry points create the same problem as no filter: you end up with information scattered across surfaces you will never reconcile.
The intake is not meant to be organized. It is meant to be complete. You will process it - or not - in a separate step. But if you are dumping raw thoughts into five different apps depending on where you are and what device you have open, you have already lost before you start.
Think of the intake as an in-tray on a physical desk. You throw everything incoming into the tray, and at a scheduled time you sort it. You do not sort while things are arriving. You do not have seventeen in-trays. One tray, one scheduled sort.