The student who nods, then can't start
You explain a process. Everyone nods. You set the task. Three hands go up before anyone writes a word. Sound familiar?
The problem often isn't attention or effort. It's that a spoken explanation vanishes the moment it's finished. Students are asked to hold the method in their heads *and* apply it to a new problem at the same time. For anything hard, that's too much at once.
This is where worked examples earn their place. A worked example is a fully solved problem, shown step by step, that students study before they attempt one themselves. Decades of cognitive load research (Sweller and colleagues) point the same way: for novices, studying a worked example beats jumping straight into problem-solving.
Why they work
A novice and an expert don't see the same problem. The expert has patterns stored in long-term memory. The novice is building everything in working memory, which is small and tires fast.
A worked example takes the strain off. It shows the finished path so students can focus on *how* each step follows from the last, rather than flailing for a starting point. You're not lowering the bar. You're removing the guesswork that has nothing to do with the learning.
This matters most when content is genuinely new or complex. Balancing a chemical equation. Structuring a PEEL paragraph. Solving simultaneous equations. Analysing a source in History. The harder the content, the more a worked example helps.
Build them so they teach, not just show
A worked example on the board is not automatically a good one. A few things separate a useful one from wallpaper.
Show every step, including the ones you'd normally skip. Experts collapse steps without noticing. Novices need the intermediate ones. If you'd usually do it in your head, write it down.
Narrate your thinking, not just your actions. Don't only say *what* you did. Say *why*. "I underlined the command word first because it tells me whether to describe or evaluate." That reasoning is the part students can't see and most need.
Flag the decision points. Show where a student might go wrong and why you chose one path. "You could start here, but that leaves you with fractions, so I'll rearrange first."
Keep the layout clean. Split attention kills the effect. If the diagram is on one page and the working on another, students burn effort connecting them. Put the information they need together.
The copying problem, and how to beat it
The classic risk: students copy the example neatly and learn nothing. They mistake having a correct answer on the page for understanding.
Two moves fix most of this.
The first is completion problems. Instead of a blank task or a full example, give a partly worked solution and ask students to finish it. Start with most of it done, then fade the support over the lesson until they're doing the whole thing. This is sometimes called the completion effect, and it's a clean bridge from studying to solving.
The second is self-explanation. After studying an example, ask students to explain a step back to you or a partner. "Why did we subtract here?" A student who can explain the step understands it. A student who only copied it can't.
Example-problem pairs
One of the most reliable structures is the example-problem pair. Show a worked example, then immediately set a very similar problem for students to try alone. Then another example, then another problem.
The pairing keeps the method fresh in working memory while it's still fragile. Compare that to showing five examples in a row, then setting five problems. By problem four, the first example is long gone.
In practice for a Year 9 Maths lesson on solving equations, that might look like:
- •Worked example: solve 3x + 4 = 19, every step shown and narrated
- •Student problem: solve 5x + 2 = 17
- •Worked example: solve 2x - 7 = 11, flagging the sign change
- •Student problem: solve 4x - 3 = 13
Same principle applies in English. Model annotating one paragraph, then hand over the next. Model one topic sentence, then they write one. The gap between watching and doing stays small.
Where this fits in the lesson
Worked examples live in the 'I do' and early 'we do' stages. They come after a clear learning intention and before independent practice. They are the concrete substance of your modelling, not a replacement for it.
One caution worth naming: the benefit is strongest for novices. As students gain expertise, studying more examples adds less, and eventually they learn more by solving problems themselves. This is the expertise reversal effect. So fade the examples as competence grows. Start heavy, thin them out.
The workload catch
Good worked examples take time to build. Every step written out, every bit of reasoning made visible, the layout clean, the paired problems matched in difficulty. That's real preparation, and it's exactly the kind of careful design that gets cut when planning is rushed.
This is one of the checks built into Smart Syllabus Assistant. When it generates a lesson for hard content, it structures the modelling around worked examples with the reasoning made explicit, paired problems that match, and a fade toward independent practice. It's checked against explicit instruction before you ever see it, so the design work is already done. You bring the judgement and the classroom.
See a worked-example lesson built end to end at smartsyllabusassistant.com/sample.