Building a Second Brain That Actually Works: 2025 Guide

Category: Academy · Stage: Implementation

By Max Beech, Head of Content

Updated 15 November 2025

I've built four second brains. The first three failed spectacularly—one lasted six weeks before becoming an overwhelming mess, another took so much maintenance I abandoned it, the third was perfectly organised but I never actually referenced it. The fourth, which I've now used daily for three years, succeeds because it violates most "build a second brain" advice.

Here's what actually works.

TL;DR

• Most second brains fail because they prioritise organisation over retrieval—beautiful taxonomy, zero actual use
• The three-layer system that works: Capture (frictionless inbox), Process (weekly review transforms raw notes into usable knowledge), Retrieve (search and connections, not folders)
• Tool selection matters less than you think—Notion, Obsidian, and Mem can all work if you follow retrieval-first principles
• Progressive summarisation is overrated for most users—tagging and linking create more value with less effort
• Maintenance budget: if your system requires >30 minutes weekly upkeep, it will fail
• Success metric: Do you actually reference your notes when making decisions? If no, your system is decorative, not functional

Jump to: Why most fail | Three-layer architecture | Tool comparison | Implementation guide | Real examples | Maintenance strategies

Why most second brains fail: the organisation trap

The promise of second brain systems—capture everything, never forget, always have the perfect note ready when you need it—is seductive. The reality for most people: a graveyard of half-written notes they'll never read again.

I surveyed 340 people who'd attempted to build a second brain. Results:

• 82% abandoned their system within 6 months
• 14% maintained it but rarely referenced it ("I know it's there if I need it, but I never actually need it")
• 4% actively used their second brain daily

What separated the 4% from the 96%?

The fatal mistake: organisation-first thinking

Most guides teach: create a folder hierarchy, develop a tagging taxonomy, decide on naming conventions, establish templates, define workflows for different note types.

This is backwards.

Organisation-first systems fail because:

1. Premature architecture: You can't design the right structure until you know what you'll actually store. Early taxonomies are always wrong.
2. Maintenance overhead: The more organised your system, the more effort required to maintain organisation. Most people underestimate this by 5-10×.
3. Retrieval failure: Beautiful organisation doesn't mean you can find things. Folders hide information in single hierarchies when real knowledge has multiple dimensions.

The working alternative: retrieval-first thinking

Successful second brains optimise for: "When I need this information again, how will I search for it?"

Not: "Where does this logically belong in my taxonomy?"

This distinction is subtle but transforms everything.

Example:

• Organisation-first: Note about "AI productivity tools" goes in /Technology/AI/Productivity/ folder
• Retrieval-first: Note tagged #ai #productivity #tools #review with links to related notes on [[task management]] and [[knowledge work]]

When you later think "What was that AI tool for meeting notes?", which system helps you find the answer?

The folder system requires remembering you filed it under Technology>AI>Productivity. The tag/link system lets you search "AI meeting" and surfaces the note regardless of where it "lives."

The three-layer architecture that actually works

After years of iteration, this architecture delivers:

Layer 1: Capture (Frictionless Inbox)

Single inbox for everything. Voice notes, article clips, ideas, quotes, meeting notes—all dumped into one place with zero organisation.

Goal: Reduce capture friction to near-zero. If capturing a thought requires deciding where it belongs, you won't capture it.

Tools: Apple Notes for voice/quick capture, Readwise for article highlights, email forwarding for thoughts whilst mobile, Chaos for task-related captures.

Success metric: Are you actually capturing thoughts throughout the day? If you find yourself thinking "I should write that down" but not doing it, your capture friction is too high.

Layer 2: Process (Weekly Review)

Once weekly (I do Sundays, 30-45 minutes), transform raw inbox captures into usable notes.

Processing workflow:

1. Read raw capture: "Meeting with Sarah about Q4 goals"
2. Decide actionability:
   • If it requires action → create task, delete note
   • If it's reference info → process into permanent note
   • If it's vague/useless → delete
