How to build a second brain without the clutter

A second brain is a place outside your head where you keep notes, plans and reference material so you can find them again. In a notes app, the simplest version is four top-level pages, Inbox, Projects, Areas and Archive, with nested pages underneath and one database to track your projects. Keep the structure shallow and review it once a week, and it stays useful instead of turning into a pile.

Why most second brains get cluttered

Most people start with too much structure. They build dozens of folders, tags and lists on day one, then stop using them after a fortnight. The system becomes something to maintain rather than something that helps.

The fix is to start with very little and only add structure when you feel a real need. Four pages and one database is enough for most people for months.

The four top-level pages

Each top-level page has one job.

• Inbox. Everything new lands here first: a quick idea, a link, a meeting note. You do not sort as you capture. Speed matters more than tidiness.
• Projects. Work with a clear finish line and a rough deadline. "Redo the kitchen", "Plan the Lisbon trip", "Write the Q3 report".
• Areas. Ongoing parts of life with no end date. Health, money, home, your job, a hobby. These hold standards and reference notes, not tasks with deadlines.
• Archive. Finished projects and anything you no longer need day to day but do not want to delete.

The difference between a project and an area is the most useful idea here. A project ends. An area does not. If you cannot say what "done" looks like, it is probably an area.

Build it with nested pages

In a notes app with pages inside pages, each of the four becomes a top-level page. Underneath, add one sub-page per project or area.

A project page might hold:

• one line at the top saying what done looks like,
• a to-do list of next actions,
• meeting notes or research as sub-pages of their own.

An area page holds reference material: a checklist for the annual car service, notes from a course, a list of where important documents are kept.

Try to keep it to three levels: top-level page, project or area, then supporting notes. Anything deeper is hard to move around in, especially on a phone screen.

Add one database for projects

Pages are good for writing. A database is better when you have many similar items and want to see them side by side. Projects are the obvious candidate.

Create one database inside the Projects page with a few properties:

• Status (select): Not started, Active, Waiting, Done.
• Area (select): Health, Money, Home, Work.
• Due (date).
• Next step (text).

Use the table view to see every project in rows. Switch to a board view to see them as cards in columns by status. Keep the detailed notes for each project on its own page, and use the database as the overview.

One database is enough. Resist building separate databases for books, recipes, contacts and habits until you actually miss them.

A worked example

Sam is a freelance designer. Here is her setup after one evening.

• Inbox has six loose notes from the week: two client ideas, a podcast recommendation and a screenshot of a tax deadline, among others.
• Projects has a database with five rows, including "Brand refresh for bakery" (Active, Work, due 14 November), "File self-assessment" (Not started, Money, due 31 January) and "Portfolio update" (Waiting, Work). Each project also has its own page for notes.
• Areas has pages for Clients, Finances, Health and Learning.
• Archive has last year's finished projects.

Every Friday she spends 15 minutes on her Inbox. The tax screenshot goes into the "File self-assessment" page. The podcast goes into Learning. One client idea becomes a new project row, and the other is deleted. The Inbox ends the week empty.

Common mistakes

• Sorting while capturing. It slows you down, so you stop capturing. Drop it in the Inbox and sort later.
• Too many top-level pages. Ten top-level pages means ten places to look. Keep four.
• Turning areas into projects. "Get fit" never finishes. Make it an area, and create projects such as "Run a 10k in May" inside it.
• Never archiving. Finished work left in Projects hides the active work. Set its Status to Done and move its page to Archive.
• Building for a system you might need one day. Add a second database only after you have felt the gap for a few weeks.

Where Asendify Notes fits

If you want a plain, ad-free place to build this, Asendify Notes gives you pages inside pages, a block editor with headings, to-dos and tables, and simple databases with table and board views. Search covers everything, deleted pages stay in the trash for 30 days, and you can export all your data as JSON. It is a small, paid product with no free plan or trial, so it suits people who already know they want a simple workspace.

Key takeaways

• Start with four pages: Inbox, Projects, Areas and Archive.
• A project has a finish line. An area does not.
• Keep nesting to about three levels.
• Use one database for projects, with Status, Area, Due and Next step.
• Empty the Inbox once a week and archive finished work.

FAQ

Do I need a database for a second brain?

No, but one helps. Nested pages are enough to start. A single projects database becomes useful once you have more than five or six active projects and want to see their status at a glance.

How often should I review my second brain?

Once a week is enough for most people. Empty the Inbox, update each active project's next step, and move anything finished to the Archive.

How much does Asendify Notes cost?

It costs £1,450 a year: £1,000 plus a 45% service fee, shown openly. There is no free plan and no free trial. You can pay by card or PayPal. If you pay by card, yearly auto-renew is optional and can be turned off any time in Settings.

More playbooks on other topics: https://www.asendify.co/books/

More Asendify Notes articles