What is a second brain? It is a store outside your head for the things you will need later and cannot reliably keep: the link, the quote, the address, the half-formed idea, the PDF the bank sent in March. Tiago Forte, who named the idea, defines it as "an external, centralized, digital repository for the things you learn and the resources from which they come". The word "brain" oversells it a little. A better mental picture is a workshop bench where the tool you need is already lying next to the job.
The reason it has a name at all is that most people already have one, badly: spread across a notes app, a bookmark bar, a self-sent chat thread and a downloads folder, none of which knows the others exist.
What actually goes into one
The test is not how much it holds. It is whether the thing you saved is standing next to the work it belongs to when the work comes up. Almost every leak is a filing problem rather than a memory problem.
| what you needed to keep | where it usually ends up | what it costs when the moment comes |
|---|---|---|
| a link somebody sent you | a browser tab, then a bookmark bar with 400 siblings | you remember it exists but not the words to search for |
| a screenshot of a booking code | the camera roll, between two photos of a dog | four minutes of scrolling while somebody waits |
| a PDF from an insurer | the downloads folder, named doc_final_2.pdf | you open five files before the right one |
| a phone number from a message | the message thread it arrived in | you search a chat app by half-remembered name |
| a decision you made and why | nowhere at all | you re-argue it with yourself six months later |
| an idea for a project | a note called "notes" | it is never read again, which is the same as never written |
Look down that middle column. Every one of those destinations is a fine place to receive something and a terrible place to keep it. The receiving place is optimised for the moment of arrival; the keeping place has to be optimised for a moment you cannot predict.
The four moves that make it work
Forte's method compresses to four verbs: capture, organise, distill, express. Capture is saving what resonates without stopping to judge it. Organise is filing by how actionable a thing is rather than by subject — the idea behind the PARA method, which sorts everything into projects, areas, resources and archives. Distill is boiling a saved thing down so a future you can use it in ten seconds instead of ten minutes. Express is the step everyone skips: producing something with the material, which is the only proof the rest worked.
Balance matters more than order. A second brain that is all capture becomes a landfill. One that is all organising becomes a hobby.
The failure everyone hits is collecting
The people who write about this call it the collector's fallacy, and Christian Tietze's essay of that name puts it bluntly: knowing about a thing is not knowing it, and until you have merged the material into your own thinking you have not learned anything. Saving an article feels like reading it, and filing a PDF feels like handling the problem. Both feelings are counterfeit and free, so the habit spreads.
There is a cheap test. Pick three things you saved last month and ask what each one was for. If you cannot name the project, the decision or the person it belongs to, you did not capture it — you deferred it. Two of three failing is normal on a first attempt.
The fix is not discipline. It is making the filing decision cheap enough to make at capture time, which usually means one question: which live thing does this belong to? Nothing is a legitimate answer, and that item goes to a resources shelf or straight into the bin.
How to run a second brain for one week
Seven days is enough to find out whether you have a capture problem, a filing problem, or neither.
- Pick one app you already pay for or already have open. Do not shop. Switching apps mid-trial destroys the evidence.
- Make the inbox reachable in under three seconds — a share sheet, a keyboard shortcut, a pinned window, whatever is fastest on the device you actually hold.
- For seven days, capture anything you catch yourself trying to remember. Links, photos of parking bays, the plumber's name, the sentence you liked. No sorting while you capture.
- Do not read anything you saved until day four. Reading during collection turns the trial into a browsing session.
- On day four, spend fifteen minutes filing. Every item gets a home next to a live project, a home on a reference shelf, or the bin. Count how many hit the bin.
- On day seven, take two numbers: how many items you captured, and how many you reached for again. The second is usually one or two, and that is fine — a second brain is insurance, priced per use.
- Write down where the friction was. Slow capture means the app is wrong. Slow filing means the structure is wrong. Nothing coming back out means you never look, and no app fixes that.
Most people finish that week with forty to eighty items and a clear idea which of the three problems they have.
Do you need one?
Honestly, not everybody does. If your work is repetitive, your commitments fit on one screen and nothing you handle has a paper trail, a second brain is overhead you will abandon in a fortnight.
You probably do need one if any of this is familiar: you have re-found the same document twice; you keep a chat thread with yourself; a project stalled because a file was somewhere you could not name. Same symptom every time — capture worked and retrieval did not.
The second signal is volume. Below roughly fifteen live commitments, a flat list and decent search will carry you. Above that, structure starts paying for itself. Which app to run it in is a separate argument, and second brain apps works through the shortlist.
Where init.Tasks fits
init.Tasks puts the to-dos and the material in the same object. It is a terminal-styled task and project app for iOS, macOS and web, and a link, a note, an image or a file is filed into a project beside that project's to-dos rather than into a parallel notes app.
So the school-application project holds "book the open day" next to the catchment map, the two prospectus PDFs and the note about the closing date. Nothing gets reconciled by hand because nothing was ever split. For the task half of that story, the app for GTD piece covers the five lists and the setup pass, so they are not repeated here.
The AI connection is coming in september: connect an assistant that speaks MCP and it can read a project and file into it. The beta waitlist is open and everything is free while in beta.
FAQ
What is a second brain?
A second brain is an external, organised store for the information you want to be able to use later — links, notes, files, images, decisions — kept next to the work it serves rather than in a general archive. The point is retrieval, not storage. If a saved thing does not surface at the moment it is useful, it was filed, not captured.
Is a second brain the same as taking notes?
No. Notes are one input. A second brain is the structure around all of them, including the inputs that are not text: a PDF, a screenshot, a link, a phone number. Apps that only accept typed text push everything else elsewhere, and that split is where most systems quietly fail.
How is a second brain different from a to-do list?
A task list holds what you owe. A second brain holds what you need in order to pay it. The two usually sit in different apps, so finishing a task means opening a second app to find the material — and that extra step is where things get postponed.
Do I need a special app to build a second brain?
No. A folder tree and consistent naming will do it, and paper worked for decades. An app helps with three things: capturing in under three seconds, searching every kind of item at once, and keeping the material beside the tasks. Judge candidates on those, not on feature counts. Personal knowledge management app goes through what you can get back out of each one.