Explain to Learn SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as explain-to-learn/SKILL.md.

---
name: explain-to-learn
description: "Learn by explaining: self-explanation research and the Feynman technique, explaining without notes, finding and studying gaps, plain-language rewrites, examples and non-examples, analogies with limits, teaching others, explanation templates and using AI as a questioning partner. Use whenever someone wants to understand a concept deeply, use the Feynman technique, check their understanding, prepare to teach or explain a topic, write an explainer or learn faster with AI quizzing."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/research-learning/explain-to-learn/
  category: productivity
  subcategory: research-learning
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-14"
---

# Explain to Learn

People often feel they understand something until they try to explain it. Explaining exposes gaps: undefined terms, skipped steps and vague links between ideas. Research on the self-explanation effect, starting with work by Michelene Chi and colleagues, found that learners who explained material to themselves while studying understood and solved problems better than those who did not. [Research, Chi et al. 1989] The popular Feynman technique, named after physicist Richard Feynman's reputation for clear explanation, turns this into a simple routine: explain the idea in plain words, find where the explanation breaks, go back to the source and simplify again.

This skill uses explanation to learn and to check understanding: plain-language explanations, gap finding, analogies and examples, teaching others, writing short explainers and using AI as a questioning partner rather than an answer machine.

## Operating principles
1. **Explain without notes first.** The gaps that appear are what you need to study.
2. **Plain words.** If you cannot say it simply, you have found a gap.
3. **Use examples and non-examples.** Show what the idea covers and what it does not.
4. **Connect to what you know.** Analogies link new ideas to familiar ones, with their limits stated.
5. **Teach to test.** Questions from others reveal weak spots fast.
6. **Iterate.** Explain, find gaps, study, explain again.

## The explain-to-learn loop
```
1. Pick one concept.
2. Explain it in writing or aloud, as if to a smart 14-year-old or a new colleague.
3. Mark where you hesitated, used jargon or skipped steps.
4. Return to sources to fill those gaps.
5. Rewrite the explanation more simply, with an example.
6. Test it: can someone else understand and use it?
```

## When to use, and when not to
Use it when learning new concepts, preparing to teach or present, checking whether you really understand a topic, onboarding into a new domain and writing explainers or documentation.

Don't use it alone for skills that need physical or hands-on practice; combine explanation with doing.

## Inputs
- The concept or topic.
- Source material.
- The audience you imagine or will actually teach.
- Your current understanding.

## Workflow

### Step 1. Choose a concept
Small enough to explain in a few minutes, such as "how canonical tags work" rather than "technical SEO".

### Step 2. Explain from memory
Write or record a plain explanation without looking at notes.

### Step 3. Find the gaps
Where you hesitated, used jargon, could not give an example or could not say why.

### Step 4. Study the gaps
Go back to sources, focusing only on what was missing.

### Step 5. Simplify
Rewrite with short sentences, defined terms, a concrete example and, if useful, an analogy with its limits.

### Step 6. Add examples and non-examples
Show cases where the idea applies and similar cases where it does not.

### Step 7. Test with others
Explain to a colleague, learner or study partner; ask them to explain it back or apply it.

### Step 8. Capture
Save the final explanation as a note or short explainer for future reuse.

## Explanation template
```
Concept: <name>
In one sentence: <plain definition>
Why it matters: <problem it solves>
How it works: <3 to 5 simple steps>
Example: <concrete case>
Not to be confused with: <similar idea and the difference>
Common mistake: <...>
Analogy (optional): <...> | Where the analogy breaks: <...>
```

## Example
```
Concept: Canonical tag
In one sentence: A canonical tag tells search engines which version of similar pages is the main one.
Why it matters: Without it, search engines may index duplicates or split signals across them.
How it works: 1) Add a link element with rel="canonical" to the page head. 2) Point it to the preferred URL. 3) Search engines usually consolidate signals to that URL, though they treat it as a strong hint, not an order.
Example: Product pages with ?color=red and ?color=blue point to the main product URL.
Not to be confused with: A redirect, which sends users and bots to another URL.
Common mistake: Canonicalising every page to the home page.
```

## Using AI as a learning partner
- Ask the AI to quiz you: "Ask me five questions about X, one at a time, and tell me where my answers are incomplete."
- Ask it to play a confused learner: "Act as a new marketer; ask questions about my explanation."
- Ask for an analogy, then ask where the analogy fails.
- Verify facts the AI provides against reliable sources.
- Write your own explanations; reading AI explanations alone gives an illusion of understanding.

## Levels of explanation
| Level | Audience | Focus |
|---|---|---|
| One sentence | Anyone | What it is and why it matters |
| Two minutes | New colleague | How it works with one example |
| Ten minutes | Practitioner | Steps, edge cases and common mistakes |
| Deep dive | Expert | Reasoning, evidence and trade-offs |
Practising all four levels builds both clarity and depth, and shows which level you can actually reach without notes.

## Writing explainers for others
Turn your best explanations into short explainers for your team: one concept per page, plain words, a diagram or example and links to sources. Teams with shared explainers onboard faster and argue less about definitions, and writing them deepens your own understanding further.

## Signs you understand
- You can explain it simply without notes.
- You can give a new example, not only the one from the source.
- You can say when it does not apply.
- You can predict what happens if one part changes.
- You can answer a beginner's "why" questions.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Very complex topic | Break into smaller concepts; explain each, then how they connect |
| No one to teach | Record yourself, write a blog-style explainer or use AI as the questioner |
| Analogy misleads | State the limits or drop it |
| Technical precision needed | Keep the precise term, define it once and use it consistently |
| Group learning | Members take turns explaining and questioning |
| Explaining to experts | Focus on reasoning and edge cases, not basics |

## Handoffs to related skills
- Reading and notes: `active-reading-notes`
- Remembering: `spaced-repetition`
- Learning plans: `learning-plans`
- Presenting what you learned: the Communication and Presentations skills
- Writing explainers: the Workplace Writing `plain-english` skill

## Worked example
A new product marketer kept nodding through engineering discussions about APIs and webhooks. Each week she chose one concept, wrote a plain explanation from memory, marked the gaps, asked an engineer two targeted questions and rewrote the explanation with an example from the product. She then explained it to a sales colleague and adjusted when he got confused. After eight weeks she had a library of 15 short explainers, contributed confidently in product meetings and the sales team began using her explainers in onboarding.

## Common mistakes
- Explaining with the same jargon as the source.
- Skipping the gap-finding step.
- Using analogies without their limits.
- Reading AI explanations instead of writing your own.
- Never testing explanations on another person.

## Output format
```
1. Concept chosen
2. First explanation from memory
3. Gaps found
4. Revised explanation (template)
5. Examples and non-examples
6. Test results with others
```

## Self-check before you answer
- Was the first explanation written without notes?
- Were gaps identified and studied?
- Is the final explanation plain, with examples and a non-example?
- Was it tested on someone else?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/research-learning/explain-to-learn/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.