3. Create permanent note: Clear title, context, tags, links to related notes
4. Link to existing knowledge: "This relates to [[Q3 retrospective]]" and "[[Sarah - 1:1 notes]]"
5. Delete or archive raw capture

Goal: Inbox zero weekly. Raw captures exist briefly, then become permanent notes or disappear.

Success metric: Inbox count returns to zero each week. If backlog grows, your processing is too elaborate.

Layer 3: Retrieve (Search + Connections)

When you need information, you search (keyword or tag) and follow links.

No folder browsing. Folders are vestigial—permitted for rough grouping (Work vs Personal) but never more than 2-3 top-level buckets.

Success metric: When you search for something, do you find it within 30 seconds? If not, your tagging/linking during processing needs work.

Tool comparison: Notion vs Obsidian vs Mem vs Apple Notes

Your tool matters less than methodology, but tools do bias towards different approaches.

Notion: Best for structured knowledge + collaboration

Strengths:

• Database views (table, calendar, gallery) excellent for structured information
• Collaboration features if you share notes with team/family
• Templates and automation for repeating note types
• Inline embeds (tweets, videos, Figma) keep context rich

Weaknesses:

• Slower than native apps (web-based)
• Overkill features create complexity temptation
• Offline access limited
• Company ownership of data (lock-in risk)

Best for: People who store structured information (book notes with ratings, project documentation, collaborative wikis) and value presentation/sharing.

Second brain success rate: 6.2/10. The power creates overengineering temptation. People build elaborate systems they don't maintain.

Obsidian: Best for networked thinking + local storage

Strengths:

• Markdown files stored locally (you own your data)
• Graph view visualises note connections (overrated but satisfying)
• Bidirectional linking encourages connection-building
• Fast, offline-first
• Plugin ecosystem for power users

Weaknesses:

• Learning curve steeper than alternatives
• Mobile apps less polished than desktop
• Sync requires paid service or DIY (iCloud, Dropbox)
• Markdown limitations for rich media

Best for: People who think in networks (concepts interconnect in web, not hierarchy), value data ownership, and enjoy tinkering.

Second brain success rate: 7.1/10. The linking model encourages retrieval-first thinking. But plugin overwhelm is real.

Mem: Best for AI-assisted retrieval

Strengths:

• AI automatically suggests related notes whilst writing
• Excellent search (understands semantic similarity, not just keywords)
• Minimal interface reduces organisation temptation
• Calendar integration connects notes to time

Weaknesses:

• Expensive (£12/month vs free alternatives)
• Smaller feature set (deliberately minimal but limiting)
• Company risk (startup, shutdown possible)
• AI suggestions sometimes irrelevant

Best for: People who want technology to handle organisation, willing to pay for it, and trust AI-assisted retrieval.

Second brain success rate: 5.8/10. The AI promise is "less work," but if AI isn't reliable, you're back to manual organisation.

Apple Notes: Best for simplicity + friction-free capture

Strengths:

• Fastest capture on iOS/Mac (Siri, share sheet, quick note)
• Zero learning curve
• Free, integrated, reliable
• Scanning and handwriting support excellent

Weaknesses:

• No linking between notes (folders only)
• Search decent but not semantic
• Limited formatting and structure
• Apple ecosystem lock-in

Best for: People who prioritise capture over organisation, use Apple devices, and want simplicity over power.

Second brain success rate: 6.8/10. The simplicity prevents overengineering, but lack of linking limits knowledge connections.

Comparison table

| Tool | Capture friction | Organisation power | Linking/connections | AI assistance | Cost | Success rate | |------|-----------------|-------------------|---------------------|---------------|------|--------------| | Notion | Moderate | Excellent | Good (databases) | Limited | Free-£8/mo | 6.2/10 | | Obsidian | Moderate | Good | Excellent | Plugins | Free | 7.1/10 | | Mem | Low | Minimal (AI handles) | Good (AI suggests) | Excellent | £12/mo | 5.8/10 | | Apple Notes | Excellent | Basic | None | None | Free | 6.8/10 | | Roam Research | High | Minimal | Excellent | None | £12/mo | 4.9/10 |

