Second brain: a simple system for using what you save

What is a second brain?

Think of a second brain as a trusted working collection, not a second mind making decisions for you. You record something useful, keep its source, add enough context to understand it later and retrieve it when needed. The system can be modest: a notebook and card index, a notes folder, or a digital workspace. The name describes a practice of externalizing information, not a biological or medical claim.

Tiago Forte’s book Building a Second Brain was published in 2022; the Digital Downloads Ohio library record dates the audiobook to June 14 of that year. The publisher’s description presents the approach as personal knowledge management using an organized digital repository. Forte’s CODE and PARA frameworks are his named approaches, not generic features every notes app automatically provides.

For this guide, the wider working idea includes paper and hybrid setups as well as digital ones. Keep that distinction clear: Forte describes a digital system; the broader habit of preserving and retrieving useful material need not begin with software. You still decide what belongs, whether a source is reliable and what conclusions the material supports.

Building a second brain with Forte’s CODE framework

In his introductory guide, Forte names four stages: Capture, Organize, Distill and Express. The following descriptions summarize those stages in our own words. They are a workflow for moving information toward use, not a requirement to complete a formal checklist for every small note.

Capture

Keep material worth returning to: a relevant passage, an observation, an image or an idea. Preserve its origin and add why it matters. Saving everything you encounter makes the later stages harder.

Organize

Give material a place based on how you expect to use it, especially in current work. A clear project name is often a more useful return path than a broad category such as “Interesting things.”

Distill

Make the useful part easier to see through a short summary or selected highlights. Keep the original source and context available; compression should not erase a condition or change a claim.

Express

Use what you kept in something tangible: a draft, explanation, comparison, drawing study or decision. The collection supports this work rather than replacing it.

Imagine a fictional essay about sheltered public spaces. Capture a relevant source with a page reference, organize it under that essay, write a short note about what it actually supports, then use it in a draft with appropriate attribution. If it does not support your argument, keep the disagreement or leave it out. The point of the framework is not to make every saved item fit a conclusion.

PARA: four places for different kinds of material

Forte’s PARA method groups information into Projects, Areas, Resources and Archives. CODE describes what you do with information; PARA describes where it can live. You can use one framework without treating the other as a rigid filing rule.

Projects

Work directed toward a particular outcome, such as drafting the sheltered-spaces essay or preparing a small exhibition. Keep the material you need for that outcome together.

Areas

Ongoing responsibilities without a single finish line, such as maintaining your personal research practice. Do not turn every continuing responsibility into a project with an artificial completion date.

Resources

Topics or interests that may inform future work, such as garden design or bookbinding. Keep this material distinct from what the current project actually needs.

Archives

Inactive material from the other categories. Move a finished essay project here so its sources remain available without crowding the active workspace.

An item’s place can change. A general note about shelter may begin as a resource, become relevant to an essay project and remain useful after that essay is archived. Prefer a clear reference or link where your tool supports it instead of creating several copies you will have to update separately. The classification serves retrieval; it is not an exam with one correct answer for every note.

Commonplace books and Zettelkasten: alternatives and ancestors

A commonplace book collects selected passages, observations and ideas under headings or an index. That practice predates contemporary digital systems: Michael Stolberg’s history of commonplacing describes early modern collections used for excerpts and observations. The second-brain label is newer than the underlying problem of keeping worthwhile material retrievable.

A Zettelkasten emphasizes separate, connected notes that can develop ideas across projects. Niklas Luhmann’s note box is a documented historical example; Bielefeld University’s archive describes his network-organized collection as a central tool of his theoretical work. You do not need to reproduce his scale or exact organization to try linking a few useful notes.

These approaches overlap without being interchangeable. Commonplacing can suit a selected reading collection; linked notes can suit ongoing argument development; project-centered organization can suit finding material for a current output. They are related practices, not evidence that Forte copied one specific historical system. Choose the emphasis that matches your work and borrow only what helps.

Live capture is a separate decision. Compare note taking methods if lectures, reading sessions or meetings are producing the raw material. A second brain does not require carefully linking every sentence while someone is speaking.

Make a visual second brain on a canvas

