n general, only create new folders if you find yourself repeatedly coming back to save similar files in the same place, only to find that it doesn’t exist yet. You’ll know when it is time to create another level in the hierarchy rather than creating a vast extensive multi-layered tree before you need it.
Just like my book classification system, start broad and go more granular only if need be. Is future-proof and doesn't require buttloads of time.
So when you’re naming that phone bill, think about how you might look for it. Probably: By date (I want the January 2023 phone bill) By company (I want the XYZCorp phone bill) By type of document (I want a phone bill)
Naming Scheme should support findability.
Easy to File– You don’t want your filing system to be a huge, hierarchical maze. You want it to be fast and easy to save files so your system does not cause friction. Easy to Find – You want your system to make it easy to find the file or folder you need, either by poking through folders or using search. Reusable – Where possible, you want to use re-usable templates and naming conventions, both of which support the previous two goals.
Goals of good organization system for computer files
(~5:00) PARA is suitable for organizing files for deliverables.
Projects => On Top of Mind Areas => Longer Term Commitments Resources => Future Reference (Research Material, current Interests) Archive => Completed or on Hold
Questions: 1. In which project will this be most useful? 2. In which area will be most helpful? 3. Which resource does this belong to? If none of these ( in prioritization order), then the archives.
See Obsidian for example (screenshot)
(3:20) A good folder structure must mimic the way one works and make it easy to access the files one needs.