Structural depth encodes real boundaries; bureaucratic…
Distinguish structural hierarchy depth (encoding real containment or inheritance) from bureaucratic depth (added for perceived tidiness) by asking what would break if you removed each level—keep only levels whose removal would destroy actual functional boundaries.
When This Fires
- Auditing hierarchy depth when navigation feels slow
- When a hierarchy has more than 4 levels and items take many clicks to reach
- During any hierarchy simplification effort
- When you notice that some levels exist "because that's how it's organized"
Common Failure Mode
Treating all depth as structural: "Each level is there for a reason." Maybe — but the reason might be "it seemed tidy when I created it" rather than "it encodes a genuine boundary." The "what breaks?" test separates retrospective justification from actual function.
The Protocol
For each level in your hierarchy: (1) Ask: "What functional boundary would be destroyed if this level were removed?" (2) If a specific boundary is identified (items that must be separated would become conflated) → structural depth. Keep. (3) If no boundary is identifiable (items could coexist at the parent level without confusion) → bureaucratic depth. Flatten. (4) After removing all bureaucratic depth, the remaining hierarchy is minimally deep and maximally functional.