Frequently asked questions about thinking, epistemology, and cognitive tools. 1480 answers
Items nested inside a container share the context of that container.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Child items often inherit properties from their parent — be aware of what propagates.
Choose a hierarchy you operate within — your organization, your note-taking system, your file structure, or your belief system. Identify three properties that propagate from a higher level to a lower level. For each one, answer: (1) Is this property explicitly stated or implicitly assumed? (2).
Blind inheritance — accepting every property that propagates from parent to child without examining whether it fits the child context. This shows up as teams following organizational processes that make no sense for their specific work, as note-takers applying folder-level tags to notes where.
Child items often inherit properties from their parent — be aware of what propagates.
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.
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.