When learners are new to a skill, “figure it out” is often a kindness that backfires. Working memory fills up with search, dead ends, and panic. A worked example shows a complete solution path so attention can go to understanding structure—not inventing it from scratch.
What a worked example actually is
A worked example is not a hint. It is a full solution with visible steps and, ideally, brief reasons for each step. The learner studies it before solving similar problems independently.
Contrast:
- Pure discovery: “Solve for x.” Silence. Frustration.
- Worked example first: Show the full algebra path, then ask for a near twin problem.
- Too much telling forever: Learners never practice retrieval and stay dependent.
The sweet spot is temporary support that fades.
Info: Worked examples reduce cognitive load while schemas form.
A classroom or tutoring pattern that scales
- Show one fully worked example for the new pattern.
- Have learners annotate why each step exists, not only what the step is.
- Fade support: next problem is half-complete; learners fill missing steps.
- Near transfer: a problem with the same structure and different surface details.
- Far transfer later: only after accuracy on near transfer is solid.
Example in math: teach percentage increase with a fully worked shop-discount problem. Next, give a salary-increase problem with the first two steps filled. Then a full problem with new numbers. Do not jump from the first demo to a multi-step word problem with irrelevant story details.
Example in writing: show a paragraph that uses claim → evidence → explanation. Ask students to label those moves. Then give a paragraph with a missing explanation sentence to write. Then ask for an original paragraph on a new topic using the same moves.
Design details that separate “example” from “magic”
| Element | Strong version | Weak version |
|---|---|---|
| Steps | Explicit and numbered | Hidden leaps (“simplify”) |
| Reasoning | One line of why per key step | Only final answers |
| Similarity | Next problem matches structure | Next problem is a trick variant |
| Timing | Example before heavy practice | Example after learners already failed for 20 minutes |
| Fade | Completion problems, then independence | Sudden sink-or-swim |
Failure modes
Example overload. Ten fully worked problems with no independent practice creates recognition without retrieval. Alternate study and solve.
Copying without thinking. Students rewrite steps robotically. Force “why” annotations and a closed-book retell of the method.
Expertise reversal. Advanced students can be slowed by too many worked examples. Give them fewer examples and more problem solving sooner.
Surface matching only. Learners memorize the story (“the train problem”) instead of the structure. Vary cover stories while keeping the deep structure stable at first, then vary structure deliberately later.
When not to lead with worked examples
Skip or shorten worked-example-first approaches when:
- Learners already have a strong schema and need challenge, not demonstration.
- The goal is open-ended creativity with no single correct path—use exemplars differently (mentor texts, critique).
- You only have assessment time left; then prioritize practice tests over new demos.
- Collaboration goals require productive struggle by design—still offer optional worked examples for those stuck after honest effort.
A 30-minute lesson sketch
Minutes 0–8: Present one clean worked example. Learners annotate why-steps in pairs.
Minutes 8–15: Completion problem (half worked). Teacher circulates for misconceptions.
Minutes 15–25: Two independent near-transfer items. Quick peer check against a rubric of steps.
Minutes 25–30: Exit ticket: “Write the method in four bullets without looking.”
Assess whether the method worked
After two lessons with worked examples, check transfer with a cold problem that shares structure but not surface details. If students only succeed on clones of the demo, your fade was too shallow or your why-annotations were skipped. If advanced students complain of boredom, shorten the example phase and move them to generation sooner.
Keep a simple teacher log: example used, completion problem used, percent correct on near transfer. That tiny dataset beats vibes when deciding whether to repeat the pattern next unit. Over a term, you will notice which topics need two worked examples and which need one—usually the ones with more invisible steps or easy-to-confuse lookalikes.
Subject-specific snapshots
Languages: Worked example = a fully annotated short paragraph with grammar moves labeled. Fade by removing labels on a second paragraph. Transfer = a new prompt with the same rhetorical moves.
Lab sciences: Worked example = a completed lab calculation with unit checks visible. Fade by blanking the unit-check line. Transfer = same calculation with new measurements.
History essays: Worked example = a thesis paragraph dissected into claim, warrant, and evidence. Students then rebuild a parallel paragraph on a different event using the same skeleton.
Across subjects, the constant is visible structure before independent production.
Troubleshooting FAQ
Students say examples make them passive. Make annotation and retell mandatory. Passivity is a design flaw, not destiny.
I teach mixed-ability groups. Provide the worked example to everyone, then branch: strugglers get another completion problem; advanced learners get a transfer twist.
Does this work for coding? Yes—show a fully commented function that solves a narrow task, ask learners to explain each block, then alter one requirement.
How many examples before practice? Often one excellent example plus one completion problem beats five mediocre demos.
Parents ask for more homework worksheets. Prefer one worked example review plus three varied problems over twenty identical drills.
Worked examples are scaffolding with an exit plan. Show the path, fade the support, demand near transfer, and stop helping the moment the schema can stand on its own.