Pinker Teach For Understanding

Pinker: Teach for Understanding

Produce a change in what the learner can reconstruct and use, not merely a smooth presentation. Treat learners as intellectually capable people who do not yet share the expert's chunks, vocabulary, or background.

Choose the mode

• Explain the method: State Pinker's direct advice, his observable teaching practices, this workflow's derivations, independent instructional evidence, and important limits separately.
• Design: Create a lesson, explanation, worked example, exercise sequence, or course segment.
• Teach: Run a responsive tutoring exchange. Ask one useful diagnostic at a time and adapt to the learner's response.
• Audit: Locate where an existing lesson assumes knowledge, obscures its model, substitutes fluency for learning, or fails to test transfer.

Read references/teaching-evidence.md when attribution, research support, or a broad claim about Pinker matters. Read references/teaching-patterns.md for ready-to-use designs and audits.

Build the lesson

1. Define an observable destination

Name the phenomenon or consequential question and the performance expected afterward. Prefer outcomes such as explain, distinguish, predict, diagnose, apply, or critique. Do not use “understand” alone.

2. Diagnose the learner model

Establish the audience, purpose, prior knowledge, likely misconceptions, language needs, accessibility needs, time, and setting. When interaction is possible, use a short prequestion, prediction, miniature case, or paraphrase. Do not assume that imagining a novice defeats the curse of knowledge.

If the user has not supplied a live learner, state reasonable assumptions and mark them as assumptions. Provide diagnostic questions the user can run later.

3. Decompress expert chunks

Write down:

• the central claim in one sentence;
• the causal or logical chain, one link at a time;
• indispensable terms, acronyms, premises, and referents;
• prerequisites classified as known, teach now, or defer;
• a concrete instance for every important abstraction.

Define necessary technical vocabulary at first useful contact. Do not purge terminology that the learner must eventually command.

4. Construct a phenomenon-first explanation

Use this default arc when it fits:

1. Present a real observation, question, demonstration, case, or paradox.
2. Connect it to something the learner already knows.
3. Show a concrete case.
4. Name the general principle.
5. Walk through the mechanism or reasoning without hidden steps.
6. State the conclusion, scope, and live uncertainty.

Pair generalizations with examples and state what each example demonstrates. For an analogy, map the corresponding parts and identify where the analogy stops working. Do not use an entertaining analogy as a substitute for the mechanism.

5. Make epistemic structure visible

Distinguish claim, evidence, inference, assumptions, alternative explanations, uncertainty, and what could change the conclusion. Separate correlation from causation and an illustration from evidence. Preserve genuine controversy while staging detail so that a novice first gains a defensible orientation.

6. Require learner reasoning

Include at least one immediate check. For a lesson of roughly ten minutes or more, or any multi-part explanation, use checks at more than one level:

• Reconstruction: explain the mechanism in the learner's own words;
• Discrimination: distinguish it from a tempting near-miss;
• Prediction: infer an outcome before it is revealed;
• Application: use it in a new case;
• Critique: identify an assumption, counterexample, or rival account.

Do not use “Does that make sense?” as the only check. Recognition, assent, and verbal familiarity are weak evidence of learning.