Building a Second Brain by Tiago Forte: CODE method

You are drowning in information. Every day brings new articles, emails, videos, podcasts, and ideas. You save some. You forget most. None of it connects to anything you actually do.

This is the second brain problem. Your first brain is excellent at thinking, creating, and deciding. It is terrible at storing and organizing information. The solution is not to store less information. It is to build a system that captures what matters, organizes it so you find it again, and connects it so it compounds into something useful.

Tiago Forte's Building a Second Brain introduced the CODE method, a practical framework for turning digital chaos into a working system. CODE stands for Capture, Organize, Distill, and Express. This is not a note-taking technique. It is an information architecture that transforms how you learn and create.

What is the CODE method and why does it work?

The CODE method is a four-stage process for managing information from capture to output. Instead of saving everything in hopes you will need it later, CODE ensures every piece of information flows through a system that makes it progressively more useful.

Capture means saving information that resonates. Organize means grouping it by how you will use it. Distill means clarifying what matters most. Express means turning information into action, output, or creation. The system works because each stage removes friction between your curiosity and your action.

Most people collect information with no end goal. They read articles and save them. They watch videos and take notes. Then they never see those notes again. CODE requires you to work backward. Before you capture, think about how you will use this. Before you organize, ask what project needs it. Before you distill, decide what action it enables. Before you express, make sure it connects to something you are building.

How to capture information you actually need

Capture is the first and most important stage. It is the decision of what enters your system. The goal is not to capture everything. It is to capture only what resonates, what connects to your work, and what answers a question you are holding.

When you read an article, does a sentence jump out? Capture it. When someone shares an idea that conflicts with something you believe, capture the tension. When you stumble on a tool or framework that might solve a problem you have been thinking about, capture it with a note about why it matters.

This sounds simple. In practice, capture is about training your attention. Most people capture too much. They become note hoarders. You capture the right amount when your notes are small, specific, and tied to something you care about. One powerful quote beats ten articles saved without context.

Capture happens in the moment. You are reading an article on a website. You are watching a video and hear something useful. You are in a conversation and someone says something true. You need to be able to capture without friction. This means having a single inbox for everything. Email, notes, a voice memo app, a browser extension, a physical notebook. Everything flows into one place first. Then you organize from there.

The wrong approach is to carefully organize as you capture. This breaks your focus. The right approach is to capture fast and organize later.

How to organize information by use, not by topic

Most people organize notes by topic. They create folders: Business, Health, Learning, Finance. This feels logical. It fails in practice because you do not retrieve information by topic. You retrieve it when you need it for a project, a decision, or a problem you are solving.

CODE uses project-based organization. Create a folder for each active project. Inside that folder, collect all information related to that project, regardless of the topic. An article on marketing research, a template from a competitor, a screenshot from Twitter, a book excerpt on customer psychology. All in one place because they all serve the same project.

Supporting this is a "reference" folder for evergreen information: techniques you reuse, frameworks that cross multiple projects, examples you return to. This is smaller and more durable than project folders, which are temporary.

The organizing principle is usability. Can you find this information when you need it? If the answer is no, you need a new structure. This means tags become powerful. A single note can be tagged with three projects plus two reference topics. It surfaces everywhere you need it without being duplicated.

Tools matter less than the structure. A folder structure in Notion, a tag system in Obsidian, a project-based setup in a note app. The method works in any system that lets you organize by use.

How to distill notes into insight

Distillation is compression. It is taking a 3,000 word article and extracting the 3 sentences that matter.

Most people either skip distillation or over-distill. They read an article once and highlight everything. Or they read it once and remember nothing. Distillation happens in layers. The first layer is marking the most important idea as you read. The second layer, later, is summarizing that idea in your own words. The third layer, much later, is connecting it to something else you know.

The goal of distillation is not to shrink notes. It is to make them more useful. A 50 word distilled version of a 2,000 word article is exponentially more useful because you will actually read it. And because it is in your own words, it feels more like your thinking, not someone else's.

Distillation also clarifies which information is temporary and which is structural. A quote from an article might be perfect for a presentation you are giving next month. It has a short shelf life. A framework for thinking about customer research has value for years. It deserves to be refined, expanded, and revisited.

