The biggest mistake in knowledge management is not forgetting things. It is trying to save everything and ending up unable to find anything.

Capture is the first link in the system, and also the most misunderstood. Many people confuse capturing with collecting, and that confusion is the origin of systems that are eternally full and eternally useless.

Collecting is not capturing

Collecting is accumulating without intention. It is the behaviour of someone with five hundred articles in Pocket without having read any of them, or thousands of browser bookmarks they will never visit again. There is something psychologically satisfying about saving things: it gives us the illusion of having already processed them, that that knowledge is already ours.

Capturing, on the other hand, is an intentional act. You save something because you have a concrete reason, even if provisional: “this might be useful for project X”, “this idea fits with something I was thinking”, “I want to come back to this this week”.

The difference is not in the tool you use, but in the intention behind it.

The problem with saving everything

Some people respond to the anxiety of missing out by saving everything that passes through their hands. The result is predictable: a system so full of noise that the signal is lost.

A saturated system has the same problem as a saturated mind: there is no space to think. When everything has the same weight, nothing has real weight. Searching becomes frustrating, review impossible, and maintenance so heavy a task that it is abandoned.

Fewer, well-selected entries are worth infinitely more than many impulsively captured entries.

Criteria for deciding what to capture

Before saving something, ask yourself at least one of these questions:

Does it make me think something new? If the information confirms what you already know or adds nothing to your model of the world, it is probably not worth saving.

Does it have a concrete application to something I am doing or plan to do? If you can relate the information to a current project, a question you are asking yourself, or a skill you are developing, it is a good candidate.

Would I look for it in six months? This criterion is demanding but useful. If in doubt, you probably will not need it.

Can I summarise why I am saving it in one sentence? If you cannot briefly articulate why something is worth capturing, it is a sign that you are collecting, not capturing.

Quick capture: the first level

Once you decide to capture something, the process must be as fast as possible. Friction kills habits.

The concept of the inbox is fundamental here: a single place where everything lands before being processed. It does not matter if it is an app, a notebook, a text document or a physical notepad. What matters is that there is only one, and it is immediately accessible.

Quick capture is not the moment to organise, tag or reflect deeply. It is only the moment to take the idea or information out of your head and put it somewhere safe. Organisation comes later, in a moment dedicated to that purpose.

Building the habit

Capture works when it is a habit, not when it requires conscious willpower. To build that habit, it helps to:

  • Always have the same capture point available. If you change tools depending on context, you create friction and confusion. One place, always accessible.
  • Accept imperfection. The note does not have to be perfect. Sometimes a few words that you can later expand are enough. The important thing is that it gets captured.
  • Empty the inbox regularly. If the inbox fills up without being emptied, it loses its function. A weekly review is enough to keep it operational.

In the next chapter we look at the different sources from which information arrives and how to manage each one without letting them become an endless pile.