Building Your Second Brain -- An Obsidian Setup Guide

A technical guide written for everyone — from engineers to executives — who wants to stop losing good ideas and start building a knowledge system that actually works.

A few years from now, I look back at a simple question that changed how I work: Where did I write that down?

Maybe it’s in Slack. Maybe a Google Doc. Maybe a sticky note. Maybe the notes app on my phone. Maybe nowhere — maybe I just forgot. That fragmentation is the default state of knowledge work, and it is quietly expensive. Every time you re-research something you already knew, re-explain context to yourself before resuming a task, or forget a decision and re-litigate it in a meeting — that is time and clarity you don’t get back.

This is a practical guide to the system I built to fix that problem. It uses Obsidian, a free local-first note-taking application, combined with a handful of carefully chosen plugins and an AI integration layer that makes the whole thing dramatically more useful. You don’t need to be a software engineer to follow this guide, though there are sections that go deeper for those who are.

Let’s build your second brain.

Why Obsidian? (And Why I Left OneNote)

For years I was a committed OneNote user. Not a casual one — a power user. Color-coded notebooks, nested sections, pages and subpages, embedded spreadsheets, shared notebooks for team collaboration. I knew the keyboard shortcuts. I had an organizational system. I genuinely believed OneNote was the best tool for the job.

I was wrong, and it took me longer than it should have to figure that out.

The OneNote Problem

OneNote is a capable product with a serious long-term liability: your knowledge lives inside Microsoft. The file format is proprietary. Exporting is painful and lossy. Search degrades as notebooks grow. The organizational model — Notebooks → Sections → Pages → Subpages — is rigid and doesn’t map well to how ideas actually connect. There’s no way to link a page in one notebook to a concept in another without copy-pasting. Tags exist but are an afterthought, not a first-class feature. And most critically: no AI tool in the world can reason about the contents of your OneNote notebooks unless Microsoft builds that feature and you trust them with your data.

I also ran into the subtler problem that every OneNote power user eventually hits: the organizational debt. After a few years, I had notebooks I was afraid to restructure because I couldn’t find things reliably enough to know what I’d break. The system had grown, but it hadn’t grown smarter.

Why the Switch to Obsidian Was Worth It

When I finally made the move, the benefits were immediate and compounding:

Your notes are files you actually own. Every note in Obsidian is a plain .md (Markdown) text file sitting in a folder on your hard drive. You can open them in any text editor, grep through them in a terminal, back them up with any tool you already use, and they will be readable in thirty years without any software. OneNote’s .one format is a black box — try opening it without OneNote installed.

Linking is a first-class feature. In Obsidian, typing [[note name]] creates a bidirectional link between two notes. OneNote has no equivalent. This single feature unlocks the Zettelkasten method and lets your knowledge base grow into something that actively helps you think, rather than just storing what you’ve already thought.

The organizational structure is yours to define. OneNote gives you one hierarchy: Notebooks → Sections → Pages. Obsidian gives you folders, tags, links, properties, and canvas views — and you decide how to combine them. If you want to reorganize, you move files in a folder. No export, no re-import, no data loss.

Search actually works at scale. With the Omnisearch plugin and Text Extractor, Obsidian indexes your entire vault including PDFs and images with intelligent ranking. OneNote’s search becomes progressively less reliable as notebooks grow, and it has no mechanism for semantic or fuzzy search.

AI can read everything. This is the game-changer. Because your vault is a folder of text files, any AI tool — a local Ollama model, Claude Code running in your terminal, a future tool that doesn’t exist yet — can read, analyze, and reason about your entire knowledge base. When I was on OneNote, AI-assisted search and synthesis of my own notes wasn’t possible. Now it’s a daily workflow.

It works without the internet. OneNote requires a Microsoft account and syncs through the cloud. Obsidian works entirely offline. Your notes are available on a plane, in a basement, or after Microsoft changes its licensing model.

What OneNote Still Does Well

To be fair: OneNote is excellent for handwritten stylus notes on a tablet, and its integration with Microsoft Teams and Outlook is genuinely useful for shared team notebooks in an enterprise environment. If your organization runs on Microsoft 365 and you need collaborative real-time editing with colleagues who won’t adopt a new tool, OneNote is reasonable for shared notes. My recommendation: keep a shared OneNote for team collaboration if your workplace requires it, but run Obsidian for your personal knowledge base — the notes that belong to you regardless of where you work.

Migrating from OneNote

The migration doesn’t have to be all-at-once. I exported my most active notebooks from OneNote as Word documents (File → Export), then used Pandoc to convert them to Markdown. It’s imperfect — formatting gets messy, embedded images need manual cleanup — but the content survives. For older notebooks I’d barely touched, I left them in OneNote as a read-only archive rather than spending time migrating notes I’d never look at again. Start fresh in Obsidian for anything new, and migrate old content only when you need it.

