Frequently asked questions about thinking, epistemology, and cognitive tools. 1480 answers
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.
Building a hierarchy that hides instead of discloses. If users can't find the detail they need because your structure buried it too deep or used opaque labels, you've created a maze, not a hierarchy. Progressive disclosure fails when the 'progressive' part requires guessing where things are. The.
Good hierarchies let people see the big picture first and drill into detail on demand.
An item can be contained within a hierarchy level or merely referenced from it.
An item can be contained within a hierarchy level or merely referenced from it.
An item can be contained within a hierarchy level or merely referenced from it.
Open a current project document or note. Identify three pieces of information that are contained (they live inside this artifact and nowhere else) and three that are referenced (they point to something that exists independently). For each contained item, ask: should this actually be a reference to.
Containing everything produces bloated, unmaintainable artifacts — the 200-page requirements document nobody reads because updating one section means re-reviewing the whole thing. Referencing everything produces hollow shells — the project plan that's nothing but links, requiring six clicks to.
An item can be contained within a hierarchy level or merely referenced from it.
Lopsided hierarchies with very deep branches and very shallow ones indicate structural problems.
Lopsided hierarchies with very deep branches and very shallow ones indicate structural problems.
Lopsided hierarchies with very deep branches and very shallow ones indicate structural problems.
Pick your primary knowledge system — file folders, note app, bookmarks, whatever you use most. Map the depth of each top-level branch. Count levels. If the deepest branch is more than three times deeper than the shallowest, you have a balance problem. Write down what the imbalance reveals about.
Pursuing perfect symmetry. Balance doesn't mean every branch has the same depth. It means no branch is so deep that retrieval fails or so shallow that nuance is lost. People who chase uniform depth end up creating empty placeholder folders — structure without substance. Balance is about.
Lopsided hierarchies with very deep branches and very shallow ones indicate structural problems.