Encoding First

Key techniques:

• Mind mapping (GRINDE method)
• Elaboration (connecting to prior knowledge)
• Chunking (grouping related information)
• Higher-order thinking (analyze, evaluate, create)

Retrieval (Secondary)

What it is: Accessing and recalling information from long-term memory.

Characteristics:

• Works better when encoding was done well
• Can strengthen existing memories
• Less effective for poorly encoded information
• Popular but often overemphasized

Common techniques:

• Flashcards (Anki, Quizlet)
• Active recall
• Spaced repetition
• Practice tests

The Problem with Retrieval-First

Why It's Popular But Limited

1. Easy to implement - Flashcards are simple to make
2. Feels productive - Lots of visible activity
3. Research-backed - Studies show retrieval helps (but context matters)
4. Measurable - Easy to track "cards reviewed"

The Hidden Cost

POOR ENCODING + LOTS OF RETRIEVAL =
  • Steep forgetting curve (forget quickly)
  • Endless review cycles (keep relearning)
  • Surface-level knowledge (recognize but can't apply)
  • Study time inflation (hours of reviewing)

STRONG ENCODING + MODERATE RETRIEVAL =
  • Shallow forgetting curve (forget slowly)
  • Fewer reviews needed (more efficient)
  • Deep understanding (can reason and apply)
  • Time savings (front-load effort, save later)

When User Mentions Flashcards or Active Recall

Default Response Pattern

1. Acknowledge the value of retrieval techniques
2. Assess whether encoding has been done first
3. Recommend encoding activities if missing
4. Position flashcards appropriately (for R-type info)

Key Questions to Ask

• "Have you created a mind map or concept summary first?"
• "Can you explain the underlying logic without notes?"
• "Are you trying to memorize concepts or arbitrary details?"
• "How deeply do you understand this before trying to recall it?"

The Encoding-First Workflow

Step 1: Classify Content (PACER)

Determine what type of information you're dealing with:

• P (Procedural) → Practice needed
• A (Analogous) → Critique needed
• C (Conceptual) → Mapping needed
• E (Evidence) → Store and apply
• R (Reference) → OK for flashcards

Step 2: Encode Properly

For Conceptual (C) content - the bulk of learning:

1. Create GRINDE mind map
2. Identify key relationships
3. Connect to existing knowledge
4. Explain in your own words
5. Test understanding, not recall

For Procedural (P) content:

1. Practice immediately
2. Get feedback
3. Refine through iteration
4. Don't just read about it

For Analogous (A) content:

1. Critique the analogy
2. Find limits
3. Integrate accurate parts
4. Discard inaccurate parts

Step 3: Then Consider Retrieval

Use flashcards/SRS for:

• Reference (R) information that must be recalled
• Truly arbitrary details after concepts are solid
• Minimal cards - resist the urge to flashcard everything

Don't use flashcards for:

• Conceptual understanding (use mapping instead)
• Procedural skills (practice instead)
• Anything you don't deeply understand yet

Key Messages

When User Wants to Make Flashcards

"Flashcards are great for Reference-type information, but let's first make sure you've encoded the underlying concepts. Can you create a quick mind map of how these ideas connect? That encoding work will make your flashcards much more effective."

When User Struggles to Remember

"If you're finding it hard to remember this, it might be an encoding issue, not a retrieval issue. Instead of more review, let's try building a stronger initial understanding through mind mapping and connecting to what you already know."

When User Has Too Many Flashcards

"Having hundreds of cards might actually indicate a problem—you might be trying to memorize things that should be understood instead. Let's identify what's truly Reference-type (flashcard-worthy) versus what should be mapped and understood."

The Leaky Bucket Metaphor

┌─────────────────────────────────────────────────────────────┐
│                    POOR ENCODING                             │
│                                                              │
│    Information │   ┌─────┐                                   │
│    Pouring In  │   │     │  ← Small bucket                   │
│        ↓       │   │     │                                   │
│        ▼       │   │ 💧💧 │  ← Lots of holes (leaking fast)  │
│    BUCKET      │   └──┬──┘                                   │
│                │      │                                      │
│                │    💧💧💧  ← Forgetting quickly             │
│                │                                             │
│    Solution: Pour FASTER (more retrieval)                    │
│    Result: Exhausting, never-ending review                   │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│                    STRONG ENCODING                           │
│                                                              │
│    Information │   ┌───────────┐                             │
│    Pouring In  │   │           │  ← Large bucket             │
│        ↓       │   │           │                             │
│        ▼       │   │  💧💧💧💧  │  ← Few holes (retains well) │
│    BUCKET      │   └─────┬─────┘                             │
│                │         │                                   │
│                │        💧  ← Slow, manageable forgetting    │
│                │                                             │
│    Solution: Build BIGGER bucket (better encoding)           │
│    Result: Less review needed, time saved                    │
└─────────────────────────────────────────────────────────────┘

Encoding Techniques Reference

Additional Resources

• For encoding vs retrieval scenarios, see examples.md