Teach Me

# Stage 4: PLAN — Design the Lesson

You have the concept map. Now plan HOW to deliver each session —
the flow, pacing, activities, and transitions.

## Session Architecture

Every teaching session (interactive or course tutorial) follows this arc:

```
    Engagement
    ▲
    │    ╭───╮         ╭───╮
    │   ╱     ╲       ╱     ╲         ╭──
    │  ╱       ╲     ╱       ╲       ╱
    │ ╱    ①    ╲   ╱    ③    ╲     ╱  ⑤
    │╱           ╲ ╱           ╲   ╱
    │      ②      ╳      ④      ╲ ╱
    └──────────────────────────────────→ Time

    ① Hook        (grab attention — why should I care?)
    ② Foundation   (build the concept — show, explain)
    ③ Checkpoint   (verify — Socratic question)
    ④ Depth        (go deeper — edge cases, connections)
    ⑤ Application  (learner DOES something)
```

Each peak is an engagement moment. Each valley is focused thinking.
Never have two valleys in a row (= lecturing too long without interaction).

## Step 1: Plan the Hook

The first 30 seconds determine whether the learner stays engaged.

```
HOOK TYPES (pick one per session):

SURPRISE HOOK — Show something unexpected
  "Watch: 0.1 + 0.2 in JavaScript gives... 0.30000000000000004. Why?"
  "Fire one electron at a time through two slits. It interferes with ITSELF."
  
PROBLEM HOOK — Present a real problem they can't solve yet
  "You need to test 50 user flows across 3 browsers. Manually, that's
   150 test runs. How would you automate this?"
  
RELEVANCE HOOK — Connect to something they care about
  "Every time you use HTTPS, quantum mechanics is protecting your data.
   Here's how."
  
MISCONCEPTION HOOK — Challenge something they think they know
  "Most people think Schrödinger's cat is about cats. It's actually
   about why quantum mechanics seems absurd when applied to big objects."
  
STORY HOOK — Start with a person or historical moment
  "In 1900, Max Planck made an assumption he called 'an act of despair.'
   It accidentally started a revolution."
```

## Step 2: Plan Each Concept Delivery

For each concept in this session, plan the Learning Loop:

```
LEARNING LOOP PLAN:

Concept: [name]
Duration: [minutes]

1. ANCHOR (30 sec)
   Connect to: [what the learner already knows]
   Phrase: "You know how [familiar thing] works? This is similar..."

2. SHOW (2-3 min)
   Example: [specific, concrete demonstration]
   Format: [code block / equation / visualization / thought experiment]
   Rule: Show FIRST, explain AFTER

3. EXPLAIN (2-3 min)
   Key insight: [the ONE thing they need to understand]
   Why it works this way: [reasoning, not just facts]
   What this enables: [what they can do now that they couldn't before]

4. PRACTICE (1-2 min)
   Checkpoint question: "[specific question to verify understanding]"
   Expected answer: [what a correct response looks like]
   If wrong: [which misconception, and how to redirect]
   If partial: [build on what they got right]

5. CONNECT (30 sec)
   Bridge to next concept: "Now that you know [this], let's see how
   it leads to [that]..."
```

## Step 3: Plan Transitions

The bridges BETWEEN concepts matter as much as the concepts themselves.

```
TRANSITION TYPES:

CONSEQUENCE: "Because [A] works this way, that creates a problem: [B]"
  Used when: B is a consequence or limitation of A
  Example: "Because light acts like particles AND waves, we need
   a new math to describe it — that's where wavefunctions come in."

GENERALIZATION: "[A] was a specific case. The general version is [B]"
  Used when: B extends or generalizes A
  Example: "We solved this for one dimension. What changes in 3D?"

CONTRAST: "We just saw [A]. Now here's the opposite situation: [B]"
  Used when: B contrasts with or complements A
  Example: "We saw how superposition works. Now what happens when
   you actually MEASURE a superposition?"

ZOOM: "We just saw the big picture. Let's zoom into [B]"
  Used when: B is a detail within A
  Example: "We know the wavefunction evolves over time. But HOW?
   That's what Schrödinger's equation tells us."

TOOL: "[A] showed us the problem. [B] is the tool to solve it."
  Used when: B is a technique or method for dealing with A
  Example: "We saw that potentials trap particles. The math for
   solving these trapped states is..."
```

## Step 4: Plan the Track Split

If the topic has math-dependent content, plan BOTH tracks:

```
CONCEPTUAL TRACK:
├── Same hooks and motivation
├── Analogies carry the weight (not equations)
├── Show results: "the math tells us X" without the derivation
├── Practice: thought experiments, predictions, qualitative reasoning
├── Visual: diagrams, simulations, animations
└── Goal: correct INTUITION, even without formalism

MATHEMATICAL TRACK:
├── Same hooks and motivation
├── Analogies to BUILD TOWARD formalism
├── Show the equation AFTER intuition is built
├── Always translate: "what this equation SAYS in English is..."
├── Practice: solve a problem, predict a value, verify numerically
├── Visual: plots, phase diagrams, function graphs
└── Goal: intuition + formal competence

IMPORTANT: Don't decide the track yet — you'll ask the learner
in Phase 1 (Orient). But have both versions READY.
```

## Step 5: Plan Error Handling

Anticipate where the learner will go wrong:

```
ERROR ANTICIPATION TABLE:

After teaching: [concept]

Likely mistake 1: [description]
  Why they make it: [root cause]
  Detection signal: [what they'll say/do that reveals the mistake]
  Error Sandwich response:
    VALIDATE: "[what's right about their thinking]"
    CORRECT:  "[the specific correction]"
    CONNECT:  "[why the correct version makes more sense]"

Likely mistake 2: [description]
  ...
```

## Step 6: Plan Pacing

```
PACING RULES:

INTERACTIVE MODE:
├── Each message: 100-300 words (shorter = better)
├── Max 1 code/equation block per message
├── Every message ends with action (question/challenge/prediction)
├── If learner responds quickly → speed up
├── If learner seems confused → slow down, add analogy
├── Never more than 2 messages without learner interaction
└── "Are you with me?" if unsure

COURSE MODE:
├── Each tutorial: 15-45 minutes
├── Each tutorial: ONE primary concept
├── Walkthrough: 3-6 steps max
├── Common Mistakes: 1-3 per tutorial
├── Challenge: extends (not repeats) the tutorial
└── Bridge: connects to next tutorial
```

## Lesson Plan Template

```
SESSION: [Title — action-oriented verb]
DURATION: [minutes]
PRIMARY CONCEPT: [one concept]
PREREQUISITES: [what learner must know already]
TRACK: [conceptual / mathematical / both ready]

1. HOOK (1 min):
   Type: [surprise / problem / relevance / misconception / story]
   Content: "[exact opening]"

2. CONCEPT DELIVERY (5-15 min):
   Anchor: "[connect to known]"
   Example: "[show first]"
   Explanation: "[explain after]"
   Key insight: "[the ONE thing]"

3. CHECKPOINT (1-2 min):
   Question: "[verify understanding]"
   Expected: "[correct response]"
   If wrong: "[redirect via Error Sandwich]"

4. DEPTH (3-5 min):
   Edge case / connection / "what if..." exploration

5. APPLICATION (3-5 min):
   Challenge: "[extends the concept]"
   Hint: "[scaffolded help]"
   Verification: "[how to check their answer]"

6. BRIDGE (30 sec):
   "[connects to next session]"

MILESTONE: "[what learner can DO after this]"
```