There are dozens of other note-taking apps — Notion, Roam, Logseq, Bear, Apple Notes. Here’s why Obsidian stands out from all of them:

1. Your notes are plain Markdown files on your hard drive. There is no proprietary format, no lock-in, no subscription required to access your own data. You own your notes the way you own a book.
2. It works offline, completely. Your knowledge doesn’t depend on someone else’s server.
3. It is infinitely extensible. A plugin ecosystem with hundreds of community-built tools means you can shape the system to your workflow rather than the other way around.
4. It works beautifully with AI. Because your notes are plain text files in a folder, any AI tool — local or cloud-based — can read, index, and reason about your entire vault.

Step 1: Choose an Organization System (And Use AI to Help You Design It)

Before you install anything, you need to answer one question: How will I organize my notes?

This is where most people either over-engineer or give up. Don’t. There are three well-known frameworks worth understanding:

PARA (Projects, Areas, Resources, Archives)

Developed by Tiago Forte, PARA organizes everything by actionability:

• Projects — things with a goal and a deadline
• Areas — ongoing responsibilities with no fixed end (your health, your team, your finances)
• Resources — reference material you might use someday
• Archives — everything completed or inactive

PARA is intuitive and maps well to how knowledge workers actually think.

Johnny.Decimal

A numeric ID system where every folder and note gets a two-level decimal number (e.g., 10.01, 10.02). It forces you to limit your categories, prevents folder sprawl, and makes things easy to find and reference by number. Think of it like a library’s Dewey Decimal system for your brain. See Johnny.Decimal for more information.

Zettelkasten

A method popularized by sociologist Niklas Luhmann, who built a 90,000-card index that helped him write 70 books. The idea: every note is small, atomic, and linked to other notes. Over time, the links between ideas become more valuable than the notes themselves. It’s powerful for researchers and writers. See Zettelkasten Wikipedia for more information.

What I Ended Up With: A Hybrid

I combined all three. My vault uses Johnny.Decimal numbering in the thousands as the folder structure, PARA categories as the semantic meaning of those numbers, and a dedicated Zettelkasten folder for atomic ideas. Here’s how it maps:

1000 - Projects/     ← PARA Projects, with decimal subfolders (1001, 1002…)
2000 - Areas/        ← PARA Areas  (2001, 2002…)
3000 - Resources/    ← PARA Resources
4000 - Archives/     ← PARA Archives (folders keep their original ID when archived)
9000 - Zettelkasten/ ← Flat folder of atomic, interconnected notes
Daily Notes/         ← Organized as YYYY/MM-Month/YYYY-MM-DD-Weekday.md
_Extras/             ← Templates, images, scripts

The key insight: numbering your folders prevents them from multiplying endlessly. When you hit the natural limit of a numbering scheme, it forces you to think carefully before adding a new category.

Use AI to Design Your System

Here’s the part most guides skip: let an AI help you build this. Before I wrote a single note, I had a conversation with an AI assistant that went something like this:

“I’m a [software engineer / project manager / consultant]. My work involves [describe your work]. I want to build a personal knowledge management system using the PARA method with Johnny.Decimal numbering. Based on my role, what top-level categories make sense for my Areas folder? What kinds of projects should get their own numbered subfolder? Help me design an initial folder structure.”

The AI will ask clarifying questions and generate a draft structure tailored to your actual work. Iterate on it. You’re not locked in — the structure should evolve — but starting with a thoughtful skeleton beats starting from nothing.

Step 2: Set Up Obsidian’s Core Plugins

Obsidian ships with a set of built-in (core) plugins. Here are the ones worth enabling immediately:

Enable these in Settings → Core Plugins.

Step 3: Install Community Plugins

Go to Settings → Community Plugins → Browse. Here are the plugins in my vault and why each one earns its place:

Productivity & Workflow

Templater The single most important plugin in my vault. Templater replaces Obsidian’s built-in template system with a full scripting engine. My daily note template automatically fills in the current date, links to yesterday and tomorrow, inserts reflection prompts, and runs Dataview queries — all the moment I open a new note. Every note type (meetings, Jira tickets, bug reports) has a template. Templater is how you turn Obsidian from a blank canvas into a structured workflow.

Tasks (obsidian-tasks-plugin) This plugin transforms Obsidian into a real task management system. You write tasks anywhere in your vault using a standard syntax, and Tasks aggregates them into a single view filtered by due date, priority, tag, or any combination. The killer feature: your tasks live inside your notes, next to the context that created them, but you can also see all open tasks across your entire vault in one place. No more switching between your notes app and your task manager.

Day Planner (obsidian-day-planner) Adds a time-blocked schedule view to your daily note. You write a simple list like - 09:00 Team standup and Day Planner turns it into a visual timeline. It keeps you honest about where your time is actually going rather than where you think it’s going.

