Obsidian Mastery February 20, 2026
Obsidian From Scratch: Your First Vault, Done Right
This is Part 1 of the Obsidian Mastery Series. View all 6 parts →
The most common Obsidian mistake I see is not a mistake with Obsidian at all. It is a mistake with the starting point.
Someone discovers Obsidian, watches fifteen YouTube tutorials, downloads a starter vault from a creator they admire, and tries to inhabit it. They spend two weeks trying to understand someone else’s folder structure, someone else’s tagging system, someone else’s plugin stack, and then conclude that Obsidian is too complicated or that they are not the kind of person who can use it effectively.
The vault was not theirs. Of course it did not fit.
Obsidian is not an app with a correct configuration. It is a blank canvas. Its power comes precisely from this blankness, it can be built around how you actually think rather than how some creator on YouTube thinks. But a blank canvas requires decisions, and most people who are new to Obsidian want to be told what to do.
Here is what to do.
Day One: Create Three Things Only
On day one, create exactly three things and nothing else.
- A folder called Inbox
- A folder called Notes
- A daily note template with three fields: Date, What I’m working on today, What I noticed
That is it. No elaborate folder hierarchy. No plugin stack. No PARA implementation. No tagging system. No maps of content. Just these three things.
You will be tempted to do more. Do not. The reason to start small is not minimalism as an aesthetic, it is that you do not yet know what your system needs. Your needs emerge from use. Every elaborate structure you build before using the system is built on speculation, not evidence. Most of it will turn out wrong for you, and the effort of building it will be demoralizing when you dismantle it.
The 14-Day Rule
Use your three things, only your three things, for two weeks. Here is what the two weeks look like:
Every idea, observation, link, and fragment goes to Inbox. No filing, no tagging, no organizing. Just get it in.
Every day, write two sentences in your daily note. What you are working on today. What you noticed yesterday that you have not yet written down. Nothing more. This is not journaling. It is a lightweight log that keeps the vault alive.
Every few days, process Inbox. Read each item, ask why you saved it, add one sentence of context if needed, move it to Notes. Delete anything that no longer seems worth keeping. This takes twenty minutes.
At the end of two weeks, your Inbox will tell you what your system actually needs. Look at what naturally accumulated. What categories did things fall into? What did you search for and not find? What connections did you wish you could make? Those patterns are your design brief for the next layer.
Three Questions That Determine Your Structure
After two weeks, answer these three questions before adding anything to your vault setup.
What do you actually put in here? Look at what has accumulated. Not what you planned to capture, what is actually there. Build your structure around your actual behavior, not your aspirational behavior.
What do you actually retrieve? When you have searched for something, what kind of thing was it? Notes from a specific project? Ideas on a topic you are developing? Reference material? Your retrieval patterns tell you where your system needs to be strongest.
Where is the friction? What have you wanted to do in the vault that you could not do easily? Add structure only in response to real friction, never in anticipation of hypothetical friction.
The Plugin Rule
Add a plugin only when you have identified a specific limitation in your current workflow that the plugin would solve. Not because a plugin sounds interesting. Not because you saw it in a video. Only when you have a real problem that requires a real solution.
For someone starting out, three plugins are worth knowing: Templater (for note templates that ask you questions), Dataview (for dynamic note queries), and Calendar (for daily note navigation). Everything else can wait until you know you need it.
Your first vault should be simple enough to understand completely and honest enough to reflect how you actually work. Build from there. The elaboration will come naturally as your needs become clear, not before.
Next in series: Folders vs. Links: The Design Decision That Changes Everything →
Suggested reading
Where to Go Next
Continue with the most relevant essays, key site pages, and trusted references.
Read Next
Core Pages
Trusted Sources
The Weekly Field Note
Ideas worth thinking about — in your inbox.
No noise. One insight per week on knowledge systems, creative output, and building with clarity. Join The Field Note
Part of the system — Stage II · Build
Pillar 04: Obsidian Mastery
How do I structure my vault?