CODE: capture, organise, distil, express

"Building a second brain" is Tiago Forte's name for a practice with an uncomfortable premise: most people's note-taking is a collection habit wearing the clothes of a thinking habit. You save, you tag, you file — and none of it ever comes back out.

CODE is his four-step answer, and the interesting thing about it is the weighting. Three of the steps are cheap. The fourth is the only one that produces anything, and it is the one almost everybody skips.

Capture — only what resonates

Not everything useful. Not everything true. The test Forte gives is resonance: the line that made you stop mid-page, the thing you felt before you could justify it.

It is a deliberately unserious-sounding criterion and it works, because the alternative — capturing what seems objectively useful — has no upper bound. Every article is potentially useful. Resonance is rare enough to be a filter, and it is correlated with what you will actually want later, which "useful" is not.

If you are saving things because they look important, you are hoarding. The tell is that your inbox grows faster than you can read it.

Organise — by project, not by subject

This is where PARA comes in, and the rule is one line: file by the project it serves, not the subject it is about.

A note filed under "pricing" is a note you will find when you go looking. A note filed under the project that needs it is a note you will encounter, this week, because you will be in that project. The difference between those two verbs is the difference between a system that works and one that is merely tidy.

Distil — in passes, never all at once

Every time you pass through a note, leave it slightly more usable than you found it. Bold the lines worth re-reading (⌘B / Ctrl+B). Next time, bold the best of the bold. Forte calls it progressive summarisation, and the important word is progressive: you do it when you happen to be there, not as a scheduled task.

The test of a distilled note is whether you could use it in a hurry, three months from now. Most raw captures fail that badly — not because they are wrong, but because rereading four hundred words to find the one that mattered costs more than looking it up again.

Doing this in one big session does not work. You cannot tell which line matters until you have needed the note at least once.

Express — make the thing

Notes that never leave the box were a hobby. Pleasant, and not what you told yourself you were doing.

Expressing does not mean publishing. A memo, a decision, a recommendation to a colleague, a paragraph in a document that goes to two people — anything that turns accumulated notes into something with an audience. The habit is weekly and small, not occasional and grand.

This step is also the only real quality control on the other three. Nothing exposes a badly captured, badly filed, undistilled note like needing it under time pressure.

Mapped onto an outline

Four branches, in order, because CODE is a pipeline rather than four categories:

• Capture — the inbox. Fast, unsorted, emptied.
• Organise — by project. In practice this branch is a pointer at your PARA Projects, not a second copy of them.
• Distil — where notes get re-read and bolded. Nesting does part of the distilling for free: the summary line is the parent, the detail is folded underneath it, and ⌘↑ / Ctrl+↑ is the reading view.
• Express — what you are making out of all of it. Keep this branch visible. A second brain with an empty Express branch is a library.

• Second brain — CODETiago Forte's four steps. The fourth is the one people skip, and the only one that produces anything.
  • CaptureOnly what resonates. If you are collecting because it looks useful, you are hoarding.
    • The line that stopped you mid-page
  • OrganiseBy the project it serves, not by the subject it is about — this is where PARA comes in.
    • Which project is this for?
  • DistilRe-read and bold the lines worth re-reading (⌘B). Do it every time you pass through, never all at once.
    • A note you have distilled twice can be read in ten secondsThat is the test: could you use this note in a hurry, three months from now?
  • ExpressMake the thing. A post, a memo, a decision — notes that never leave the box were a hobby.
    • What I am making out of all this
  • How to run it

Folded bullets open with a click; every line is yours to rename or delete. Open it →

How to run it

Capture in seconds, throughout the day. Organise weekly, when you review. Distil whenever you happen to open a note, never on a schedule. Express once a week, something small.

Never capture and distil in the same sitting — the first wants speed and no judgement, the second wants judgement and no speed, and doing both at once produces a slow inbox and shallow notes.

What to skip

Skip the taxonomy. If you cannot name the project a note serves, it goes in Resources and you move on; a subject tree is what you build when you are avoiding the question.

And skip the idea that the system needs to be finished before it is useful. Capture and Express alone, with the middle two done badly, still beats a beautifully organised archive nobody reads.