Second Brain Templates, Explained

Search for a second brain template and you will find thousands: Notion dashboards with careful greyscale icons, Obsidian vaults with pre-wired plugins, spreadsheets standing in for databases. Under the styling, nearly all of them are the same template, and that is not a criticism. It is the most useful thing to know before you choose one, because the canonical second brain has a small anatomy that every serious template implements, and once you can name the parts you can evaluate any template in the gallery in about a minute.

The best of these templates are real craftsmanship. A polished Notion second brain represents hundreds of hours of thinking about how databases should relate, what a weekly review should surface, and how a dashboard should feel on a Monday morning. If you are going to organize a Notion workspace by hand, starting from a template built by someone like Thomas Frank or Easlo is genuinely better than starting from a blank page, and the people who build them have earned the audiences they have.

• A capture inbox One place where everything lands first, so saving something never requires deciding where it goes. Every template has this because the insight is correct: capture and filing are separate jobs, and mixing them kills capture. The inbox comes with an implied contract, which is that you will empty it regularly.
• PARA buckets or topic areas The main organizational spine, almost always Tiago Forte's Projects, Areas, Resources, and Archives, occasionally a set of topic sections instead. This is where items from the inbox are supposed to end up, sorted by what you intend to do with them.
• A resource database A structured library for articles, links, books, and reference material, usually with properties for source, status, topic, and rating. This is the part of the template that looks most impressive in a demo, filled with someone else's example content.
• Project views Filtered dashboards showing active work: what is in flight, what is stalled, what got done. In tools with linked databases these views are the payoff for the tagging discipline everywhere else, because they only stay accurate if every item's properties do.
• A review checklist A recurring routine, usually weekly, for emptying the inbox, updating project statuses, and archiving what is finished. Template authors include it because they are honest: they know the structure only survives if a human maintains it on a schedule.

A template earns its place in three situations. The first is when your tool is manual by nature. Notion, Obsidian, and Apple Notes hold whatever structure you give them and build none of their own, so a template is the difference between inheriting a working system on day one and designing one from scratch while you are still learning the tool. The second is when you genuinely enjoy systems, and some people sincerely do: tuning a dashboard is part of how they think, and for them the template is a starting point for a hobby as much as a productivity tool. The third is a team that needs shared structure, because when several people file into the same workspace, an agreed template is how the workspace stays legible to everyone.

You also do not need to buy anything to get the canonical structure, because the structure is public. The layout underneath almost every paid template is PARA, and you can rebuild it in any tool in about ten minutes: create four top-level sections named Projects, Areas, Resources, and Archives, add a page for each piece of work with a clear endpoint under Projects, a page for each ongoing responsibility under Areas, let saved reference material accumulate in Resources, and move anything no longer active into Archives. That is the whole skeleton. We keep a plain-English walkthrough of the four buckets in our PARA guide, the linked atomic-note approach in our Zettelkasten guide, and the capture-to-publish workflow that sits on top of both in our CODE guide, all free to read whether or not you ever touch Mindly.

Here is the honest problem, and it applies to the best templates as much as the worst. A template arrives full of someone else's demo content and empty of yours, and every structure in it is a standing request for your future labor. The inbox asks to be emptied every week. The project dashboard asks for statuses to be updated. The resource database asks for every save to be filed, tagged, and rated. The review checklist is, quite literally, a list of chores. On the day you install it, a template is not an organized second brain. It is a promise that you will do the organizing, renewed weekly, forever.

This is why the abandoned second brain is such a familiar object. The first two weeks go beautifully, because the structure is fresh and the demo content makes everything look inevitable. Then a busy week arrives, the inbox reaches sixty items, the dashboards start describing your life as it stood in March, and opening the workspace begins to produce guilt instead of clarity. None of this is a personal failure, and it is not the template author's failure either. It is structural. A template can shorten the setup of a system, but it cannot perform the maintenance of one, and in a manual tool the maintenance is the system. A template is scaffolding for tools that make you do the organizing, and it stands exactly as long as your filing discipline does.

Mindly has no template gallery, and not because we have not gotten around to building one. The structure a template promises is the thing the app itself produces. You press ⌘M from any app on your Mac and save whatever is in front of you: a note, a link, a PDF, a file, a screenshot, a voice memo. The AI reads each item as it lands, writes a summary, tags it by topic, transcribes voice memos, reads the text inside screenshots, and links the new item to the related things already in your library. There is no inbox to empty, because nothing waits to be filed. There is no resource database to maintain, because the tagging is done by the time you look.

Measure that against what the template promised. Things sorted by topic: the tags do that automatically. Things connected to each other: the automatic links do that, and the interactive mind map shows the result as a living picture of what you know rather than a dashboard you update. Things findable later: you search in plain language and the search works by meaning, so a query in your own words finds the article you saved months ago under a title you have long forgotten, and you can open any saved item and ask it questions directly. The setup step a template shortens is a step Mindly deletes, and the maintenance step no template can do for you is deleted with it.

The honest boundary runs the other way too. If you love tinkering with systems, if adjusting database properties on a Sunday evening is a pleasure rather than a chore, a manual tool with a good template will make you happier than Mindly will, and you should keep Notion and choose a template with a clear conscience. Mindly is for the larger group of people who want the organized library without wanting the organizing, and who would rather their second brain live quietly in a local library on their own Mac than in a workspace that needs weekly attention.

Because there is no structure to build, starting takes a week of ordinary use rather than a weekend of setup. Download Mindly, which needs no account and runs on macOS 14 or later, and let the first week look like this.

• Day one: capture five things Press ⌘M and save whatever you would normally lose: the article in your browser, a PDF from your desktop, a screenshot, a stray thought typed or spoken. Do not organize anything. Watch each item come back with a summary and topic tags it earned on arrival.
• Days two and three: keep saving, resist sorting Save on instinct, ten or twenty items across the two days. The instinct to sort is the template habit talking, and this is where you retire it. The library is organizing itself in the background, and every save is making the tags and connections denser.
• Day four: search in your own words Ask for something you saved by what it was about, not what it was called. Try the vaguest phrasing you can, the way you would ask a colleague. Search that works by meaning is the moment most people stop missing folders.
• Day five: open the mind map Look at the week's saves as a map instead of a list. Items you saved on different days about the same theme will already be sitting near each other, connected. This is the dashboard a template asks you to maintain, drawn for you instead.
• Days six and seven: ask your library a question Open a saved article or PDF and ask it something directly, then decide the only thing that matters: whether you trust this enough to keep saving into it. Your first 25 items are free, which is deliberately enough to answer that question before any money changes hands.

A second brain template is a genuinely good answer to a real problem, as long as the tool underneath is one that makes you do the organizing. If that is your situation, take the free PARA skeleton or a well-made Notion template and go in with clear eyes about the weekly maintenance you are signing up for. If what you actually wanted was the outcome, a library where everything you save is summarized, tagged, connected, and findable in your own words, then the template was always a workaround, and you can skip it. Mindly is free for your first 25 items, and Pro is €7.99 a month or €44.99 a year after that, which costs less than most of the templates it replaces.