Dataview Think of Dataview as SQL for your notes. It lets you write queries like “show me all notes tagged #project that were modified this week, sorted by date” and renders the results as a table, list, or calendar right inside a note. My daily note template uses Dataview to automatically list every note created or modified today. It’s also how I build dashboards — a single “Projects MOC” note that always shows the current state of every active project.

Meta Bind (obsidian-meta-bind-plugin) Lets you create interactive UI elements — buttons, dropdowns, progress bars, toggles — bound to note properties. Useful for building lightweight “dashboards” inside notes without needing to write code.

Search & Discovery

Omnisearch Obsidian’s built-in search is good. Omnisearch is great. It provides Google-quality full-text search across your entire vault with intelligent ranking, fuzzy matching, and results that actually surface what you’re looking for. If you have more than a few hundred notes, install this immediately.

Text Extractor The companion to Omnisearch. Text Extractor reads the text content out of PDFs and images stored in your vault, making that content searchable. Drop a PDF into your vault and Text Extractor indexes it. Combined with Omnisearch, nothing in your vault is unsearchable.

Recent Notes A simple sidebar showing your most recently accessed notes. Underrated — it’s how you pick up where you left off without hunting.

Visuals & Diagrams

DrawIO (drawio-obsidian) Lets you create and embed DrawIO diagrams (.svg files) directly in your notes. Architecture diagrams, flowcharts, org charts — all stored and versioned alongside your notes as plain SVG files.

Excalidraw (obsidian-excalidraw-plugin) A hand-drawn-style whiteboard that lives inside Obsidian. Where DrawIO is precise and structured, Excalidraw is fluid and fast. Great for sketching out ideas, brainstorming diagrams, or quick visual explanations.

Canvas (core plugin) For spatial thinking — connecting notes, ideas, and media on an infinite whiteboard. Think of it as a mind map that links directly to your actual notes.

Export & Sharing

Better Export PDF (better-export-pdf) Obsidian’s built-in PDF export is basic. This plugin gives you control over headers, footers, page numbering, and styling. Essential if you share notes with people outside your vault.

Confluence Converter (confluence-converter) Converts Obsidian notes to Confluence wiki markup. If your organization uses Confluence, this dramatically reduces the friction of getting your notes into the shared knowledge base.

Copy Document as HTML (copy-document-as-html) One click copies the rendered HTML of your note to the clipboard. Useful for pasting into emails, Slack messages, or any rich-text editor while preserving formatting.

Pandoc (obsidian-pandoc) Export notes to Word, HTML, LaTeX, EPUB, and more using the Pandoc conversion library. The Swiss Army knife of note export.

PDF+ (pdf-plus) Enhanced PDF reading and annotation inside Obsidian. Highlight, annotate, and link directly to specific sections of PDFs stored in your vault.

Utilities

Table Editor (table-editor-obsidian) Markdown tables are notoriously painful to write by hand. This plugin gives you a spreadsheet-like editor for tables, with tab navigation between cells. A small quality-of-life improvement that you’ll use constantly.

Explorer Colors (explorer-colors) Lets you color-code folders in the file explorer. I use this to visually distinguish Projects (active, bright) from Archives (muted) at a glance.

AI Image Analyzer (ai-image-analyzer) Uses a local or cloud AI model to analyze images stored in your vault and generate descriptive text, making images searchable. Particularly useful if you screenshot things and store them in your notes.

Copy URL in Preview (copy-url-in-preview) When you’re reading a note in preview mode, this adds a right-click menu to copy URLs from links. Small but constantly useful.

Step 4: Use Daily Notes as Your Activity Log

The Daily Note is the heartbeat of the system. Every working day, I open a new daily note generated from a Templater template. My template includes:

• Day Planner block — time-blocked schedule for the day
• Top Priorities — the two or three things that actually matter today
• Reflection prompts — end-of-day questions that force honest retrospection
• Dataview: Notes created today — automatically lists every note I touched
• Dataview: Notes modified today — same, for edits
• Tasks: Scheduled for today — pulled automatically from across the entire vault

The navigation arrows at the top (<< Yesterday | Tomorrow >>) are Templater-generated links that make it trivial to page through your history. Over time, your daily notes become a detailed journal of your work life — searchable, linked, and always available locally.

The key habit: open your daily note every morning and close it every evening. It takes five minutes to set priorities in the morning and five minutes to capture reflections at night. That ten minutes is worth more than any productivity app.

Step 5: Use Tags Strategically

Tags in Obsidian are powerful because Omnisearch and the Tag Pane make them immediately queryable. But undisciplined tagging creates noise instead of signal. A few principles that work well:

