Video summary

The Ultimate Guide to File Organization: 5 Systems You Must Know

Main summary

Key takeaways

Educational

Main ideas / lessons

  • The video addresses the common problem of digital file overwhelm and the difficulty of finding specific documents.
  • It argues that a good folder structure should:
    • Reflect how you actually work
    • Make files easy to find and access
    • Reduce duplication, clutter, and “orphaned”/unplaced items
  • The speaker emphasizes using organizational systems to improve findability and reduce wasted time.
  • Multiple well-known systems are compared, showing different philosophies:
    • Folder-based: PARA, GTD, Johnny Decimal, Access
    • Link-based: Zettelkasten
    • Flat (naming + linking; folders minimized): flat file systems
  • The video concludes with the speaker’s reflections on which parts they like from each system—e.g., reference numbers, an “inbox/encounters” concept, thinking of folder paths as namespaces, and using metadata instead of moving files.

Methodologies / systems presented (detailed)

1) PARA (Thiago Forte) — folder-based, action + knowledge oriented

Core folder idea (4 areas):

  • Projects (active work / dishes you’re cooking now)
    • Immediate attention
  • Areas (ongoing responsibilities / items you access regularly)
    • Long-term commitments (e.g., finances, home, family)
  • Resources (things you may use later / “freezer” items)
    • Topics of interest, reference materials, research
  • Archives (completed or put-on-hold / “pantry” items)

How to decide where to store a new file (3 questions):

  1. Projects
    • Which project will this be most useful for?
    • If there’s a relevant active project, store it under that project.
  2. Areas
    • Which area will this be most useful for?
    • If it fits an area, store it there.
  3. Resources / Archives
    • Which resource does this belong to?
    • If it doesn’t fit a project or area, store it in the relevant resource, otherwise put it into archives.

2) Johnny Decimal System (John / John Noble, as referenced) — numbering + consistent categories

Three steps to build the system:

  1. Create high-level areas
    • Maximum 10 broad/high-level areas
    • Assign each area a number from 10 to 90
  2. Create categories within each area
    • Maximum 10 granular categories per area
    • Assign each category a number from 0 to 9
  3. Name files with the category.id numbering
    • Use a descriptive title
    • Add the corresponding area + category numbers, plus a dot and a sequential ID number
    • The reference number is placed at the beginning or end of the file name (as described)

Maintenance / enhancements mentioned:

  • Create a separate index file to track IDs.
  • Reference the category.id in email subjects to connect and locate related items later.
  • Implementation ideas:
    • Use metadata (e.g., in Obsidian), or
    • Use folders in Obsidian Explorer using the Johnny Decimal scheme.
  • For multi-project environments:
    • Add a project layer at the root with three-digit project IDs, then apply the area/category approach within each project folder.

3) Nick Milo’s ACCESS (ATLAS, Calendar, Cards, Extras, Sources, Spaces) (+ “inbox/unsorted” capture)

High-level concept:

  • ACCESS is designed for productivity and clarity by organizing information into a structured set of folders.

“Seventh folder” concept:

  • The video notes a “seventh folder” for unsorted items and suggests renaming it to something like “inbox/entries” (subtitle wording is unclear, but the idea is an unsorted capture).

Six main folders (+ capture concept):

  • Atlas
    • High-level nodes: maps of content, dashboards, overviews
  • Calendar
    • Time-based tracking: daily notes, meeting notes, plans, reviews, journals
  • Cards
    • Connected ideas/insights; notes about concepts, people, and things
  • Extras
    • Support materials: images, manuals, templates
    • Also for miscellaneous items that don’t fit elsewhere
  • Sources
    • External knowledge sources: articles, books, podcasts, videos
    • For citing/reference to original material
  • Spaces
    • Different areas of life (work, personal, hobbies)
    • Each space includes its own maps of content, areas, projects, support notes

Philosophy:

  • “Knowledge at the top, action at the bottom”
    • A clear separation meant to prevent misfiling and purpose overlap.

4) Flat file structure — minimize folder hierarchy; emphasize naming + linking

Definition:

  • Store all files and folders at the same level (avoid deep subfolder hierarchies).
  • Prioritize file naming conventions and linking rather than building complex folder trees.

Key advantage:

  • Reduces time spent creating/managing folder structures.
  • Makes it easier to find and link related items.

Important note (folders aren’t forbidden):

  • Folders can be used, but should typically remain top-level only.

Naming guidance given:

  • Use clear naming conventions; one example is starting filenames with the date in YYYY-MM-DD format.

Tools/examples referenced:

  • Systems mentioned as using flat structures include Rome, Brain, and loxac (spelling unclear in subtitles), plus mentions of namespaces and folder tree display features.

Relating to GTD filing (physical analogy included):

  • David Allen recommends filing physical reference documents alphabetically into labeled cabinets/folders—used here as an analogy for simpler digital organization.

5) Zettelkasten (Zettolcastan / ZK) — link-based knowledge graph; avoid “orphan notes”

Core idea emphasized:

  • New items must be placed somewhere in an existing chain.
    • This helps avoid “orphan notes.”

Additional handling mentioned:

  • Attachments can be managed as part of node handling.
  • Plugins/features mentioned (as tools to manage attachments), e.g.:
    • Folder node plugin in Obsidian to help manage attachments.

6) GTD (Getting Things Done) — action + reference filing (as described in the video)

How it’s portrayed for file organization:

  • Similar “reference cabinet” approach to PARA/access logic:
    • Organize reference information like a filing cabinet.
    • Track action via lists.

Also mentioned:

  • The “inbox” concept is valued similarly to an unsorted capture folder in note systems.

Final reflections (what the speaker says they like / how they apply ideas)

  • Likes Johnny Decimal because reference numbers create cross-platform connections (e.g., linking between docs, PKM, and emails).
  • Considering flat structures because they emphasize linking (important for PKM).
  • Likes Zettelkasten to avoid orphan notes.
  • Values “inbox/encounters” style capture folders:
    • Encounters in Nick Milo’s ACCESS
    • Inbox in GTD
  • Thinks of folder paths as a namespace / primary ontology rather than just storage locations.
  • Wants folders for attachments (using folder-note concepts / plugins like “folder node”).
  • Dislikes moving files between project folders over time; prefers using metadata instead (tied to “Brownfield” constraints—existing data and tool limitations such as sync behavior).
  • Concludes that organizing is broader than folders/names, including:
    • Tags, links, templates
    • Ontology / maps of content
    • Dynamic lists, daily notes, and geotags, etc.

Speakers / sources featured

  • Nick Milo — ACCESS system (ATLAS/Calendar/Cards/Extras/Sources/Spaces)
  • Thiago Forte — PARA method
  • David Allen — GTD (Getting Things Done)
  • John Noble — Johnny Decimal System (numbering scheme)
  • Zettelkasten creator(s) are not explicitly named in the subtitles, but Zettelkasten is referenced as a method (via “Zettolcastan/ZK”).
  • Aiden Alex — referenced in relation to a plugin idea (folder node plugin) for attachment handling

  • Johnny Decimal / PARA / GTD / Zettelkasten / flat file systems / Rome / Obsidian / Logseq/related tools are referenced as tools/systems rather than individual speakers.

  • The video’s narrator/speaker (not named in the subtitles) — provides the walkthrough, comparisons, and personal reflections.

Original video