Three levels deep is the maximum — any level that does not enable a decision is noise
When navigation to any item requires remembering a path more than three levels deep, audit whether each nesting level provides unique decision-making value—if you cannot explain what decision a level enables, eliminate that level as noise.
Why This Is a Rule
Miller's research on working memory limits implies that a navigation path exceeding three decisions taxes recall: by the time you reach the fourth level, you may not remember why you chose the path you're on. Each level must earn its cognitive cost by enabling a unique decision — if a level doesn't help you make a different choice than you'd make without it, it's adding navigational friction without informational value.
The three-level threshold is the practical heuristic: most personal knowledge systems work well at three levels (domain → topic → item). Beyond three, the navigation becomes memory-dependent rather than recognition-based — you have to remember the path instead of recognizing the right choice at each level.
The decision-value test applies to each level independently: "What decision does this level enable?" Level 1: "Which domain am I in?" (Engineering vs. Personal) — clear decision. Level 2: "Which topic within that domain?" (API Design vs. Testing) — clear decision. Level 3: "Which specific item?" (the-spec-doc vs. the-test-plan) — clear decision. Level 4: what decision does it enable? If you can't articulate one, the level is noise.
When This Fires
- When any item requires more than 3 clicks to reach from the top level
- During hierarchy audits when evaluating depth
- When you can't find items despite knowing they exist
- When you have to "remember the path" to navigate rather than "recognize the choice"
Common Failure Mode
Adding a fourth level "for organization" without asking what decision it enables. "I'll add a 'Templates' subfolder under 'Engineering > API Design > Documentation'" — but does the 'Templates' level enable a decision you couldn't make at the 'Documentation' level? If the documentation folder has 5 items including 2 templates, the templates can live alongside the other items with a tag.
The Protocol
When navigation exceeds 3 levels: (1) For each level beyond 3, ask: "What unique decision does this level enable?" (2) If the level enables a clear, distinct choice → keep it (the hierarchy genuinely needs this depth here). (3) If no unique decision is identifiable → eliminate the level. Flatten its children into the parent. (4) After flattening, verify that retrieval works: can you find items at the shallower depth? Tags and search compensate for lost depth.