You probably already have somewhere 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 you sent to yourself. Quick notes whose titles already tell you nothing.

At the time, it all looked useful. The article looked brilliant. The video looked important. The quote made you want to come back to it. The question looked fertile.

Then nothing.

The capture stayed where it was. It was never reread. It was never transformed. It never produced any thinking. It became a promise of knowledge, then a small mental debt, then one more item in a stockpile you no longer want to open.

The problem isn't a shortage of information. The problem is piling up interesting things without ever deciding what they become.

Capturing isn't building capital

Capturing a source isn't learning yet.

It only gives you a chance to learn later.

The distinction looks simple, but it changes everything. When you save an article, you haven't produced any knowledge yet. You've only kept a possibility open. The source is there. It might be useful one day. It might feed a line of thought, a note, an article, a decision.

But until you pick it up again, it's worth almost nothing.

A capture you never process isn't an asset. It's a stockpile. And a stockpile that grows too big ends up costing more than it returns: it takes up room, it nags at you, it makes the important things harder to find.

So capture is useful, but only as long as it stays a step. It has to set up a transformation.

The flow can be summed up like this:

1. capture;
2. distil;
3. act.

Capture keeps. Distillation transforms. Action produces.

Stop at the first level and you aren't really building capital. You're piling up.

Don't try to be too clever in the heat of the moment

The opposite temptation is to filter hard from the outset.

Before saving a source, you could ask: is this really useful? Does it line up with my projects? Am I really going to process it? Does it deserve a place in my system?

In theory, that would be clean.

In practice, it isn't so simple.

When you come across something, you're rarely in a perfectly clear-headed state. There's the thrill of the find, the surprise, the immediate interest. An idea can look very strong because it lands at the right moment. A source can look essential because it answers a question you've only just asked yourself.

That isn't necessarily a bad thing. It's often how a good lead starts.

So don't ask capture to be too clever. Demand a perfect justification at the exact moment of discovery and you risk losing sources that deserved to be picked up again.

But that doesn't mean capturing 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 the knowledge I'm building?"

That word matters: promising.

A capture isn't a validation. It puts something on hold.

Let it sit for a few days

The decision that matters isn't taken at the moment of capture. It comes later.

You have to let things sit.

A few days are usually enough. The initial momentum drops. The excitement of the new settles. The captured source becomes an ordinary object again. You can then look at it with a colder question: does it still hold?

Some captures lose their force straight away. They were appealing because they were new, well phrased, or simply well placed in the day. Three days later, they have little left to say.

Others hold. They keep pulling at your attention. They still look connected to a project, a question, an important hunch. Those may deserve to be distilled.

The delay mustn't stretch too far. Wait weeks or months and the stockpile becomes unmanageable. The following week already brings other reading, other ideas, other emergencies, other captures.

A good, simple rhythm is to work through your captures once a week.

Not to satisfy some abstract rule. Simply because it's long enough to get some perspective, and short enough not to be swamped.

Mass helps you choose

There's a paradoxical benefit to letting captures pile up for a few days: the mass becomes visible.

A single capture can always make its case. It looks interesting. It takes up little room. It might be useful.

Twenty or thirty captures tell a different story.

They show the real cost of the system. They say: keep everything and you won't have 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 along. With a cool head, looking at the list, you see more clearly what really counts.

Past 20 or 30 captures waiting, the stockpile gets hard to process. It isn't a sacred number. It's a signal. When the box overflows, don't optimise the filing. Cut.

An over-long list isn't only a problem. It's an instrument of discernment.

It makes you ask: what do I actually want to let into my thinking?

Bin it without regret

A source captured but not distilled goes in the bin.

That'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 just moved the problem somewhere less visible.

There's no point keeping a detailed record of what you rejected either. For one person's practice, tracing and processing everything ends up costing more than it brings. The system is there to help you think, not to administer your own abandonments.

Deleting a capture isn't losing knowledge.

It's protecting your capacity to process.

What isn't distilled was perhaps only a possibility. Not every possibility deserves to become work.

Capture the source, note the path

There are also two gestures that look alike but don't play the same role.

On one side, documentary capture. It keeps a complete source, or at least enough of a trace, to preserve traceability. If an article, a white paper, a video or a document deserves to be picked up again, better to keep the source than an isolated fragment.

Distillation comes afterwards.

On the other side, the personal log. Another space, another form. There you can note a question, a quote, a hunch, a remark, an idea that crosses a day. One file per month, in chronological order, does the job perfectly well.

Documentary capture follows the logic of the source.

The log follows the logic of thinking in progress.

Mixing the two usually makes the system more confusing. An important quote you run into during the day doesn't have to land in the same box as a whole article waiting to be processed. A personal question doesn't have the same shape as an external source.

Not the same place, and not the same gesture.

The goal isn't to have a good system

The trap with capture is believing the tool is the main subject.

Which tool for capturing web pages? Which app for quick notes? Which system for PDFs? Which automation on the phone? Which filing scheme? Which tag? Which database?

These questions can be useful. But they quickly become an elegant way of avoiding the real work.

The tool is a means. As with any new tool, you can be seduced by the system itself. You can spend more time improving 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 cumbersome, however elegant it is.

A simple rule

The art of capture may come down to one rule:

You capture in the heat of the moment what looks promising; you decide with a cool head what deserves to be worked on.

In the heat of the moment, don't try to be perfectly rational. Recognise what looks promising.

With a cool head, don't be sentimental. Choose.

Between the two, leave a little time. Just enough for the immediate interest to be tested against some perspective. Not enough for the box to become unmanageable.

A good capture system doesn't try to keep everything. It creates a small distance between discovery and decision.

That distance is where we stop piling things up.

And start thinking again.