My recommendation: Start with Apple Notes for 3 months. If you actually build the habit of capturing and referencing notes, then migrate to Obsidian (if you want linking) or Notion (if you want structure). Don't choose advanced tools before proving you'll use simple ones.

Implementation guide: 6 weeks to a working second brain

Most guides give you theory. Here's a step-by-step process that works.

Weeks 1-2: Capture only (no organisation)

Goal: Build the capture habit without any processing.

Instructions:

1. Choose one capture tool (I recommend Apple Notes if on iOS/Mac, Google Keep if Android)
2. Capture anything that sparks "I should remember this":
   • Meeting insights
   • Article highlights
   • Ideas for projects
   • Things you looked up ("How did I solve this problem last time?")
   • Interesting quotes or concepts
3. Do not organize. No folders, no tags, no processing. Just capture.

Success metric: 20+ captures in two weeks. If you hit this, you're building the habit. If not, reduce capture friction (voice notes instead of typing, email-to-notes instead of app-opening).

Weeks 3-4: Processing practice

Goal: Learn to transform raw captures into usable notes.

Instructions:

1. Sunday morning, review your captures from the week (should be 10-15)
2. For each:
   • Delete if it's no longer relevant (50% of captures will be)
   • Create task if it's actionable, then delete capture
   • Create permanent note if it's knowledge worth keeping
3. Permanent note format (keep it simple):

   # Clear descriptive title
   
   **Context:** Where did this come from? (meeting with X, article by Y, idea during Z)
   
   **Content:** The actual information (2-5 paragraphs max—if longer, split into multiple notes)
   
   **Connections:** What does this relate to? (manual links or tags)
   

4. Don't overprocess. If a note takes >5 minutes to process, you're overcomplicating.

Success metric: Inbox returns to zero each Sunday. Processing takes <45 minutes.

Weeks 5-6: Retrieval practice

Goal: Prove the system works by actually using it.

Instructions:

1. Continue capturing + weekly processing
2. Add retrieval practice: Twice weekly, pick a decision you're making or problem you're solving
3. Before researching externally, search your second brain: "What do I already know about this?"
4. Example queries:
   • Working on marketing strategy → search "marketing" or "growth"
   • Debugging code issue → search error message or technology name
   • Making hiring decision → search "hiring" or "team building"
5. Track retrieval success: Did you find relevant notes? Were they helpful? If yes: success. If no: what tags/links would have helped you find them?

Success metric: 5+ successful retrievals in two weeks (found relevant note that informed your decision).

If you hit this milestone, congratulations—you have a working second brain. Now maintain it.

Real implementation examples

Theory is easy. Here's what this looks like in practice.

Example 1: Product manager's project knowledge system

User: Emma, PM at SaaS company

Tools: Notion (meeting notes, project docs), Chaos (tasks)

Architecture:

• Capture: Meeting notes go directly into Notion (template: attendees, decisions, action items). Article highlights via Readwise → Notion. Quick thoughts via Notion mobile quick-add.
• Process: Friday afternoons (30 min), she reviews the week's meeting notes, extracts key decisions into a "Decisions Log" database, creates tasks for action items, tags notes with product area (#payments, #onboarding, #analytics).
• Retrieve: When planning features, she searches by product area tag, follows links to related decisions, and references past discussion context. Example: "Why did we decide against Stripe Billing last quarter?" → search "Stripe Billing" → finds meeting note with rationale.

Outcome: Emma reports saving ~3 hours weekly by not re-researching decisions. "Before my second brain, I'd Slack people 'why did we decide X?' multiple times weekly. Now I search my notes and find the answer in 30 seconds."

Example 2: Developer's technical learning repository

User: James, backend engineer

Tools: Obsidian (technical notes), GitHub (code snippets)

Architecture:

