Frequently asked questions about thinking, epistemology, and cognitive tools. 1431 answers
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
Open your knowledge system and find a category, tag, or folder where at least one item doesn't fully belong — it inherited assumptions from its parent that don't hold. Write a one-sentence override statement on that item: 'Unlike [parent category], this item [specific difference].' Notice how the.
You notice exceptions but leave them implicit, trusting your memory to handle the special cases. Over time, the exceptions multiply. You stop trusting the parent category because too many children violate its assumptions, but you never articulate which assumptions break or why. The hierarchy.
Sometimes a child needs to differ from its parent — explicit override is cleaner than implicit exception.
When your hierarchy becomes awkward restructure it rather than forcing things to fit.
When your hierarchy becomes awkward restructure it rather than forcing things to fit.
When your hierarchy becomes awkward restructure it rather than forcing things to fit.
When your hierarchy becomes awkward restructure it rather than forcing things to fit.
Open your primary knowledge system — notes app, vault, project folders, whatever you use. Find one category that has become a dumping ground: too many items, too many 'sort of fits here' entries, or subcategories that overlap. Write down three alternative ways you could split or restructure that.
Treating your hierarchy as sacred architecture instead of working scaffolding. You'll know you've fallen into this when you spend more time debating where something 'belongs' than engaging with the content itself. The second failure mode is the opposite: restructuring compulsively, chasing the.
When your hierarchy becomes awkward restructure it rather than forcing things to fit.
The same set of items can often be organized in several equally valid hierarchical structures. Each hierarchy foregrounds different relationships and obscures others. No single arrangement is canonical — the right hierarchy depends on what you are trying to see, find, or do. Recognizing this.
The same set of items can often be organized in several equally valid hierarchical structures. Each hierarchy foregrounds different relationships and obscures others. No single arrangement is canonical — the right hierarchy depends on what you are trying to see, find, or do. Recognizing this.
Pick a set of fifteen to twenty items you work with regularly — notes, projects, skills, books, contacts, tools. Write them on a list. Now organize them into three completely different hierarchies, each using a different organizing principle. For your notes, try organizing by topic, then by.
Hierarchy fixation — treating your current organization as the only possible one. You built a project folder structure organized by client. Now you need to find everything related to "data migration" across all clients, and you cannot, because the client hierarchy buries cross-cutting concerns..
The same set of items can often be organized in several equally valid hierarchical structures. Each hierarchy foregrounds different relationships and obscures others. No single arrangement is canonical — the right hierarchy depends on what you are trying to see, find, or do. Recognizing this.
What sits at the top of your hierarchy reflects what you consider most important.
Good hierarchies let people see the big picture first and drill into detail on demand.
Good hierarchies let people see the big picture first and drill into detail on demand.
Good hierarchies let people see the big picture first and drill into detail on demand.
Good hierarchies let people see the big picture first and drill into detail on demand.
Pick a document, note, or project plan you own that's longer than one page. Create three layers: Layer 1 — a single sentence that captures the whole thing. Layer 2 — one paragraph per major section (3-5 sections). Layer 3 — the full detail, accessible but not forced on anyone. Read only Layer 1.