Use shallow folders for true containers (Daily/, Templates/, Attachments/), wikilinks on every new note as the default organising act, and 3–5 MOCs as your navigation layer once you cross ~50–100 notes. Treat folders as "where it lives", links as "what it relates to", tags as "what state it's in." If you're forcing a perfect folder tree, you're spending energy that should be going into links.
[1]
[2]
[3]
01 · the five primitives
Six mechanisms. Each one answers a different question.
Mixing them up is the #1 source of vault paralysis. Read each as a graph fragment — what it links to, what it costs.
"Where does this live?"
- up
- True container, file-system clarity
- down
- A note can only be in one — forces a choice
[[ ]]"What does this relate to?"
- up
- No exclusive ownership, builds graph
- down
- Discipline required to add at write-time
"Who pointed at me?"
- up
- Free — Obsidian generates from outgoing links
- down
- Only as good as your wikilink habit
"Who said my name without linking?"
- up
- Surfaces hidden connections retroactively
- down
- Noisy if titles are too generic
"What's the index for this topic?"
- up
- Note can live in many MOCs; supports context
- down
- Manual to maintain
#status"What state is this in?"
- up
- Live queries via search / Bases / Dataview
- down
- Bad at "aboutness" — degrades to clutter
02 · why "MOC vs folder" is the wrong fight
It's really about exclusivity.
A note about "AI in healthcare" belongs in Health/, AI/, and Work/ simultaneously — but the file system only lets you pick one.
Strict file tree
The note has one parent. To reorganise, you move the file.
MOC web
The note has one location, and any number of indexers.
Tim Miller (Obsidian Rocks) puts the limit bluntly. But "no folders ever" is also wrong — even Nick Milo, whose Linking Your Thinking (LYT) framework popularised MOCs, now ships the ACE scaffold: three top-level folders covering knowledge, time, and projects [8]. And Steph Ango — Obsidian's CEO — runs ~4 folders and navigates via Quick Switcher and backlinks, not the file tree.
"A file either is in a folder, or it isn't. You can't have a file that exists in two folders at the same time… As your project grows and changes, folders have a hard time keeping up." — Tim Miller · Obsidian Rocks [1]
03 · adoption-ordered roadmap
Capture → link → emerge. Not design → capture.
The single biggest mistake is trying to design the perfect structure before you have notes in it. Each card below is the same vault at a different scale — watch the graph thicken.
One link rule.
Add at least one [[wikilink]] to every note before you close it. Don't build folders. Don't build MOCs. Don't perfect tags. [10]
The squeeze point.
Around 50–100 notes the orphans become impossible to ignore. That's the signal — not earlier. Aidan Helfant's rule: "think and link first." [12]
Exactly three.
Create three MOCs covering your broadest active topics — not perfect, just three. Dump → Lump → Jump: paste, group, leave it, come back. [12]
Backlinks become the UI.
Open the Backlinks pane (right sidebar). Linked Mentions = who pointed at me. Unlinked Mentions = who said my name in plain text. Navigation = Quick Switcher + backlinks + MOCs. [4] [13]
Only if you need one.
Once you have several MOCs, decide if you want a top-level container system. Three mainstream choices. Or stick with minimal. [8]
Atlas, Calendar, Efforts
Best for: PKM-heavy users already thinking in MOCs. [8]
Requires you to internalise the STIR model.
Projects, Areas, Resources, Archives
Best for: Cross-tool productivity (Drive, Notion too). [14]
Fights Obsidian's graph nature — note in one bucket only. [15]
Minimal · 3–4 admin folders
Best for: Default for most users; lets links do the work. [2]
Requires link discipline.
04 · backlinks vs unlinked mentions
Two arrows. One you wrote. One Obsidian found.
Linked mentions are the bracket pair you committed to. Unlinked mentions are free — every prose occurrence of the note's title, surfaced by the same pane.
LINKED MENTION
Trigger: you wrote [[Acme Migration]] in the source note.
Cost: one bracket pair at write-time.
Use for: explicit, claimed connections.
Create a stub note titled with your project's recurring proper noun — say Acme Migration. Every future daily note that mentions it in prose appears in the stub's Unlinked Mentions pane automatically. No link discipline required.
— pragmatic trick · Learning Aloud [13]
05 · MOCs vs tags
Complementary. Not competing.
MOC = curated index page
A hand-curated, ordered, contextual index page you write commentary on. Frozen state until you update it. Supports description, ordering, formatting that tags can't.
"MoC lets you describe the document you are linking to, and also order and format the documents in a manner appropriate to the work at hand." [6]
Tag = signal for live query
A signal consumed by search / Bases / Dataview for live queries. Best for status (#draft, #needs-link), type (#person, #book), or filter dimensions.
"Tags are signals, not structure — use them for discovery, not primary organization." [3]
User Orand's pragmatic ladder: "start with tags and only add a MOC once a particular tag area becomes large enough to warrant the extra effort." [6]
06 · common traps
Seven warning nodes. And the green edge out.
Designing the folder tree before writing notes.
Capture first. Folders, if any, emerge from real friction. [12]
Nesting folders 4+ levels deep.
Cap at 2–3 levels; let MOCs handle the rest. [3]
200 unused topic tags from week 1.
Delete them. Tags = status/type, not topic. [3]
Building MOCs before you have ≥10 notes on the topic.
Premature — you're guessing the shape. Wait for the squeeze. [12]
Optimising for a pretty graph view.
"Creating for the graph" leads to forced links between unrelated ideas. The graph is a side-effect, not the goal. [16]
Circular backlinks created just to look connected.
Avoid Note A ↔ Note B loops with no semantic relationship. [17]
Hundreds of orphan notes from rapid capture.
Use #needs-link weekly batch; prune via Graph View. [10]
07 · concrete next moves
A directed path. Five steps.
-
today
Enable the rule — every new note gets
[[at least one link]]before close. Add#needs-linkfor emergencies. -
this week
Open the Backlinks pane and read its Unlinked Mentions section for your three most-active notes. Promote any worth keeping.
-
at ~100 notes
Create exactly three MOCs (
MOC-<broad topic>) and Dump → Lump → Jump every orphan into one. -
only when you have ≥5 MOCs
Decide on a scaffold (ACE / minimal / PARA). Until then, don't.
-
never
Re-org folders to chase a perfect tree. Refactor links instead.
graph perimeter · 17 sources
External nodes. The edges of the vault.
Every claim above carries the citation marker next to it. Listed here in order — origin domain, what they said, what kind of source.
Tim Miller uses only 5 workflow folders (FINVA); folders force exclusivity that hurts as projects grow.
Steph Ango (Obsidian CEO) uses ~4 folders and organises via links/properties; navigates with Quick Switcher and backlinks, not the file tree.
Recommends shallow folders + MOCs + tags as discovery signals; tags are signals not structure; cap nesting at ~2 levels.
Official Obsidian docs define backlinks pane with Linked Mentions and Unlinked Mentions sections.
MOCs and tags are complementary not opposing; MOCs are curated frozen state, tags qualify status.
Forum: MOCs allow description/ordering/formatting that tags can't; start with tags and add MOCs only when needed.
MOCs are "folders on steroids" — a note can appear in multiple MOCs unlike folders; types: basic, contextual, meta-MOCs.
Nick Milo's ACE = Atlas, Calendar, Efforts; based on STIR model; Relatedness via links not folders.
LYT framework popularised MOCs; community testimony of going folderless then re-adding a few folders for balance.
System for linking 500 orphan notes: one wikilink per new note, Graph View to spot orphans, 3 MOCs to absorb them.
Official Obsidian: linking notes is the platform's core power; non-existent links appear muted, acting as future seeds.
Five-level MOC adoption progression: isolated notes → linking → first MOC → MOC-of-MOCs → Home note. "Think and link first."
Strategic title selection makes unlinked mentions surface free connections; low-maintenance retrieval layer.
PARA (Projects, Areas, Resources, Archives) — Tiago Forte's cross-tool method, frequently used as an Obsidian scaffold.
Recommends against strict PARA in Obsidian; folder exclusivity fights graph structure; selective borrowing only.
Cautions against "creating for the graph" — writing pointless notes or forcing links just to see new dots.
Avoid circular backlinks (A→B, B→A with no semantic value) as a backlink antipattern.
adjacent in the expedition
Four other chapters. Same vault, different layer.
Properties & tagging for queryable notes
How to add structured metadata so Bases and Dataview can query — when to reach for a property, when a tag, and the naming rules that keep both useful.
expedition · chapterBases: turn existing reference notes into live views
Convert a folder or tag of reference notes into a live, editable, filterable view using Obsidian Bases — the .base format, ready-to-steal recipes, formula language.
Low-friction capture & daily-note habits
The smallest viable Obsidian capture loop — five-line daily template, one hotkey, one mobile pathway, one weekly pass — over four weeks.
survey · chapterCore + community plugins & keyboard-driven navigation
Which core plugins to enable, the tight community-plugin starter pack, and the hotkey patterns that turn a beginner into a keyboard-first intermediate.