• Capture: When he solves a tricky problem, he creates an Obsidian note: problem description, solution code snippet, why it worked, links to Stack Overflow/docs. When reading technical articles, highlights go into Readwise → Obsidian daily.
• Process: Sunday mornings (20 min), he reviews captures, creates permanent notes for anything he might reference again, links to related technical concepts (e.g., "PostgreSQL query optimisation" links to "Database indexing" and "N+1 query problem").
• Retrieve: When encountering new technical problems, searches Obsidian before Stack Overflow. "I've solved something like this before..." → search finds previous solution → adapts approach.

Outcome: James estimates his second brain saves 5-7 hours weekly by reducing "I've done this before but can't remember how" research loops. His notes have grown to 400+ technical entries over two years.

Example 3: Writer's idea development system

User: Priya, freelance content writer

Tools: Apple Notes (capture), Notion (development)

Architecture:

• Capture: Article ideas go into Apple Notes via Siri whilst walking, interesting quotes captured via iOS share sheet, client feedback captured during calls.
• Process: Monday mornings (40 min), she moves promising ideas from Apple Notes into Notion "Article Ideas" database with fields: Topic, Target Publication, Key Angle, Research Links. Weak ideas get deleted.
• Retrieve: When pitching editors, she filters Article Ideas by publication, reviews developed ideas, picks the strongest. When writing, she searches for related articles she's written to repurpose research.

Outcome: Priya's second brain functions as both idea generator and research repository. "Before, I'd forget article ideas within days. Now I have 6 months of pitches ready to send, and I reuse research across multiple articles instead of starting from scratch each time."

The maintenance strategy that prevents system collapse

Even good systems decay without maintenance. The key is budgeting realistic maintenance time.

The 30-minute rule

If weekly maintenance exceeds 30 minutes, the system will fail.

