Frequently asked questions about thinking, epistemology, and cognitive tools. 1480 answers
Define what makes a schema good — accuracy predictive power simplicity scope.
Define what makes a schema good — accuracy predictive power simplicity scope.
Define what makes a schema good — accuracy predictive power simplicity scope.
Define what makes a schema good — accuracy predictive power simplicity scope.
Pick one schema you actively rely on — a belief about how your industry works, a model of what motivates your team, a theory about your own productivity patterns. Score it on each of the six criteria from this lesson (accuracy, predictive power, scope, simplicity, fruitfulness, falsifiability).
Evaluating schemas only by how they feel. A schema that reduces anxiety ('Everything happens for a reason') or flatters your self-image ('I succeed because I work harder than everyone') can score high on emotional comfort and zero on predictive power. Comfort is not a quality criterion. If your.
Define what makes a schema good — accuracy predictive power simplicity scope.
List your most important schemas so you can maintain and improve them systematically.
Some schemas depend on others — map these dependencies to understand cascading effects.
Some schemas depend on others — map these dependencies to understand cascading effects.
Some schemas depend on others — map these dependencies to understand cascading effects.
Some schemas depend on others — map these dependencies to understand cascading effects.
Pick one schema you hold strongly — a belief about your career, your relationships, or your capabilities. Ask: what must be true for this schema to hold? Write down three underlying beliefs it depends on. Then pick one of those and repeat: what must be true for that belief to hold? You have just.
Treating each schema as an independent, freestanding belief. When you ignore dependencies, you are surprised by cascading failures — one belief changes and suddenly a half-dozen others feel unstable, and you cannot understand why. You think you are having an identity crisis when you are actually.
Some schemas depend on others — map these dependencies to understand cascading effects.
When two schemas contradict you need a meta-schema for deciding which to trust.
When two schemas contradict you need a meta-schema for deciding which to trust.
Identify two schemas you hold that have recently contradicted each other — they might sound like competing proverbs, opposing instincts, or clashing advice you've internalized from different mentors. Write each one as a clear declarative statement. Then write a third statement: the rule for when.
Resolving every conflict by picking a winner and discarding the loser. This feels clean but destroys nuance. Most schema conflicts exist because both schemas are valid in different contexts. The goal isn't to eliminate one — it's to build a meta-schema that routes to the right one based on.
When two schemas contradict you need a meta-schema for deciding which to trust.
You need rules for choosing which schema to apply in a given situation.
You need rules for choosing which schema to apply in a given situation.
You need rules for choosing which schema to apply in a given situation.
Pick a real decision you're currently facing. List every schema (mental model, framework, lens) you could apply to it — aim for at least four. For each, write one sentence: what would this schema optimize for? Then answer three selection questions: (1) What is the cost of being wrong? (2) How fast.