# Hierarchical Organization Hierarchical organization structures information as a tree: a root with branches that subdivide into smaller branches, each item having exactly one parent. This is the dominant metaphor in computing (file systems, folders) and traditional knowledge organization (library classification, outlines, org charts). [[Outliner]]s like [[Workflowy]] and traditional note apps use hierarchies. The strength is clarity: everything has one place, and you navigate by drilling down. The weakness is rigidity: real knowledge often doesn't fit neatly into trees—an idea may belong in multiple categories. The rise of [[Networked Thought]] and tools like [[Roam Research]], [[Obsidian]], and [[Logseq]] challenged pure hierarchies by emphasizing links over folders. In a network, items connect to many others without a single "correct" location. However, hierarchies remain valuable for certain tasks: project breakdown, sequential processes, and when you need clear structure. Modern PKM often combines both: hierarchical folders for broad organization, with links and tags creating a network within. The [[PARA method]] uses a light hierarchy (Projects, Areas, Resources, Archive) while encouraging linking. The question isn't hierarchy vs network—it's finding the right balance. ## Hierarchy vs Network ``` ┌─────────────────────────────────────────────────────────────┐ │ HIERARCHICAL vs NETWORKED ORGANIZATION │ ├─────────────────────────────────────────────────────────────┤ │ │ │ HIERARCHICAL (Tree) NETWORKED (Graph) │ │ │ │ Root ┌───┐ ┌───┐ │ │ │ │ A │───│ B │ │ │ ┌─────┼─────┐ └─┬─┘ └─┬─┘ │ │ │ │ │ │ ╲ │ │ │ ┌┴┐ ┌┴┐ ┌┴┐ │ ╲ │ │ │ │A│ │B│ │C│ ┌─┴─┐ ┌┴──┴┐ │ │ └┬┘ └─┘ └┬┘ │ C │──│ D │ │ │ ┌─┴─┐ ┌─┴─┐ └───┘ └────┘ │ │ │A1││A2│ │C1││C2│ │ │ └──┘└──┘ └──┘└──┘ Items link freely │ │ No single parent │ │ Each item has ONE parent │ │ Clear path from root │ │ │ └─────────────────────────────────────────────────────────────┘ ``` ## Characteristics | Aspect | Hierarchical | Networked | |--------|--------------|-----------| | **Structure** | Tree (one parent) | Graph (many connections) | | **Navigation** | Drill down | Follow links | | **Location** | One "correct" place | Multiple entry points | | **Strength** | Clarity, overview | Flexibility, discovery | | **Weakness** | Rigid, forced categorization | Can feel chaotic | | **Metaphor** | Filing cabinet | Brain/web | ## Examples of Hierarchies | Domain | Example | |--------|---------| | **File systems** | /Documents/Projects/2024/Report.docx | | **Outliners** | [[Workflowy]], [[DynaList]] | | **Library science** | Dewey Decimal, Library of Congress | | **Organizations** | Org charts, reporting structure | | **Biology** | Taxonomic classification | | **Writing** | Outlines, chapters, sections | ## When Hierarchies Work Well | Use Case | Why | |----------|-----| | **Project breakdown** | Clear parent-child tasks | | **Sequential processes** | Steps in order | | **Formal documents** | Chapters, sections, subsections | | **Organizational structure** | Reporting lines | | **Navigation menus** | Users expect tree structure | | **Archiving** | Clear categorization | ## When Hierarchies Fail | Problem | Description | |---------|-------------| | **Cross-cutting concerns** | Item fits multiple categories | | **Arbitrary placement** | Where does "machine learning in healthcare" go? | | **Maintenance burden** | Moving items requires restructuring | | **Discovery** | Must know the path to find things | | **Evolving knowledge** | Categories change over time | ## Hybrid Approaches | Approach | Description | | ---------------------------------------------------- | ----------------------------------------------- | | **Folders + Tags** | Hierarchy for structure, tags for cross-cutting | | **[[PARA method]]** | Light hierarchy (4 top levels) + links | | **[[Zettelkasten method]]** | Flat notes, rich linking | | **[[Map of Content (MoC)\|Maps of Content (MoCs)]]** | Maps of Content as navigational hierarchies | | **Johnny.Decimal** | Structured hierarchy with numbering | ## The "Folders vs Tags" Debate | Folders (Hierarchy) | Tags (Flat + Metadata) | |---------------------|------------------------| | One location per item | Multiple tags per item | | Clear structure | Flexible categorization | | Familiar mental model | Requires discipline | | Browsing-friendly | Search-friendly | ## Best Practices | Practice | Description | |----------|-------------| | **Shallow hierarchies** | 2-3 levels max | | **Use links liberally** | Connect across branches | | **Tags for cross-cutting** | When item fits multiple places | | **Don't over-categorize** | Resist premature structure | | **Let structure emerge** | Start flat, organize as patterns appear | ## References - Bush, V. (1945). "As We May Think" (critique of hierarchies) - https://en.wikipedia.org/wiki/Hierarchy ## Related - [[Networked Thought]] - [[Outliner]] - [[Workflowy]] - [[PARA method]] - [[Zettelkasten method]] - [[Personal Knowledge Management (PKM)]]