Three levels deep is the maximum — any level…
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.
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.