Obsidian knowledge management
How do I use Obsidian to build a linked knowledge management system?
Projekt-Plan
Why: Without a clear goal, your vault will become a digital graveyard of random notes.
How:
- Decide if your focus is on project management (PARA), academic research (Zettelkasten), or creative writing.
- Write down three primary questions you want your system to answer (e.g., 'What did I learn about AI this month?').
- Identify your main information sources (Books, Podcasts, Web Articles).
Done when: You have a written 'Mission Statement' for your vault in a simple text file.
Why: A framework prevents 'folder fatigue' and provides a logical home for every piece of information.
How:
- Use the PARA Method (Projects, Areas, Resources, Archives) if you are action-oriented.
- Use the Zettelkasten Method (Inbox, Literature, Permanent) if you focus on long-term learning and connecting ideas.
- Adopt a 'Folder-Light' approach, relying on links and tags rather than deep hierarchies.
Done when: A decision is made between PARA, Zettelkasten, or a hybrid model.
Why: Analyzing existing workflows prevents you from carrying over bad habits into the new system.
How:
- List where your notes currently live (Apple Notes, Notion, Paper).
- Identify the biggest pain point (e.g., 'I can't find anything' or 'I never revisit my notes').
- Commit to a 'Capture' method that takes less than 10 seconds.
Done when: You have a list of 3 friction points to solve with Obsidian.
Why: Obsidian stores files locally in Markdown, ensuring your data remains yours forever.
How:
- Download the installer from the official website.
- Create a new folder on your hard drive named 'MyKnowledgeVault'.
- Open this folder as a 'Vault' in Obsidian.
Done when: Obsidian is open and showing an empty vault.
Why: Proper settings ensure a distraction-free writing environment and consistent file linking.
How:
- Enable 'Properties' in the editor view for metadata management.
- Set 'Default location for new notes' to a specific 'Inbox' folder.
- Enable 'WikiLinks' format for easier internal linking (e.g., [[Note Name]]).
Done when: Settings are adjusted to support a linked-note workflow.
Why: Folders should be broad categories, while links handle the specific connections.
How:
- Create an '00_Inbox' folder for unprocessed notes.
- Create a '10_Sources' folder for literature and meeting notes.
- Create a '20_Notes' folder for your own processed thoughts.
- Create an '80_Templates' folder for automation.
Done when: Your sidebar shows a clean, top-level folder structure.
Why: Automation via templates saves time and ensures consistent metadata (Properties) across notes.
How:
- Go to Settings > Community Plugins > Browse.
- Search for and install 'Templater'.
- Enable the plugin and set the 'Template folder location' to your '80_Templates' folder.
Done when: Templater is active and pointed to your templates folder.
Why: Dataview turns your vault into a database, allowing you to create automated lists and tables.
How:
- Install 'Dataview' from the Community Plugins gallery.
- Enable 'JavaScript Queries' in the Dataview settings for advanced functionality.
- This will later allow you to see 'All notes tagged with #research' automatically.
Done when: Dataview is installed and enabled.
Why: Literature notes capture external information while keeping it separate from your own original ideas.
How:
- Create a new file in '80_Templates' called 'T_LiteratureNote'.
- Add Properties: 'Author', 'Source_URL', 'Topic', 'Date_Captured'.
- Add a section for 'Key Takeaways' and 'Quotes'.
Done when: A reusable template for external content exists.
Why: Permanent notes are 'atomic'—one idea per note—which makes them easier to link and reuse.
How:
- Create 'T_PermanentNote' in your templates folder.
- Include a 'Links' property to connect it to broader topics.
- Add a 'References' section at the bottom to link back to the original Literature Note.
Done when: A template for your own synthesized ideas is ready.
Why: Over-tagging leads to clutter; linking creates a neural network of knowledge.
How:
- Use Tags for status (e.g., #to-process, #draft) or high-level categories.
- Use Links ([[Note]]) for concepts and relationships.
- Avoid using tags for topics that could be their own notes.
Done when: You have a 1-page 'Style Guide' note in your vault.
Why: Testing with real data reveals if your templates and folders actually work in practice.
How:
- Pick 5 articles or book highlights you've recently read.
- Use your 'Literature Note' template to summarize them.
- Extract at least one 'Permanent Note' (original thought) from each.
Done when: Your vault contains at least 10 interconnected notes.
Why: Linking is the core of a PKM; it allows for the emergence of new insights.
How:
- Open a Permanent Note.
- Find a concept that relates to another note.
- Type '[[' and select the related note to create a bidirectional link.
Done when: You can navigate between three notes without using the file explorer.
Why: A system only works if it survives daily life.
How:
- Use Obsidian exclusively for all new notes for one week.
- Do not change the structure during this week; just take notes.
- Note down every time you feel 'stuck' or don't know where to put something.
Done when: You have a list of 'Friction Points' after 7 days of active use.
Why: MOCs act as entry points or 'hubs' for complex topics, preventing you from getting lost in the graph.
How:
- Create a note named 'MOC [Your Topic]'.
- Use Dataview or manual links to list all notes related to this topic.
- Organize the links logically (e.g., by sub-topic or importance).
Done when: You have one central hub note that organizes at least 5 related notes.
Why: Regular maintenance prevents the 'Inbox' from overflowing and ensures links are maintained.
How:
- Set a recurring calendar event for 30 minutes every Sunday.
- Empty the '00_Inbox' by processing notes into 'Sources' or 'Permanent'.
- Check the 'Graph View' for isolated notes (orphans) and link them.
Done when: A recurring 'Review' task is added to your calendar.
Why: Local files are vulnerable to hardware failure or accidental deletion.
How:
- Use a generic cloud sync service (like a private cloud folder) to keep files synced across devices.
- Alternatively, use a Git-based backup (e.g., 'Obsidian Git' plugin) for version control.
- Ensure the backup is automated and runs at least daily.
Done when: Your vault is synced to at least one external location.