A visual workspace gives a project an inspectable arrangement: the question in one area, source material nearby, your interpretations in another, and the intended output where you can see it. Use space to make distinctions, not simply to display everything you have saved. A small board of relevant material is often easier to work through than a panoramic archive.

1. Set the question: write the project’s purpose and what you are trying to produce.
2. Keep source cards: place relevant excerpts, images or links with their origin and page or timestamp.
3. Separate your thinking: write summaries, disagreements and uncertainties on distinct notes.
4. Explain relationships: connect items only when you can say how they support, challenge or extend one another.
5. Leave an output area: put a draft outline, comparison or next step beside the material it uses.

For the fictional essay, one group could compare descriptions of shelter, another could hold conflicting accounts, and a separate note could state what remains unanswered. A connection means only the relationship you explain. Two items being close together does not establish that they share a cause or that one verifies the other.

Canvas Perch supports images, notes, links and files side by side, with frames and connections for spatial arrangement. Its personal knowledge page describes keeping your own words with a path to the source, while search covers finding notes and library material again. The canvas is a working surface, not a system that decides which ideas are true.

Keep notes that survive retrieval

A system becomes trustworthy through ordinary maintenance, not because you give it a reassuring name. Make each useful note understandable outside its original moment. A link labeled “read this” may fail that test; a title naming the claim or question gives you a better route back. Keep a stable original file or source record where the material matters to your work.

• Title: a specific idea or question you can recognize later.
• Content: the excerpt, observation or explanation, with copied wording clearly marked.
• Origin: author or creator, title, original link or file, date when available and page or timestamp.
• Relevance: why you kept it and which project or interest might use it.
• Status: what is confirmed by the source, what is your interpretation and what still needs checking.

Before relying on a tool, try finding a note from its title, correcting a source and keeping a copy outside the tool. Check backup and export options, access controls and whether your chosen format remains useful without the app. Do not save confidential material simply because capture is easy. Keep only the personal detail the project actually requires.

Distillation also needs care. A short summary should retain the conditions and limits that matter. If the source says a result applies to one setting, your summary should not turn it into a claim about every setting. Keep disagreements rather than smoothing them away to make the collection look consistent.

Avoid collecting without using and other traps

The most obvious failure is an inbox that grows while your work does not change. Resist treating the number of saved items as progress. Name an output before expanding the collection, and return to an older note before saving another similar one. You may need fewer sources, a more specific question or a different capture habit—not a more elaborate system.

Overdesigning the structure

If you spend each session renaming folders and polishing templates, return to one project and one clear output. Let new categories earn their place through actual use.

Keeping only highlights

A highlight can lose its surrounding argument. Add a source location and your own account of the context before treating it as reusable evidence.

Linking everything

A dense web of unexplained connections is hard to inspect. Add a sentence about the relationship or leave the notes unconnected.

Splitting the same material everywhere

Choose an authoritative home for the note and a deliberate backup. Avoid competing copies whose sources and summaries diverge.

If your problem is mostly a bookmark backlog, from bookmarks to ideas offers a smaller starting move: add the reason for saving, group around a live question and promote only the useful few. You do not need to migrate your whole history before beginning a better practice.

A first-week second brain setup

This is a suggested seven-day trial, not a required schedule or a promise of productivity. Keep your existing archive intact and work with a small sample. The aim is to complete the capture-to-use loop once, then decide which parts deserve to become habits.

1. Day 1: choose one real project and state its output. Pick one capture place and one authoritative home for its material.
2. Day 2: save a few relevant sources or observations. Add full source details and one sentence about why each belongs.
3. Day 3: group the material around the project’s question. If PARA helps, create only the categories you currently need.
4. Day 4: summarize the useful part of each selected item in your own words. Keep the originals and important qualifications available.
5. Day 5: retrieve something without browsing the entire collection. Improve the title or index if the route back is unclear.
6. Day 6: use a note in a draft, explanation, study or decision. Check the original before attributing a claim or reproducing material.
7. Day 7: review what actually helped. Set a modest recurring review time and remove organizational steps you did not need.

At the end of the trial, ask whether you can explain a saved idea, locate its source and point to something it informed. Those are more useful observations than a large inbox or a polished dashboard. Keep the parts that make your next session easier and leave the rest out.