This is where most knowledge systems fail. They capture and organize. They never distill. The information accumulates and becomes less useful because you have too much and cannot find the signal.

How to express what you have learned

Expression is the purpose of the entire system. It is why you capture, organize, and distill. It is the moment you turn information into output.

Expression can be writing. A blog post, a memo, a proposal, a book. It can be teaching. A conversation where you share what you learned. A presentation. A workshop. It can be building. A project, a product, a system that reflects what you now know.

Without expression, your notes are just consumption. With expression, they become leverage. One good idea expressed as a blog post reaches a hundred people. One framework expressed as a project template saves your team hours of work.

Expression also forces honesty. When you try to write or teach what you learned, you discover what you actually understand and what you only thought you understood. This is valuable feedback. It tells you which notes to distill further and which are already integrated into how you think.

How EveryOS helps you build a second brain

The CODE method works only when captured information flows into action. EveryOS connects all four stages of the CODE method into one operating system, turning passive notes into an engine for compounding progress.

Capture and Organize. The notes module is your capture inbox. Write in Markdown. Create folders to organize by project. Tag everything so information surfaces in multiple contexts. Star what matters most. Unlike standalone note apps, your captured information does not sit in isolation. Every note lives within the context of the systems it supports.

Distill through Skills. When you capture a learning resource, log it directly in your skill tracker. EveryOS records the resource, tracks your learning sessions, measures hours invested, and shows completion progress. This forced act of linking the resource to a skill is distillation in practice. You are deciding how this information matters.

Express through Projects. Save an article idea related to a project, and link it in the notes. That note becomes available in the project context. As you work on the project, you revisit, refine, and reference the captured ideas. Expression happens when you turn those notes into tasks, milestones, and completed work. EveryOS surfaces your notes exactly when you need them because they are connected to the projects that use them.

Connect to Goals. When a captured habit or principle becomes a daily ritual, it connects upward to your goal. A learning resource feeds into a skill. A skill contributes to a goal. A goal manifests as a project. A project breaks down into daily tasks. The second brain stops being a silo. It becomes an integrated system where information compounds.

Put it into practice

Here is a concrete example of building a second brain in EveryOS:

  1. You read an article on user research methods that resonates. Capture it as a note with the title "Five interview techniques for product research." Tag it with "research-methods" and "customer-discovery."

  2. You are working on a project to launch a new product feature. Link the captured note to that project. In the project view, your research article is now contextually available, not buried in a notes archive.

  3. Create a skill track called "User Research" in EveryOS. Log the article as a learning resource. Estimate it will take 30 minutes to digest. When you read it and apply the techniques in your interviews, log that as a learning session. The skill now shows your investment and progress.

  4. After conducting interviews, create tasks for each insight discovered. Tag those tasks with the project. The insights from your captured notes now drive action.

  5. Complete the project. EveryOS shows you how many learning resources you consumed, how many hours you invested in the skill, and how many tasks you completed. The information you captured became directly measurable progress.

Over time, your notes do not accumulate as clutter. They transform into documented learning that compounds your skills and ships your projects.

Start building your second brain

EveryOS free plan includes the core features for building a second brain: unlimited notes with folders and tags, unlimited tasks linked to projects, 5 habit tracks, and 3 skill tracks. Capture, organize, distill, and express everything you are learning and building. Get started for free at EvyOS.

FAQ

How much should I capture? Only what resonates or answers a question you are holding. Quality over quantity. One genuinely useful note beats ten vague ones saved on impulse.

What if I never distill my notes? You will accumulate a growing archive that becomes less useful over time. Distillation is where capture becomes knowledge. Without it, you just have a storage system.

Should I organize by project or by topic? Start with project organization for active work. Build a reference folder for evergreen information that spans multiple projects. Tag everything so it surfaces in multiple contexts.

How long should a distilled note be? Short enough to re-read in 2 to 3 minutes. Long enough to be useful without re-reading the original. Aim for 50 to 200 words depending on the complexity of the original.

Key takeaways