Back to Blog
GoScript Journal

Examples Before Definitions: A Teaching Order That Works

·7 min read·GoScript Team /Research

Examples before definitions is a simple rule: show two or three concrete cases, let learners notice the pattern, then give the term a name. People remember the picture far longer than the label.

A definition handed over first is an empty box. The learner parses the words, nods, and has nothing to attach them to. An example gives the box something to hold.

Let learners find the shape

Give three cases that share a hidden pattern and one that breaks it. Ask what the first three have in common. That question does the teaching, because the learner is the one assembling the idea.

When they name the pattern themselves, the term you supply afterward lands as a shortcut for something they already understand. When you name it first, the term becomes a thing to memorize instead of a thing to use.

A definition is a label for an experience. Give the experience first or the label has nothing to stick to.

Use contrast, not just similarity

The clearest understanding comes from the border, not the center. Show a strong example next to a near miss. Learners who can tell the two apart know the idea better than learners who only ever saw the perfect case.

Ask which example does not belong and why. That single move exposes whether they caught the pattern or just copied the surface features.

Name it last, then push back to cases

Once learners have the pattern, give the term, then send them straight back to new examples. The definition should be a tool they test, not a sentence they repeat.

If they can sort fresh cases using only the term, the order worked. If they need the original examples again, the pattern never fully took hold.

Key takeaways

  • Start with concrete cases and let learners spot the pattern.
  • Delay the term until the experience is in place.
  • Use near misses so learners learn the edges of an idea.
  • Ask which example does not belong to test real understanding.
  • End by sending them back to new cases with the new term.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel