Building a Second Brain Summary: CODE and PARA in Practice
Tiago Forte’s book explains how saved knowledge can support real output. This summary separates its main methods and gives you a small way to try them.
Updated 6 min read
Building a Second Brain, by Tiago Forte, describes a way to save useful knowledge and turn it into work you can share. Its main methods are CODE, a process for using information, and PARA, a way to organize it around practical needs. For AI-assisted projects, fenbs can keep current decisions and progress alongside the personal notes you maintain elsewhere.
This is a concise explanation of the methods followed by an original project example. The author’s book page (opens in a new tab) provides the full book and its context. A summary can help you choose a starting point; applying the ideas requires noticing where your own information habits break down.
What is the book’s central idea?
The central idea is to make selected knowledge available beyond the moment you first encounter it. A saved idea becomes useful when you can find it again, understand why you kept it, and use it toward a result. The book treats digital notes as material for thinking and creating.
Consider the difference between collecting advice about presentations and preparing an actual talk. You may have dozens of saved links, yet still struggle to choose an opening example. That suggests a practical question for your collection: can you retrieve something relevant to the audience and explain why it belongs in this talk?
The general second brain introduction covers the wider concept. For this book, the useful distinction is between a process for handling information and the places where you keep it. CODE and PARA answer those two different needs.
What do the four CODE steps mean?
Forte introduces CODE in his overview of the method (opens in a new tab). The letters stand for Capture, Organize, Distill, and Express. In plain terms, they describe saving selected material, putting it somewhere useful, making its important meaning easier to see, and using it to produce something.
| Step | What you do in the example |
|---|---|
| Capture | Save a relevant survey and a note explaining which proposal question it may answer. |
| Organize | Place the note where you will look while preparing the workshop proposal. |
| Distill | Write the key finding and its limitation above the longer reading notes. |
| Express | Use that checked finding in a draft argument for the workshop schedule. |
The example gives you a test for every step. If you cannot explain why the survey matters, capture needs more thought. If you cannot find it while drafting, organization needs attention. If the draft overstates the survey, return to the source rather than polishing the wording around a weak claim.
How does PARA relate to CODE?
PARA supplies four broad categories for saved information: Projects, Areas, Resources, and Archives. Forte’s PARA explanation (opens in a new tab) distinguishes work with a defined outcome from ongoing responsibilities, topic material, and inactive information. CODE describes what you do with information; PARA helps you decide where it belongs.
| Category | Meaning | Example |
|---|---|---|
| Projects | Current efforts with a particular outcome | Prepare the workshop proposal |
| Areas | Responsibilities that continue over time | Volunteer coordination |
| Resources | Information kept around an interest or topic | Examples of accessible workshop formats |
| Archives | Inactive material retained for later reference | The completed workshop proposal |
In the example, the proposal has a finish line while volunteer coordination continues after the proposal is done. A reference note about room layouts could support several future proposals. Decide which version is the source of truth and link to it rather than creating competing copies in every project.
You do not need to reorganize years of material to test this distinction. Choose the notes for one current deliverable, give them a clear home, and see whether drafting becomes easier. Move older material when a real use brings it back into view.
What does distilling a note change?
Forte’s Progressive Summarization explanation (opens in a new tab) describes adding layers of emphasis and summary so the important parts of a note are easier to rediscover. The purpose is to help your future self understand a note without rereading everything each time. Preserve the underlying material so the shorter version can be checked.
For the workshop example, put a short statement at the top: “Respondents preferred evening sessions, but the survey did not ask about transportation.” Under it, keep the exact source location and your fuller reasoning. That limitation matters if someone later tries to use the preference as proof that an evening venue is accessible.
A useful summary answers a particular question. If you cannot name the question, writing an elaborate abstract may create more reading rather than less. Revise the note when using it exposes an ambiguity, and keep your interpretation distinguishable from the source’s actual finding.
How can you apply the methods to one real project?
Choose a deliverable you already owe someone. In the workshop example, the deliverable is a short recommendation for the coordinator. Your first collection can be small: the application requirements, one survey, notes from a venue discussion, and a list of unanswered questions.
- Write the output first: a recommendation that states the proposed schedule, the supporting evidence, and the unresolved venue question.
- Gather only the source material needed for those claims. Put a reason for keeping each item beside its reference.
- Prepare a short working outline. Add the strongest checked evidence and a limitation beneath each claim.
- Draft the recommendation, then compare its factual statements against the sources. Return unanswered questions to the working list.
This application exercise also reveals whether your setup serves the work. If the source is easy to find but the coordinator’s choice is missing, another folder will not settle that choice. Record the approval and its reason separately. fenbs keeps Decisions and rules with the active project for that part of the workflow.
What does an AI assistant need beyond personal notes?
A note archive may contain every option you considered. An assistant continuing the project needs to know which option a person approved and what remains unfinished. Treat this as an additional work record, not a request to rewrite your whole note collection around AI.
The AI second brain guide explains how assistants use saved knowledge; the AI brain guide focuses on reusable work context. In the workshop example, selected context should say that the coordinator chose evenings, transportation is still unresolved, and the next task is to check the venue.
Keep the working answer beside your source notes
Use your personal notes for reading and developing ideas, then put the project’s current goal, selected references, and approved choices in fenbs. A connected assistant can read that record before helping with the next draft. Save where the work stopped so another session can continue without interpreting every old option as current.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account and add one project tied to a deliverable. fenbs is free for one person, no credit card.
- Add the current tasks and an AI context note describing the goal. Save selected source references in Links and listings while keeping longer reading notes in your notes system.
- Record what a person chose in Decisions and rules, including who decided. Keep a proposal open until a person makes the choice.
- Connect a supported assistant through the integration guides. Ask it to read the project context before work and save progress, remaining questions, and the next step afterward.
fenbs is not the right fit when your only requirement is a personal notebook for long reading notes. It keeps active work context and does not automatically import that notebook. Try the smallest useful record and inspect whether a fresh assistant session can correctly explain what is settled and what is next.
Explore the second brain collection when you need a specific tool setup. The practical outcome to seek is modest: one source you can find, one argument you can check, and one next step you can resume.