How I manage projects and tasks in Obsidian, complete process and setup tour

I’ve penned an article detailing my two-year journey with Obsidian, and I’m eager to further delve into my daily interactions with this formidable tool, highlighting how I orchestrate my projects.

I’ll provide insights into my methods of folder structuring, information organization, and task management. Additionally, I’ll showcase the templates and plugins integral to crafting my system.

While I’ve navigated through various platforms, from ClickUp to Monday and Notion, my affinity for Obsidian and its future-proof approach stands unparalleled.

The goal isn’t for you to replicate my system verbatim, but rather to offer you inspiration and stimulate thoughtful consideration for tailoring your unique setup.

Let’s dive into it.

Embracing a holistic process philosophy

Having a comprehensive and interconnected view is paramount.

Centralizing information is at the heart of this philosophy. Envision the main project page as your command center. From this nexus, you should have immediate access to all vital details: contacts, notes, and tasks intricately linked to the project. It’s about having everything at your fingertips, ensuring no detail is overlooked.

Structuring the Vault: The PARA Method

My Personal Knowledge Management (PKM) system draws inspiration from the PARA (Projects, Areas, Resources, Archives) methodology, a brainchild of Tiago Forte. At the foundational level of my digital vault, you’ll find these four quintessential folders. For the scope of this discussion, our attention will be riveted on the ‘Projects’ folder.

While some may gravitate towards a tag-based organization reminiscent of Bear 2, I’ve found solace in a folder-based structure. It resonates with my cognitive style, offering a visual scaffolding that aids in precise organization.

Plugin integration: enhancing Obsidian’s prowess

While Obsidian’s inherent plain text capabilities are commendable, a sprinkle of plugins can amplify its functionality, ushering in efficiency.

Dataview

This is not just a plugin; it’s a game-changer. Dataview empowers users to conduct intricate queries on notes. Its beauty lies in its ability to cull specific data from notes systematically. Whether it’s crafting dynamic tables or curating lists of notes, Dataview simplifies the analytical process.

Auto Note Mover (Under Evaluation)

Automating tasks is the holy grail of productivity. The Auto Note Mover aims to streamline note organization, ushering active notes to their designated folders based on set criteria.

Decoding the Projects Folder

The guiding principle here is unambiguous: Each project translates to a singular folder, christened with a lucid name.

Within each project folder, you’ll discover distinct subfolders:

  • Notes: A repository for all project-centric notes and meeting notes.

  • Canvas: Dedicated space for Obsidian canvas storage.

  • Documents: A haven for project-related documents or annotations about cloud-stored documents.

The Keystone: Project File

At the heart of the project folder lies the project file, a comprehensive document delineating the project’s essence. This document is replete with:

  • Team composition and roles.

  • A succinct project synopsis.

  • Dataview queries to collate project-tied notes.

  • Dataview queries to aggregate pending tasks.

  • A compilation of canvases.

  • Links to pivotal project resources.

To further categorize the project, metadata (such as frontmatter) encompasses:

  • Project timelines: inception and culmination dates.

  • Relevant tags.

Additional attributes tailored to company-specific workflows can also be integrated. This document serves as a snapshot, encapsulating the entire project spectrum.

Here is the template I use for the project file:

---dueDate: tags:  - projectprojectCode: ---# {{title}}>[!info] Project description> Describe the project here>[!important] Project team>- Stakeholder : >- Leading team> - PM :> - Technical PM : >- A-Team :> - members>- Experts> - members>[!todo] ToDo> ```dataviewTASKFROM "1. PROJECTS/--Project--"WHERE !completed>[!todo] Done> ```dataviewTASKFROM "1. PROJECTS/--Project--/notes"WHERE completed>[!quote] Notes>```dataviewTable datefrom "1. PROJECTS/--Project--/notes"sort date desc## Informations

The sections “ToDo,” “Done,” and “Notes” utilize the Dataview plugin to aggregate lists from the subfolders directly onto this central page.

Notes

Notes serve as the foundational pillars, encapsulating nuanced details, valuable insights, and critical observations. Constructing well-organized and uniform notes is pivotal, ensuring both lucidity in content and ease in information retrieval. Every note related to a project is meticulously interconnected with the project’s primary note, further enhanced with specific tags for better categorization. I diligently craft a separate note for every pertinent piece of information concerning the project. This includes aspects such as:

  • Comprehensive research findings.

  • Key takeaways from phone calls.

  • Innovative ideas or brainstorming sessions.

  • Casual yet insightful discussions over a coffee break.

  • And other such significant interactions or revelations related to the project.

---date: {{date:YYYY-MM-DD}}aliases: []tags:  - noteproject: []author: url:---# {{title}}## Ressources-

Meetings

