Testing the Waters - AC.(PRO/PR).(0/ID) method?

Hello! Newbie here after seeing @brimwats apply the J.D. at a top level for their organization. I’m sort of in the middle of my testing week and wanted to share what I got. Plus, thank you very much @johnnydecimal, for this gem of a system.

Yet, I share the same worries posted here. I’m also coming from a PARA background, but the flow I have in my mind is more like; Areas-Projects-Items. Hence, my method took the shape of a AC.(PRO/PR).(0/ID) I guess.
I’ve tried to follow @ks84’s post, but I am cheating at certain points; e.g. the People (PPL) Area.

At the same time, I’m trying to reach for a whole life approach as well, if you haven’t figured that out b now :slight_smile: and I know things are not fleshed out and weird, but that’s why I’m here.
Things could get discarded/merged further. Seeking advice as to if I go through with this setup, what kind of trouble lie ahead—or rather, is there trouble ahead?

  • Proposed System - J.D. w/ AC.(PRO/PR).(ID0)
    • 10-19_Culture–CULT
    • 20-29_Finance&Legal–FnL
      • Archive
        • achivedProject/Category
      • 21_Bookkeeping
        • 100-199_Credit
          • 21.101_CreditReports
            • 21.101.001_Report#1
        • 200-299_Bills&Receipts&Tickets
        • 300-399_Templates
        • 400-499_Taxes
          • 21.401_Year’16
          • 21.402_Year’17
        • 500-599_Banking&Other
          • 21.501_Bank#1
            • 21.501.01_Statements
            • 21.501.02_Transactions
            • 21.501.03_Communications
            • 21.501.04_Data
          • 21.502_Bank#2
          • 21.503_Bank#3
          • 21.504_MobileCo.
        • 600-699_Insurance
          • 21.601_HealthInsurance
      • 22_Investing
        • 100-199_RealEstate
          • 22.101_Rental
        • 200-299_Goods&Products
        • 300-399_Statistics&Data
          • 22.301_ETFdb
      • 23_GOV %%could also be broken down by country; US, TR, CA%%
        • 100-199_OPT
          • 23.101_OPT#1
          • 23.102_OPT#2
      • 24_PrivyDocs %%(iCloud Drive>PersonalDocs)%%
        • 100-199_SocialMedia
        • 200-299_MobileScannerApp
    • 30-39_Health&Fitness–HnF
      • 31_Medical
    • 40-49_Intellect–INTL
      • 41_ePub %%stands for e-publications%%
        • 100-199_Books
        • 200-299_CalibreAutoAdd
        • 300-399_CalibreLibrary
        • 400-499_Zotero Library
      • 42_Academia
        • Archive
        • 00-99_Meta
        • 100-199_College
        • 200-299_GradSchool
          • Archive
          • 42.201_Admin
          • 42.202_FA’17_ARCHXXXX_Class1
            • Archive
            • 42.202.01_Admin
            • 42.202.02_Project#1
            • 42.202.03_Project#2
            • 42.202.04_Lectures&Notes
            • 42.202.05_AssignmentX
            • 42.202.06_Working
          • 42.209_SP’18_ARCHXXXX_Class2
          • 42.213_FA’18_ARCHXXXX_Class3
          • 42.223_FA’19_ARCHXXXX_Class4
          • 42.224_SP’20_ARCHXXXX_Class5
        • 300-399_Doctorate
        • 400-499_SchoolApplications
        • 500-599_HighSchool
      • 43_Courses&Training
        • 100-199_Course1
        • 200-299_Course2
        • 300-399_Coding
          • 10-19_Dictionaries
      • 44_PKM
        • 100-199_Obsidian
        • 200-299_Dendron
    • 50-59_People–PPL
      • 51_Family
        • 51.101_Mom
          • 50.101.01_MothersDay
        • 51.102_Dad
          • 51.102.02_FathersDay
      • 52_Friends
        • 52.101_Friend#1
        • 52.102_Friend#2
      • 53_Academics?
      • 54_BusinessContacts?
      • 55_HistoricalFigures?
    • 60-69_Practice–PRAC
      • 61_Examination
      • 62_Organizations
        • 100-199_Org#1
        • 200-299_Org#2
        • 300-399_Org#3
      • 63_CareerPlanning
        • 100-199_Application Packets
        • 63.101_CoverLetters
        • 200-299_CareerServices
        • 300-399_Resumes
        • 400-499_WorkSamples
      • 64_Portfolio
      • 65_ProWork
        • Archive
        • 65.100_Meta
        • 65.101_Employer#1
          • 100-199_Admin
          • 200-299_Clients
            • 65.101.201_Client#1
          • 300-399_Projects
            • 65.101.301_MarketingProject#1
            • 65.101.302_ConceptProject#1
        • 65.102_Employer#2
        • 65.103_Employer#3
      • 66_Design Resources
        • 100-199_TypeFaces
        • 200-299_ImageLibrary
        • 300-399_SoftwareResources
        • 400-499_Specs&ConstrxnMaterials
        • 500-599_Stamps-Signatures-Logos
        • 600-699_Statistics&Data
      • 67_Personal Projects
        • 100-199_Fiverr
        • 200-299_BrowserBookmarks
        • 300-399_OtherProjects

Hi there!

This sort of layout isn’t for me, but the beauty of the JD system, which is just some numbers and some decimal points, is that it’s infinitely flexible. I’ve long stopped thinking that there’s ‘a JD system’ that is the Right System. Everyone’s different, our brains all work in their own special ways.

The one guiding principle you should always check is this: will your system let you find things again. Because that’s the whole and only point, really. If it does that for you – and try to picture yourself in a year when you’ve forgotten how it’s set up and are just logically following the breadcrumbs – then go for it. :slight_smile:

Update: yeah, the more I think about this, the more I think this is just an interesting variant. Why not have AC.PRO.ID? The main advantage of PRO.AC.ID is that the hierarchy allows sharing of an individual project, which I do a lot at work. When you embed projects throughout the system that becomes more difficult. But this looks personal, you’re never going to do that, so it won’t matter.

1 Like

Ok alright, I get it, thank you for reminding me the over arching perspective btw. I think it works for now, but I gotta sleep over it.