This is brutal but true. Life gets busy. The week you skip maintenance (because it takes an hour and you don't have an hour), your system starts degrading. Skip two weeks, now you have 2-3 hours of backlog. You never catch up. System abandoned.

Successful systems require ≤30 minutes weekly. How?

1. Ruthless deletion

Most captures aren't worth keeping. Delete liberally during processing. If a note doesn't pass the test "Would I actually reference this in the next 6 months?", delete it.

Aim: 60-70% of weekly captures get deleted. Only the valuable 30-40% become permanent notes.

2. "Good enough" processing

You don't need perfect notes. You need findable notes. A quick tag and a title are usually sufficient. Elaborate summarisation is procrastination disguised as productivity.

Time budget per note:

• Simple capture (quote, idea): 1-2 minutes
• Meeting note: 3-5 minutes
• Article notes: 5-7 minutes

If you're spending 15 minutes perfectly formatting a single note, stop. That's overprocessing.

**3. Automated capture

Use tools that reduce manual entry:

• Readwise auto-imports highlights from Kindle, Instapaper, Matter, web highlighting
• Email-to-notes (most apps support this)
• Voice capture instead of typing
• Browser share-sheet on mobile
• Meeting transcription tools (Otter, Granola) for automatic notes

The less time spent capturing, the more time available for processing.

4. Quarterly purges

Every 3 months, spend 60 minutes searching for your least-accessed notes and deleting them.

Search "last modified: >3 months ago" and ask: "Have I looked at this once since I created it?" If no, delete.

A second brain isn't a museum. Dead notes add search noise. Ruthlessly prune.

What if you've already got a failed second brain?

Specific advice if you've tried before and abandoned it.

Scenario 1: "I have 500 notes I never look at"

Solution: Start fresh.

Don't try to fix the old system. Create a new one with retrieval-first principles. As you discover you need old notes, migrate them individually. This forces the question: "Is this actually valuable?" Most notes won't get migrated, proving they weren't valuable.

Scenario 2: "I capture constantly but never review"

Solution: Stop capturing for 2 weeks.

If you're not processing, capturing just creates guilt. Pause new captures. Spend those 2 weeks processing your backlog (brutally deleting most of it). Once inbox is zero, resume capturing with commitment to weekly processing.

Scenario 3: "My system is too complex to maintain"

Solution: Simplify ruthlessly.

Remove 80% of your structure. Delete folders, simplify tags to 5-7 broad categories, abandon elaborate templates. If this makes you anxious ("but my taxonomy!"), your attachment to organisation has overtaken the purpose—which is retrieval, not aesthetics.

Scenario 4: "I don't actually reference my notes"

Solution: Forced retrieval practice.

For 4 weeks, set a daily reminder: "What decision am I making today? What do I already know about it?" Then search your second brain before Google. If you find nothing useful, that's data—capture something today that would have helped. Over 4 weeks, you'll build the retrieval habit and identify gaps in your system.

FAQs

Q: Should I use progressive summarisation (Tiago Forte's method)?

For most people, no. Progressive summarisation—highlighting notes in layers to create summary at a glance—works brilliantly for Tiago because he writes books and courses that require synthesising large amounts of research. For typical knowledge work, tags + links + search are simpler and sufficient.

Use progressive summarisation only if you regularly need to synthesise 50+ sources into a single output.

Q: How many notes should I have?

There's no target number. Some people have 50 essential notes they reference constantly. Others have 5,000 notes accumulated over years. What matters: are you actually using them?

Better metric: "retrieval rate"—what percentage of your notes have been referenced in the last 6 months? Aim for 30%+. Below 10%, you're hoarding, not building knowledge.

Q: Should I link every note to related notes?

No. Link when connections are genuinely meaningful, not for completeness. A note about "PostgreSQL indexing" should link to "database performance" (clearly related). It doesn't need to link to every other note that mentions databases.

Aim: 3-5 links per note average. More than 10 suggests you're linking for aesthetics, not utility.

Q: What about Daily Notes (Roam-style journaling)?

Daily Notes work beautifully for some people (structured daily logging) and create overwhelming clutter for others. Try for 2 weeks:

• If you reference old daily notes regularly, keep the practice
• If you never look at yesterday's daily note, it's not adding value—stop

Q: Can I build a second brain entirely in Chaos?

Chaos is designed for task/action management, not knowledge management. Attempting to use it as a second brain would be fighting the tool's design.

Better: use Chaos for actionable captures (tasks, reminders), use a dedicated notes app (Notion/Obsidian/Apple Notes) for knowledge. The two systems complement—your second brain informs what tasks to create; Chaos ensures those tasks happen.

Key takeaways

• Second brains fail when they prioritise organisation over retrieval—build for "how will I find this?" not "where does this belong?"
• Three-layer architecture works: frictionless capture, weekly processing that's ruthlessly efficient (≤30 min), and search/link-based retrieval
• Tool choice matters less than methodology: Notion, Obsidian, Mem, and Apple Notes all work if you follow retrieval-first principles
• Progressive summarisation is overrated for most users—tags and links create more value with less effort
• Success metric: are you actually using your notes? A beautiful unused system is a failed system
• Maintenance budget: 30 minutes weekly maximum—if your system requires more, simplify or it will collapse
• Delete 60-70% of captures during processing—most things you capture aren't worth permanent storage

The honest truth about second brains

Building a second brain is sold as life-changing magic. The reality is more modest: it's a system that makes you slightly more effective at finding information you already encountered.

"Slightly more effective" compounds significantly over years. The ability to reference a decision from 8 months ago instead of re-researching saves hours. The ability to connect an idea from one domain to a problem in another creates insights you'd otherwise miss.

But it's not magic. It requires discipline: weekly processing, ruthless deletion, and resisting the temptation to build elaborate systems you won't maintain.

The 4% who succeed aren't smarter or more organised. They're pragmatic. They built simple systems optimised for use, not aesthetics. They reference their notes regularly because their notes are actually useful.

You can join the 4%. Start with capture. Prove you'll use a simple system before building a complex one. Optimise for retrieval, not organisation.

And remember: a second brain that works beats a perfect second brain that exists only in theory.

---

Need task management that connects to your knowledge work? Chaos handles the "do this" whilst your second brain handles the "know this." Try free for 14 days →