Meetings are integral components of collaborative endeavors, serving as platforms where ideas converge, strategies are forged, and decisions are made. They facilitate direct communication among team members, stakeholders, or partners, ensuring everyone is aligned with the project’s objectives and progress.

Whether it’s brainstorming sessions, progress reviews, or problem-solving discussions, meetings foster a sense of unity and shared purpose. However, for meetings to be truly effective, they must be well-organized, have a clear agenda, and be time-efficient.

Now that virtual meetings are becoming the norm, the essence of these gatherings remains unchanged: to drive collective understanding, action, and forward momentum.

I create a meeting note related to the main project file for each meeting that takes place. Participants are listed, as well as the agenda and key informations.

Tasks are also listed in the body of the note.

---date: {{date:YYYY-MM-DD}}tags:  - réunionparticipants:  - project: []---# {{title}}>[!example] Agenda>- >- >[!info] Key info>- >- ## Notes- ### ToDo### Ressources-

Canvas

In my project management process, Obsidian Canvas emerges as a versatile and innovative feature to elevate the way information can be visualized. Also it’s centralized and integrated in may project management system, so I don’t need to store files somewhere else.

I listed some use cases :

  • Visual brainstorming: Obsidian Canvas offers a digital canvas where ideas can flow freely. Instead of being confined to linear notes, we can brainstorm in a more visual and spatial manner alone or during meetings. This is especially beneficial during the initial stages of a project when creativity is at its peak, and ideas are abundant.

  • Mind mapping & flowcharts: For projects that require intricate planning and multiple phases, the canvas can be utilized to create mind maps and flowcharts. This not only gives a clear overview of the project’s trajectory but also helps in identifying potential challenges and interdependencies between tasks.

  • Integrating textual & visual data: The canvas feature allows a blend of text, diagrams, sketches, and more. This multimodal approach caters to different learning and processing styles, ensuring that all team members can engage with the project content effectively.

  • Dynamic Linking: One of Obsidian’s strengths is its ability to create interlinked notes. This feature extends to the canvas, allowing project managers to link specific sections of their visual representations to detailed notes, resources, or tasks. This interconnected web ensures that no detail is lost in translation and that every visual element has a comprehensive explanation attached.

The Resources Section: A Project’s Compendium

The Resources section stands as a crucial cornerstone in any project’s architecture.

Acting as a repository, it meticulously collates all materials and references tied to the project, ensuring that vital information is both accessible and organized. Within this section, one can find a range of content: from research documents, datasets, and multimedia files to external links, vendor details, and stakeholder communications. By centralizing these assets, the Resources section eliminates the inefficiencies of scattered information, enabling team members to swiftly locate and utilize the resources they need.

Furthermore, as projects evolve, this section provides a structured space to continuously update and augment materials, ensuring that the project always operates with the most current and relevant data at its disposal. In essence, the Resources section acts as the project’s knowledge hub, fostering efficiency, collaboration, and informed decision-making.

Managing Contacts and Interactions

Within my Obsidian vault, a dedicated section titled the “Ressources” folder plays a pivotal role in organizing my professional and personal interactions. This folder houses my bespoke Personal CRM (Customer Relationship Management) system, where I meticulously log and categorize every contact associated with my projects. Whether they are external stakeholders, collaborators, or colleagues from various departments, each individual’s details are systematically stored.

This structured approach provides dual benefits. Firstly, it ensures I have a consolidated directory of all individuals tied to different projects, streamlining communication and collaboration. Secondly, by harnessing the power of the Dataview plugin, I can execute specific queries to trace back every interaction, note, or meeting associated with a particular contact. This capability is invaluable, especially when I need to recall past discussions, decisions, or feedback related to a specific individual or group. In essence, my vault not only acts as a repository of information but also as a dynamic tool to trace and analyze past interactions, fostering efficient project management.

Conclusion

Project management requires a robust system that ensures clarity, organization, and efficiency. Obsidian, with its myriad of features and plugins, emerges as good option in this endeavor. From crafting well-structured notes and leveraging dynamic linking to harnessing the visual prowess of the Canvas feature, Obsidian becomes more than just a tool; it evolves into an extended cognitive workspace.

The detailed exploration of the “Ressources” folder, the Personal CRM system, and the profound impact of plugins like Dataview underscores the software’s adaptability. It’s not merely about documenting; it’s about creating an ecosystem where information is interconnected, easily accessible, and primed for collaboration.

The incorporation of a dedicated Resources section further amplifies the project’s comprehensiveness, ensuring that every asset, be it a research paper or a multimedia file, finds its rightful place, ready to be summoned at a moment’s notice.

In essence, this journey through Obsidian’s capabilities in the context of project management is not just a testament to the software’s robustness, but also an invitation to explore, adapt, and innovate. By sharing this setup and methodology, I hope that you, whether you are an Obsidian user or newcomer, find inspiration to tailor your systems.