📝 Lesson 4.3: Capture, Process, Connect — A Second-Brain Workflow

The Loop That Ties It Together

Everything in this module has been building to one idea: a knowledge system isn't a place, it's a habit loop. Individual notes, methods, and daily pages are just the parts. The workflow is what makes them a machine. Here's the whole thing in one picture:

Four stages, and they genuinely form a cycle — Review feeds back into Capture (you notice gaps and new questions) and even back into Process (old notes resurface, ready to combine). Let's name what each stage is really for:

Capture: Frictionless In

You built the capture habit last lesson with daily notes. Let's formalize the idea behind it: the inbox.

You have two good options for your inbox, and you can even use both:

• The daily note — its ## Capture section is a perfect rolling inbox. Best if you live in your daily note anyway.
• A dedicated Inbox.md note (or Inbox/ folder) — one fixed place that doesn't move with the date. Best if you want a single, always-in-the-same-spot target.

The golden rule of capture is lower the bar until you can't trip over it. No titles, no folders, no tags at capture time — just get the thought down. A capture can be three words. The organizing happens later, at the Process step, on your schedule and not the idea's.

⚠️ Important Note: An inbox only works if it's trusted and singular. Three competing inboxes is the same as none — you'll never be sure where a thing is. Pick one primary inbox and route everything there.

Process: Raw Note to Atomic Note

This is the stage that separates a real second brain from a hoard. Processing means taking a raw capture and asking: is this worth keeping, and if so, what is the actual idea? Most captures are answered with "no, done" — and deleting them is a feature, not a failure. The few that survive get promoted into atomic notes (Lesson 4.1).

The processing checklist for one capture

