Originally written in French. Translated by AI — the meaning has been preserved, not the prose.
You probably already have a place full of interesting things you'll never read.
Tabs open for three weeks. A To read folder on the desktop. Screenshots on your phone. Newsletters set aside. Links sent to yourself. Quick notes whose titles no longer tell you anything.
In the moment, everything looked useful. The article seemed brilliant. The video seemed important. The quote made you want to come back to it. The question seemed fertile.
Then nothing.
The capture stayed there. It was never reread. It was never transformed. It never produced a thought. It became a promise of knowledge, then a small mental debt, then one more item in a stock you no longer want to open.
The problem isn't a lack of information. The problem is accumulating interesting things without ever deciding what they become.
Capturing Isn't Building Capital
Capturing a source isn't yet learning.
It's only giving yourself a chance to learn later.
This distinction seems simple, but it changes everything. When you save an article, you haven't produced any knowledge yet. You've only preserved a possibility. The source is there. It might one day be useful. It might feed a line of thought, a note, an article, a decision.
But until it's picked up again, it's worth almost nothing.
An untreated capture isn't an asset. It's a stock. And a stock that grows too large ends up costing more than it returns: it takes up space, it weighs on your conscience, it makes the important things harder to find.
Capture is therefore useful, but only if it stays a step. It should set up a transformation.
The flow can be summed up like this:
- capture;
- distill;
- act.
Capture preserves. Distillation transforms. Action produces.
If you stop at the first level, you're not really building capital. You're accumulating.
Don't Try to Be Too Clever in the Heat of the Moment
The opposite temptation would be to filter very harshly from the outset.
Before saving a source, you could ask yourself: is this really useful? Is it perfectly aligned with my projects? Am I really going to work on it? Does it deserve to enter my system?
In theory, that would be clean.
In practice, it's not so simple.
At the moment you discover something, you're rarely in a perfectly lucid state. There's the thrill of the find, the surprise, the immediate interest. An idea can seem very powerful because it arrives at the right time. A source can seem essential because it answers a question you've only just asked yourself.
That's not necessarily bad. In fact, it's often how a good lead begins.
So you shouldn't ask capture to be too clever. If you demand a perfect justification at the exact moment of discovery, you risk losing sources that would have deserved to be picked up again.
But that doesn't mean you should capture everything.
The right criterion in the heat of the moment isn't: "is this interesting?"
Almost anything can become interesting if you're curious.
The right criterion is rather: "does this look genuinely promising for my projects, my thinking, or my acquisition of knowledge?"
That word matters: promising.
A capture isn't a validation. It's a holding pattern.
Let It Sit for a Few Days
The important decision isn't made at the moment of capture. It comes afterward.
You have to let it sit.
A few days are often enough. The initial momentum subsides. The excitement of novelty settles. The captured source becomes an ordinary object again. You can then look at it with a colder question: does this still hold up?
Some captures immediately lose their force. They were seductive because they were new, well phrased, or simply well placed in the day. Three days later, they no longer have much to say.
Others hold up. They keep drawing your attention. They still seem connected to a project, a question, an important intuition. Those ones may deserve to be distilled.
The delay mustn't become too long. If you wait weeks or months, the stock becomes unmanageable. The following week already brings other readings, other ideas, other emergencies, other captures.
A good, simple rhythm is to process your captures once a week.
Not to honor some abstract rule. Simply because it's long enough to gain perspective, and short enough not to be overwhelmed.
Mass Helps You Choose
There's a paradoxical advantage to letting captures accumulate for a few days: the mass becomes visible.
An isolated capture can always make its case. It looks interesting. It doesn't take up much space. It might one day be useful.
Twenty or thirty captures tell a different story.
They reveal the real cost of the system. They say: if you keep everything, you won't have the time to process it. They force you to choose.
It's often easier to cut after the fact than to filter perfectly beforehand. In the heat of the moment, you're carried by momentum. In the cold light of hindsight, facing the list, you see more clearly what really matters.
Beyond 20 to 30 captures waiting, the stock becomes hard to process. It's not a sacred number. It's a signal. When the inbox overflows, you shouldn't optimize the filing. You should cut.
A list that's too long isn't only a problem. It's an instrument of discernment.
It forces you to ask: what do I really want to let into my thinking?
The Trash Without Regret
A source that's been captured but not distilled goes in the trash.
It's brutal, but healthy.
There's no point creating a second space for "maybe later" captures. That's often how systems fill up with quiet graveyards. You haven't really deleted anything, you've only moved the problem to a less visible place.
There's no point either in keeping a detailed history of what you've rejected. For an individual practice, tracing and processing everything ends up costing more than it brings. The system exists to help you think, not to administer your own abandonments.
Deleting a capture isn't losing knowledge.
It's protecting your processing capacity.
What isn't distilled was perhaps only a possibility. Not all possibilities deserve to become work.
Capture the Source, Note the Path
You also need to distinguish two gestures that look alike but don't play the same role.
On one side, there's documentary capture. It serves to keep a complete source, or at least a sufficient trace, to preserve traceability. If an article, a white paper, a video, or a document deserves to be picked up again, it's better to keep the source rather than an isolated fragment.
Distillation will come afterward.
On the other side, there's the personal log. It's another space, another form. In it you can note a question, a quote, an intuition, a remark, an idea that crosses your mind during the day. One file per month, in chronological order, can do this job perfectly well.
Documentary capture follows a logic of source.
The log follows a logic of thinking in progress.
Mixing the two often makes the system more confused. An important quote you come across during the day doesn't necessarily need to join the same box as a whole article to be processed. A personal question doesn't have the same form as an external source.
It's not the same place, nor the same gesture.
The Goal Isn't to Have a Good System
The trap, with capture, is believing that the main subject is the tool.
Which tool for capturing web pages? Which app for quick notes? Which system for PDFs? Which automation for the phone? Which filing scheme? Which tag? Which database?
These questions can be useful. But they quickly become an elegant way to avoid the real work.
The tool is a means. As with all new tools, you can let yourself be seduced by the system itself. You can spend more time improving the capture than transforming what you capture.
The right criterion isn't: is my system complete?
The right criterion is: does it help me produce knowledge?
If the answer is no, the system is too heavy, however elegant it may be.
A Simple Rule
The art of capture may come down to a single rule:
You capture in the heat of the moment what looks promising; you decide in the cold light of hindsight what deserves to be worked on.
In the heat of the moment, you shouldn't try to be perfectly rational. You should recognize what seems promising.
In the cold light of hindsight, you shouldn't be sentimental. You should choose.
Between the two, you need to leave a little time. Just enough for the immediate interest to be tested against hindsight. Not enough for the inbox to become unmanageable.
A good capture system doesn't try to keep everything. It creates a small distance between discovery and decision.
It's in that distance that we stop accumulating.
And start thinking again.