Frequently asked questions about thinking, epistemology, and cognitive tools. 190 answers
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.
Select three schemas you currently hold — about yourself, your work, or your field. For each one, write down the specific observation that would prove it wrong. If you cannot name a concrete falsifier, the schema is unfalsifiable in its current form. Rewrite it as a falsifiable claim: state it.
Pick one belief you hold about how something works — your learning process, your team's behavior, your market, your habits. Write it as a falsifiable prediction: 'If [schema] is true, then [observable outcome] should happen when [specific condition].' Design the smallest experiment you could run.
Select one schema you currently hold about a person, a system, or a recurring situation. Write down three specific, observable predictions that this schema implies. Be concrete: what will happen, when, under what conditions. Then observe. Over the next week, track which predictions are confirmed,.
Pick a belief you hold with high confidence — about your career, your relationships, or how the world works. Now generate three extreme scenarios where it would fail: the smallest possible case, the largest possible case, and the most adversarial case. For 'preparation beats talent,' try: a.
Choose one schema you currently rely on — a belief about how something works in your domain. Write it down in two or three sentences, as clearly as you can. Then explain it to someone: a colleague, a friend, a partner. Don't ask them if they agree. Ask them to tell you where it breaks. Write down.
Identify one schema you currently hold about how something works — in your career, a relationship, your health, or a creative practice. State it as a testable prediction: 'If I do X, then Y will happen within Z timeframe.' Commit to actually doing X within the next 48 hours. Before you act, write.
Choose a schema you currently rely on — a belief about how something works, a mental model for a recurring situation, or a rule you follow without questioning. Write it down as a single falsifiable claim. Now identify the smallest, most contained scenario where that claim should hold true. Test it.
Pick one belief you currently hold with high confidence — about your career, your team, a market trend, or a personal relationship. Write it as a single declarative statement. Now spend 10 minutes writing the strongest possible case against it. Do not write a weak objection you can easily dismiss..
List five schemas (beliefs, mental models, operating assumptions) you currently rely on. For each one, estimate two things: (1) how much damage you'd suffer if this schema is wrong, and (2) how much time and energy it would take to validate it properly. Now rank them by the ratio of potential.
Identify one schema you hold that cannot be tested through a single direct observation — something about your motivation, your relationships, your learning style, or your decision-making tendencies. Write the schema as a clear statement. Then generate five independent indicators that would be.
Select one schema you hold with high confidence — a mental model about how something works in your career, relationships, or thinking process. Write it down in two to three sentences. Then share it with someone you trust intellectually and ask them three questions: (1) What assumption does this.
Pick a schema you tested recently — a belief you put against reality in any form (a prediction, a conversation, an experiment). Write a validation record with five fields: (1) the schema as you held it before testing, (2) what you did to test it, (3) what you expected to happen, (4) what actually.
Select a schema you consider well-validated — something you have tested and believe to be true. Write it down as a single declarative statement. Then systematically probe its boundary conditions by answering six questions: (1) In what specific contexts have I actually tested this? (2) What.
Pick one belief you hold with high confidence — something you'd rate at 90% or above. Write it down as a testable claim. Now list the actual evidence you have for it: not impressions, not 'everyone knows this,' but specific observations, experiences, or data points. Count them. Then list any.
Identify a schema you hold with high confidence — a belief about yourself, your industry, your relationships, or your capabilities. Write it down as a clear proposition. Now design three specific observations or experiments that could falsify it. Not tests that would confirm it — tests that would.
Pick one schema you rely on daily — a belief about how your team communicates best, how you learn most effectively, or what makes a project succeed. Write down when you last deliberately tested it against fresh evidence. If the answer is 'I can't remember,' schedule a 15-minute review this week:.