1. Decide its fate. Trash it, do it (if it's a 2-minute task), or keep it as knowledge.
2. Extract the idea. Create a new note. Write the idea in your own words — no copy-paste.
3. Title it as a claim. "Deadlines create focus" beats "productivity note." The title is the idea.
4. Add properties. A little frontmatter makes the note findable later.
5. Then Connect (next section).

A processed atomic note, with properties, looks like this:

---
type: permanent
tags: [productivity, focus]
created: 2026-09-14
source: "[[2026-09-13]]"
---
# Deadlines create focus by forcing trade-offs

A deadline removes the option of "do everything," which is what
actually causes procrastination. The constraint is the feature:
it forces you to choose what matters and drop the rest.

Related: [[Parkinson's Law]] · [[Constraints boost creativity]]

Notice the source property links back to the daily note where it was captured — a breadcrumb to the original context. The type and tags make it queryable later (Dataview, Module 5). None of this is heavy: it's maybe 90 seconds per keeper.

Progressive summarization

Why this matters: it stops you from over-processing notes you'll never look at again, and it makes the notes you do use progressively faster to skim. In Markdown, the layers are just **bold**, Obsidian's ==highlight== syntax, and a summary line. Don't force it — let it happen naturally as notes prove their worth.

Connect: Wiring It In

An atomic note that isn't linked is a book with no shelf and no index — technically saved, practically lost. Connecting is what makes your notes resurface at the right moment, and it's the stage that pays off everything you learned about links and MOCs in Module 3.

For each freshly-processed note, ask three questions:

• What does this relate to, agree with, or contradict? Link those notes directly with [[ ]]. Contradictions are gold — they're where thinking happens.
• Which MOC does this belong under? Add a Part of: [[Topic — MOC]] line, or add the note to that MOC's list. This gives it an entry point you'll actually navigate through.
• Is there a note that should exist but doesn't? Write the link anyway — [[a note not yet created]]. Obsidian shows it as an unresolved link, a standing invitation to write it later.

Here's the closed loop from a real capture, so you can see the stages hand off to each other:

A useful mantra: a note isn't finished until it's connected. Processing writes the idea; connecting gives it a life in your vault.

Review: The Weekly Reset

The first three stages happen note-by-note, day-by-day. Review is the higher-altitude habit that keeps the whole system honest. Without it, entropy wins: the inbox fills, links go stale, and you slowly stop trusting your own vault. With it, you stay in control in about 15 minutes a week.

A simple weekly review (~15 min)

1. Empty the inbox. Process every remaining capture — keep, do, or delete — until the inbox is at zero. This is the core of the review.
2. Skim the week's daily notes. Rescue any good idea you captured but didn't process. Promote and connect it.
3. Glance at your projects/MOCs. What moved? What's stuck? Anything need a new note or link?
4. Look ahead. Jot the top 1–3 things for next week into an upcoming daily note or your weekly note.

The weekly note from the Periodic Notes plugin (Lesson 4.2) is the natural home for this. Give it a template with these four prompts and the review becomes a fill-in-the-blanks routine rather than a blank-page ordeal:

---
type: weekly
created: 2026-09-14
---
# Week {{date:GGGG-[W]WW}}

## 📥 Inbox to zero
- [ ] Process all captures

## 🌱 Ideas I promoted this week
-

## 🚧 Projects — moved / stuck
-

## 🎯 Focus for next week
-

Later, a Dataview dashboard (Module 5) can make review almost automatic — a note that lists every unprocessed capture, every note created this week, or every orphan with no links, generated live. For now, a manual skim is more than enough and teaches you what to automate later.

Keeping It Sustainable

The best workflow is the one you still run in six months. Elaborate systems collapse under their own weight; simple ones compound. Here's how to keep this loop light enough to last.

Three principles keep it sustainable:

• Build notes for your future self, not for show. The audience is you, in six months, tired and busy. Write so that person understands instantly. Clarity beats polish.
• Let structure emerge. Add a folder, tag, or MOC only when a real pain demands it — the same rule from Lesson 4.1. Don't pre-build.
• Consistency beats intensity. Five honest minutes daily grows a second brain; a heroic six-hour reorg once, then nothing, does not.

Plugins that accelerate the loop (later)

🎯 Project: Run One Full Loop

Theory's over. In the next 20 minutes you'll run the entire Capture → Process → Connect → Review loop once, start to finish, with real material from your own life. Doing it once makes it real; doing it once a day makes it a second brain.

Best Practices for the Workflow

✅ Do's

• Keep one trusted inbox. Everything routes there; nothing gets lost.
• Process a little, daily. Small and steady beats a giant dreaded session.
• Connect every keeper. A note isn't finished until it's linked.
• Guard the weekly review. It's the 15 minutes that keeps everything else trustworthy.
• Write for future-you. Clarity now saves confusion later.

❌ Don'ts

• Don't capture and organize at the same time. Two jobs, two moments.
• Don't fear deleting. Most captures should die; that's healthy.
• Don't chase automation before the habit exists. Manual first, plugins later.
• Don't let the inbox grow unbounded. A never-emptied inbox is a dying system.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've completed Module 4 with the thing most tutorials never give you: a working workflow, not just a pile of features. You know how to get an idea from your head, turn it into durable knowledge, wire it into a growing web, and keep the whole system alive week after week — sustainably. That is, genuinely, what a "second brain" is. Everything from here is refinement and power tools.

❓ Common Questions at This Stage

🔭 Looking Ahead

You've been leaning on core plugins (Daily notes, Templates, Backlinks) throughout this module. In the next lesson we take a proper guided tour of Obsidian's core plugins — the built-in superpowers already in your vault — so you know every tool at your disposal before we step into the community-plugin ecosystem.

✅ Before the Next Lesson

• Run the full loop at least once (the project) — and ideally again tomorrow
• Have a single, trusted inbox and know how to reach it instantly
• Put your first weekly review on the calendar and create its note
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Obsidian Help — official documentation
• Obsidian Help — Backlinks & Outgoing links
• Obsidian Help — Properties (frontmatter)
• Tiago Forte — Progressive Summarization