Hierarchical Organization
A tree-like structure for organizing information where each item has exactly one parent, creating clear paths from root to leaves.
Also known as: Tree Structure, Folder Hierarchy
Category: Methods
Tags: organizations, information-architecture, structure, pkm, note-taking
Explanation
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). Outliners 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.
Hierarchies work well for 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), and archiving (clear categorization). They fail when dealing with cross-cutting concerns (items fitting multiple categories), arbitrary placement decisions, maintenance burden (moving items requires restructuring), discovery limitations (must know the path to find things), and evolving knowledge (categories change over time).
Best practices include keeping hierarchies shallow (2-3 levels max), using links liberally to connect across branches, employing tags for cross-cutting concerns, avoiding over-categorization, and letting structure emerge organically rather than imposing it prematurely.
Related Concepts
← Back to all concepts