Frequently asked questions about thinking, epistemology, and cognitive tools. 567 answers
Pick a significant outcome in your life from the past six months — a project that succeeded, a habit that collapsed, a relationship that shifted. Now trace the causal chain backward using exactly five links. Start with the outcome and ask 'What directly caused this?' for each link. Write each link.
Open the most developed map you have — your note system, project plan, team org chart, or personal knowledge graph. Pick any five nodes (concepts, people, tasks, whatever your map contains). For each node, list its current connections. Then ask: what is conspicuously absent? What should this node.
Choose a system you participate in — your team at work, your family, a community you belong to, even the tools in your daily workflow. List every element (person, tool, process, concept) on a blank page. Now draw every relationship you can identify. Use arrows to show direction: who influences.
Select a relationship map you already maintain — your professional network, your project dependency diagram, your personal knowledge graph, or even your mental model of your team. Now perform a temporal audit. Pick five relationships (edges) in that map and for each one, answer three questions:.
Map one transitive chain in your own life. Pick a relationship that matters to you — professional, personal, or intellectual — and trace how you arrived at it. Write down the intermediary: who introduced you, what event connected you, or what piece of knowledge led to the next. Now extend the.
Map one critical dependency in your life — a skill, a relationship, a tool, an income source, or an information channel that, if it disappeared tomorrow, would cause serious disruption. Now identify your current redundancy level for that dependency. Do you have zero backup paths (single point of.
Map one system you participate in — your team, your household, your project workflow, your social circle. Identify every node (person, tool, process) and draw the connections between them. Now ask: if I removed this one node or this one connection, what breaks? Find the single point whose removal.
Pick a system you navigate regularly — your team's reporting structure, your personal knowledge domains, the tools in your workflow. On paper or a whiteboard, draw each entity as a node (circle with a label). Then draw a line between any two nodes that have a direct relationship (reports to,.
Choose a domain you work in daily — your job responsibilities, a project you manage, a field you study, or even the contents of your home. Write down 20-30 items that belong to this domain, each on a separate line, in whatever order they come to mind. Now organize them into a hierarchy: group.
Pick any concept you work with regularly -- a skill, a project, a domain of knowledge. Write it in the center of a page. Above it, write two super-concepts it belongs to (the larger wholes it is part of). Below it, write three sub-concepts it contains (the smaller parts that compose it). Then pick.
Pick a problem you are currently working on. Write it down at three levels of abstraction: (1) the broadest framing — what is the category of problem this belongs to? (2) your current working framing — the level where you have been spending most of your time, (3) the most granular version — what.
Pick one project or goal you are currently working on. Write it at the top of a page. Decompose it into 2-3 sub-components. Then decompose each sub-component until you reach items that are concrete enough to do in a single sitting without further clarification. Circle those leaf nodes. Count how.
Pick one domain of your life — career, health, a side project, a relationship. Write down the single deepest assumption that everything else rests on. Not a tactic or a preference — the foundational belief. Now ask: if this root concept were wrong, what would collapse? What would suddenly make.
Take a hierarchy you use daily — your file system, your task manager, your note-taking structure, your email folders, your team org chart. Count the maximum depth: how many levels exist between the root and the deepest leaf? Now ask two questions for each intermediate level: (1) Does this level.
Pick one active project in your knowledge system. List five items nested inside it. For each, ask: what context does this item inherit from its container that would be lost if I moved it to the root level? Write down the invisible context that nesting provides. You will likely find that the.
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).
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.
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.
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.
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.
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.
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.
Perform a hierarchy audit of your current cognitive infrastructure. Select three systems you use daily — your task manager, your note-taking system, and your calendar or project plan. For each one, map the hierarchical structure: how many levels deep does it go, what are the root concepts, how.
Select one schema you hold with high confidence — a belief about how something works in your life, your team, or your field. Write it as a falsifiable claim: 'I believe [X] because [Y], and if [Z] happened, it would prove me wrong.' Then identify one observable test you could run in the next seven.