Restructure at the friction point, in the moment…
Restructure hierarchies at the specific node causing friction during the moment you feel the friction, rather than conducting proactive system-wide reorganizations, to keep restructuring costs small and diagnostic signals fresh.
When This Fires
- When you experience navigation friction in a hierarchy (can't find something, wrong folder, confusing choice)
- Instead of scheduling "reorganization time" for your knowledge base
- When the instinct is "I need to redo my whole folder structure" (usually overkill)
- During any moment of hierarchy friction where the problem and fix are both clear
Common Failure Mode
Noting the friction and planning to "fix it later during the next reorganization." By later, the diagnostic signal — exactly what was wrong and where — has faded. You remember "the folder structure is messy" but not "I couldn't find the API spec because it was filed under 'Design' instead of 'Engineering.'" Fix it now while the signal is crisp.
The Protocol
When hierarchy friction occurs: (1) Notice the friction: what were you trying to find or file? Where did the hierarchy fail? (2) Fix the specific node now: move the item, rename the folder, flatten the unnecessary level, add the missing category — whatever resolves the friction. (3) Time budget: 30-60 seconds. If the fix would take longer, note it for your next review session. (4) Over time, friction-driven micro-restructuring converges on an optimized hierarchy without ever requiring a disruptive system-wide reorganization.