Using Worked Examples to Learn

What a worked example is

A worked example is a problem presented with its complete solution, showing each step and, ideally, the reasons for it. You find them in textbooks, in teacher demonstrations and in many online lessons. They are used in math, but also in physics, chemistry, statistics, programming and any subject where problems follow methods.

A common instinct is to jump into solving problems yourself as soon as possible, on the theory that doing is the only way to learn. Doing matters, but for a beginner facing a new kind of problem, studying a good solved example first is often a more efficient start.

Why they help

When you do not yet know a method, trying to invent it takes up a lot of mental effort. You have to hold the problem in mind, search for approaches, test them and track what has failed, all at once. Working memory is limited, so little room is left for noticing the underlying structure.

A worked example takes over much of that search, leaving your attention free to see how the problem is organized, what each step accomplishes, and why that step comes next. Learning research on this topic generally supports using worked examples for novices, though the benefit tends to shrink as skill grows, at which point independent problem solving becomes more valuable.

Study an example actively, not passively

Reading a solution and nodding along is the least useful way to use it. The recognition feels like understanding but may disappear when you face a blank page. Better approaches:

Cover the solution and try the first step yourself. Then uncover and compare. This turns reading into active recall.
Ask “why” at each line. Why this operation? Why in this order? What would go wrong otherwise?
Label the steps. Write a short note beside each line, such as “subtract 5 from both sides to isolate the term with x.”
Name the problem type. What features make this method appropriate? What would make it the wrong choice?
Explain it aloud or in writing as if teaching someone, which is the idea behind the Feynman technique.

A small illustration

Here is a simple worked example for solving a linear equation, 3x + 5 = 20.

Goal: find the value of x that makes the statement true.
Step 1: subtract 5 from both sides, since doing the same thing to both sides keeps the equation balanced. This gives 3x = 15.
Step 2: divide both sides by 3, to undo the multiplication. This gives x = 5.
Check: replace x with 5. Then 3 times 5 is 15, and 15 plus 5 is 20, which matches.

The useful parts are not only the answer but the reasons beside each step and the final check. Studying it well means being able to say why each operation was chosen and noticing that the order undoes the equation’s operations in reverse. After that, you might cover the solution and attempt 4x + 3 = 19. Subtracting 3 gives 4x = 16, and dividing by 4 gives x = 4. The check is 4 times 4, which is 16, plus 3, which is 19.

Compare examples

Looking at two or more examples side by side helps you see what stays the same and what changes. That is how you separate the core idea from surface details like the particular numbers or the context of a word problem. Ask: how are these alike? What changed, and did the method change? Including an example where a familiar method does not work shows the boundary of the idea.

Move gradually from support to independence

A powerful way to use examples is to fade the support:

Study a complete example.
Complete a partly worked problem, where some steps are left blank for you to fill in.
Try a similar problem with only a hint.
Solve a similar problem on your own.
Tackle a problem that differs in a meaningful way, where you must decide which method to use.

Many textbooks follow this pattern, and you can build it yourself by covering parts of a solution. If you get stuck at a stage, step back one level before pushing forward.

Pitfalls to avoid

Copying the pattern without understanding. If you change the numbers and follow the steps mechanically, you may fail on problems that look different. Always connect steps to reasons.
Looking at the solution too early. Give a problem a genuine try first when you have some knowledge of the topic. Productive struggle followed by a worked solution can teach well, but too long without progress is just frustrating.
Collecting examples without practicing. Examples are a stepping stone to your own work, not a substitute.
Using poor examples. A solution that skips steps or gives no reasons is less helpful. If a source is unclear, look for another or add the missing explanations yourself.
Only seeing one type. Mixing problem types through interleaved practice later ensures you can choose the right method.

Fitting examples into your study routine

When reading a textbook chapter, work through each example with a pencil instead of only reading. Record favorite ones in your notes with your own labeled steps, or turn them into question-and-answer cards using principles from flashcard design: the front shows a problem, and the back shows the key idea and first step. Later, use practice tests to check that you can handle problems without any examples in view. Your own study summaries can include a short list of problem types and the method that fits each one.

Worked examples also help when learning to code, where reading and tracing a working program before writing your own is a similar progression.

Why this is worth trying

Studying solved problems is not cheating or a shortcut. It is a well-supported way to build the understanding that independent practice relies on. Used actively, it saves effort, reduces frustration, and prepares you to solve problems on your own.