• Use tags for cross-cutting concerns that don’t fit neatly into your folder structure. For example: #meeting_notes, #decision, #risk, #blocked
• Use tags for note types: #architecture, #runbook, #retrospective
• Keep your tag taxonomy small and deliberate. Twenty tags used consistently beats two hundred tags used randomly.
• Link to Maps of Content (MOCs) — index notes that aggregate links to related notes by topic. My meeting notes tag links to a Meeting Map of Contents note that provides an overview of meeting categories.

In the YAML front matter of every note, you can set properties that Dataview can query. This is distinct from tags but equally powerful — use properties for structured metadata (dates, status, priority) and tags for semantic categorization.

Step 6: Enhanced Search with Omnisearch and Local AI

Omnisearch already gives you excellent full-text search. But you can go further.

Local Ollama Integration

Ollama lets you run large language models locally on your machine — completely private, no data leaving your computer. When combined with Obsidian, you can:

• Ask natural-language questions about your notes: “What did I decide about the database migration?”
• Summarize long notes on demand
• Generate links between related concepts you might have missed
• Draft new notes based on existing content

Several Obsidian community plugins support Ollama as a local AI backend. Look for plugins that support “local LLM” or “Ollama” in the community plugin browser. The AI Image Analyzer plugin in this vault supports configuring a local model endpoint.

The combination of Omnisearch (keyword) + Ollama (semantic) means you can find things even when you don’t remember exactly how you phrased them.

Step 7: Wire In AI Assistance with AGENTS.md

This is where the system becomes genuinely future-proof.

When you use AI coding assistants like Claude Code, GitHub Copilot, or Cursor, those tools look for instruction files at the root of your project to understand context. The same principle applies to your Obsidian vault: create an AGENTS.md file at the vault root to serve as a briefing document for any AI that works with your notes.

Here’s what to include in your AGENTS.md:

# AGENTS.md — AI Instructions for This Vault

This is a personal knowledge management vault using Obsidian.

## Vault Structure
- 1000 - Projects/: Active projects with goals and deadlines
- 2000 - Areas/: Ongoing responsibilities
- 3000 - Resources/: Reference material
- 4000 - Archives/: Completed or inactive items
- 9000 - Zettelkasten/: Atomic idea notes
- Daily Notes/: Daily journals (YYYY/MM-Month/YYYY-MM-DD-Weekday.md)

## Conventions
- Jira tickets: 2000 - Areas/2001 - Jira Tickets/OC2-XXXX description.md
- Meeting notes: prefixed with YYYY-MM-DD, tagged #meeting_notes
- Tasks use Obsidian Tasks plugin syntax with scheduling dates
- MOCs (Maps of Content) link related notes across the hierarchy

## When Editing Notes
- Preserve YAML front matter
- Respect Templater syntax (<% ... %>) — do not modify template expressions
- Dataview code blocks (```dataview) are queries, not static content
- Do not rename files that use date-prefixed naming conventions

## README
See README.md for a full description of the organization system.

Pair this with a README.md at the vault root that explains the full system in prose — why each folder exists, how notes should be named, what each template is for, and how the plugins interact. The AGENTS.md is the machine-readable briefing; the README.md is the human-readable explanation. Reference the README from AGENTS.md so any AI tool can find the deeper context.

This two-file setup means that any AI assistant — whether it’s Claude Code analyzing your vault from the command line, a local Ollama model, or a future tool that doesn’t exist yet — arrives with full context about your system. It can make correct suggestions, avoid breaking your naming conventions, and understand the intent behind your structure.

Getting Started: The Minimal Viable Vault

If this feels overwhelming, start here. In order:

1. Download Obsidian from obsidian.md — free, available on Mac, Windows, Linux, iOS, and Android.
2. Create a vault folder in a location synced to your cloud provider (iCloud, Dropbox, Google Drive).
3. Ask an AI to help you design a folder structure based on your role and responsibilities. Use the prompt template in Step 1.
4. Enable Daily Notes in Core Plugins. Set a folder and create a simple template.
5. Install Templater and Tasks — these two community plugins give you 80% of the value.
6. Install Omnisearch — immediately better search.
7. Commit to the Daily Note habit for two weeks. Everything else can wait.
8. Create your README.md and AGENTS.md at the vault root once your structure stabilizes.

Add plugins and complexity only when you feel a specific pain point that a plugin would solve. The goal is a system you actually use, not a system that impresses you in screenshots.

Closing Thought

The best knowledge management system is the one you return to every day. Obsidian’s combination of local files, flexible structure, powerful plugins, and AI compatibility makes it uniquely well-suited for building that habit. The hybrid PARA + Johnny.Decimal + Zettelkasten structure described here took iteration to find — yours will too.

Start simple. Use AI as a thinking partner during the design phase. Add the plugins that solve real problems. Write the daily note. Link things together. Over months and years, the connections between your notes will become more valuable than any individual note — and you’ll stop asking “Where did I write that down?”

Written from experience. Your future self will thank you.