My Obsidian Workflow

Overview

This workflow combines the PARA method with hierarchical note-taking using dot notation in Obsidian. It leverages several plugins to create an efficient and organized system for managing notes and tasks.

File Structure

The file structure follows the PARA method, using single-letter prefixes (except for archives):

• p. for Projects
• a. for Areas
• r. for Resources
• archive. for Archive

Examples:

• p.write-novel
• a.health
• r.writing-tips
• archive.p.completed-project

Hierarchical Organization

Topics and subtopics are organized using dot notation:

• p.write-novel.characters
• p.write-novel.characters.protagonist
• a.health.exercise
• r.writing-tips.dialogue

Archiving

When a project, area, or resource is completed or no longer active, it's moved to the archive by adding archive. at the beginning of the file name:

• archive.p.completed-project
• archive.r.outdated-resource

Daily Workflow

1. Inbox: The root file serves as an inbox for quick note-taking and idea capture. The "Homepage" plugin ensures that root is always opened and pinned on Obsidian launch, providing easy access to the inbox.

2. Note Retrieval: The primary search tool is The Lookup function, with the native Obsidian search function to search through the contents of the files.

3. Task Management: Tasks are managed using the "Tasks" plugin. All tasks are added at the topic level, which is directly below the PARA files in the hierarchy. For example, tasks relating to my health should be located inside the a.health file.

File Naming Convention and Properties

File Name Formatting

• Always use lowercase letters
• Replace spaces with hyphens (-)
• Use single-letter or short names where it makes sense
  • Example for work meeting notes with m. as prefix: p.work-project.m.workshop-2024-09-03

Note Properties

All notes contain the following properties:

1. title

   • The displayed note title in the Tree and Lookup
   • Customizable in plugin settings

2. desc

   • A short, single-sentence description of the note
   • Displayed while searching for a note with Lookup
   • Customizable in plugin settings

3. created

   • A date field indicating when the file was created

4. tags

   • Obsidian's native tagging system

Example of properties in a note:

---
title: Workshop Summary
desc: Key takeaways from the 2024 project planning workshop
created: 2024-09-03
tags: [work, planning, workshop]
---

Tips for Using This System

1. Use the Lookup function frequently to quickly access notes within your hierarchical structure.

2. Regularly review and process notes in the root file, moving them to appropriate locations in your PARA structure.

3. Keep task management streamlined by consistently adding tasks at the topic level.

4. Periodically review your projects, areas, and resources to determine if any should be moved to the archive.

5. Utilize Obsidian's linking features to create connections between related notes across your PARA categories and hierarchy.