The Worked-Example Effect

A worked example presents a problem together with a solution that makes important steps visible. Its purpose is to help a learner notice how a method works before having to discover every step alone. The worked-example effect describes findings in which studying such examples supports novice learning more effectively or efficiently than spending the same learning period solving conventional problems. It is a conditional instructional effect, not a rule that every lesson should become a demonstration.

The mechanism is closely connected to cognitive load. A novice searching for a solution may devote much of their limited working-memory capacity to trying possibilities and tracking partial results. A well-designed example directs that effort toward relationships among the problem, the chosen operation, and the reason the operation is valid. Merely showing a final answer does not provide this support. Conversely, an explanation overloaded with commentary can make the relationships harder to follow.

Imagine teaching an adult numeracy group to solve 3x + 5 = 20. A useful example shows subtracting five from both sides, obtaining 3x = 15, then dividing both sides by three to obtain x = 5. Alongside the changes, the teacher identifies the shared goal: preserve equality while isolating the unknown. Learners check the answer in the original equation. The teacher then offers 4x + 7 = 23 and asks which operation should come first and why. This second task tests whether the example has supplied a usable method.

Example design matters. Keep explanations close to the steps they explain so learners need not search across a page. Highlight meaningful subgoals instead of decorating every symbol. Include enough variation to show what stays invariant: changing numbers is useful, but eventually the equation's arrangement should change too. Comparing a correct solution with a carefully chosen error can reveal a misconception, provided learners receive enough support to identify and correct it. An unexplained erroneous example can instead strengthen confusion.

Support should change as knowledge grows. A completion problem might supply the first step and ask the learner to finish. Later examples can omit more steps, followed by independent problems and delayed checks. The transition should respond to evidence of understanding, rather than a fixed number of demonstrations. Learners who already know the method may gain little from repeatedly studying fully specified solutions, and redundant guidance can consume attention that would be better spent on a new challenge.

For teachers, the practical question is what learners should learn to see. In a writing lesson, an annotated paragraph can reveal how evidence supports a claim; in programming, a short traced function can reveal the role of a loop. Ask learners to explain the decision at a pivotal step and then solve a related problem without the example. Smooth copying or apparent agreement is weak evidence of learning. Success means that learners can select, explain, and adapt the method when the original worked solution is no longer in front of them.