FYI, Tiago’s book came out and I’m completely happy with it so far at the $15 price point for the Kindle version. Paired with his YouTube videos, I like his much more app-agnostic approach and the introductory chapter really changes my perspective of him. I previously ignored PARA simply because I didn’t like the “online course huckster” model, but I can get behind a book that doesn’t cost me $1000+ to get into. Anyway, I’m sure you’ve stayed on top of this, but if you haven’t seen his book, it’s worth checking out!
The book was engaging but I’m having trouble applying it to my vault.
I have thought a great deal about implementing P.A.R.A. in my workflow and have come up with the following:
- Projects: exists in my task manager (Things3) and in Obsidian (indexed in Devonthink) and mostly contains courses I teach and administrative projects I have as a director of studies.
- Areas: In Obsidian (indexed in Devonthink) and contains my notes on topics of interest. Mostly topics related to my field of study. But of course, also contains a lot of personal stuff (family-related)
- Resources: Might only be in Devonthink (so that Sync in Obsidian won’t be a problem). And contains files of all kind. Mostly templates for the courses I teach with presentations, exercises etc in all kinds of document-types (docx, keynote etc.). These I can link to with DevonThink URLs if I need them in Obsidian or Things3. What about my PDFs in Zotero - they might go here as well or maybe I should change to just use Devonthink for PDFs and only use Zotero when I actually need to write a research article or similar some day. Have to think on that one.
- Archive: Might stay only in Devonthink.
Any comments/ideas about this setup?
This is actually inspiring. Currently, I use a single folder structure for my PARA system but it limits me to apps that understand folder structures. The way you do it might actually be the only functional option for systems kept in apps like Logseq or Supernotes that don’t really do folders.
I came accross the P.A.R.A. only shortly after looking in to Zettelkasten, which was a concept igot hooked last year.
I also looked into the Lyt Kit.
Actually what PARA and Lyt Kit are missing, at least to my taste is a greater sense of order and also one point to mentions is the depth of nesting folders. (especially in Lyt Kit).
PARA is to broad and doesnt suggest and kind of structure inside the main folders. Lyt Kit has spaces and therefor will cause too deep nested folders.
I implemented a kind of JohnnyDecimal system before. It was a German author who wrote about his concept of agile files and is suggesting “actionable categories”. This was very unique view and I’ve never come across that concept in the English realm of productivity.
The basic concept is that you dont name a file (in para it would be a process) with an actionable description. So there is no Tax category but the project is “filing income tax 2022” the actionable approach is missing in many of these concepts of categories. By doing so the risk of filing in more than one folder is apparent.
I also think Nick has a point in his calendar folder to store timebased information.
So my approach is to have an
- inbox (thats GTD)
- Calendar (time based notes / daily / journaling)
- projects (with project folder like “0002.51 Filing Taxes for 2022”)
- areas (with a decimal substructure like “5 Financial / 51 Filing Taxes”)
- Resources
- Archive ( in the book it was recommended to set an achrive folder within each section as in “5 Financial / 51 Filing Taxes/ Archive” which holds all the accomplished project folders) so maybe i skip archive as main folder and set that up as last folder “zzArchive”
Having a business made me use the numbering approach, because when satff asks me about something they need I can just tell them to look into Binder 51 or I tell them look within the 5 Section.
Also important is quick access so no more than 2 Folders deep. Having Areas just being named folders might work for more simple life styles but i figures it will get super messy in not time if you really use that approach for too long.
When I am done setting it fully up i might also post a starter kit.
the book I was mentioning: Prozessorientierte Ablage: Dokumentenmanagement-Projekte zum Erfolg führen. Praktischer Leitfaden für die Gestaltung einer modernen Ablagestruktur by Wolf Steinbrecher
Its German, so maybe not many will make use of it. But i think this is worth mentioning here.
looking forward to your comments on this.
I also use Obsidian for project and file management. One thing I’ve adopted is a convention of reserving the first digit of a folder’s two-digit prefix for the storage location:
0 = Obsidian
1 = File folder (on hard drive and iCloud-synced)
2 = Task-management (OmniFocus, in my case)
3 = Email folder
4 = DEVONthink databases
5 = Folder on One-Drive (typically shared with co-workers)
6 = Folder on SurfDrive (a research cloud service in the Netherlands)
I’m an academic, so have folders for Research writing projects (1), Teaching and supervision (2), University governance (3), Research project collaborations (4), Service to the profession outside my university (5), Personal (6), and Systems maintenance (7).
So, any folder in Obsidian about teaching starts with 02 (e.g., “02 Digital Ethics 2022-23”, whereas the OmniFocus project a project starts with 22 (e.g., “22 Grade midterms for Digital Ethics”)
For me, what is useful about this, is that if I’m running a search for folders, I can see right away whether something is a folder in my Obsidian vault (“02 Digital Ethics”) or on my hard drive (“12 Digital Ethics”).
I’ve not really decided yet whether to designate which of those folders are part of parent folders P.A.R.A., but I could easily do that. I toyed around with indicated that in the folder name (e.g., 12P for “teaching PROJECT on my hard drive”), but that got a bit fiddly. And there seemed to be a huge proliferation of folders. But I see the advantages of having just four P.A.R.A. parent-folders at the top level and then a small set of folders in an “ACTIVE Projects” folder and also a place (Archive) where projects and areas of responsibility go to R.I.P.
I’m also an academic and I keep courses I teach as active projects, the material I produce for the courses I keep in the resources folder.
I like the idea of having the location added to the system. As we all know, things spread over many locations. So that might be helpful.
Thanks for that suggestion.
Have been thinking about doing something similar all day… and this is just so nice and simple.
Thank you for sharing!
Very helpful link, thank you - Maggie’s cautionary note is very insightful too. I’m new to Obsidian and been down a few rabbit holes to get here.
I’ve been “using” PARA for a little over a year now after my GTD-like setup felt over-optimized for completing tasks without a clear alignment to value and completeness of a project. What I see I’ve done since then is slowly drift into a messy filesystem of stuff that’s lost the thread. Thank you all for reminding me of both the actionable focus of the layout and the distinction between Area/Resource. @cotemaxime gave me the ah ha moment: