Protocol
Remove worked steps gradually
There is a useful middle ground between watching and being abandoned.
When it fits
- A complete example makes sense, but a blank problem leaves you stranded.
When to avoid it
- Fading too quickly can remove needed instruction; leaving every step visible can hide dependence.
Why it matters
Move from a worked solution to completion problems with some steps missing, then to an independent problem. Research on fading examines this transition; a 2025 programming study also found a performance benefit in its setting. Do not judge the method only by whether it feels easier: that study did not find a significant cognitive-load difference.
Steps
- Study a correct example and identify the purpose of each step.
- Complete a similar example with part of the solution removed.
- Reduce support as performance permits, then solve a fresh problem unaided.
An example
First finish the final calculation, later supply the setup as well, and finally select and execute the whole method.
Check your result
You can complete a new problem after the scaffold is removed.
Keep this limit in mind
- Fading too quickly can remove needed instruction; leaving every step visible can hide dependence.
Connected ideas
Use beforeMix problems so the method is no longer announced
Evidence and sources
Renkl and colleagues investigated transitions from worked examples to independent problem solving by progressively removing solution steps.
The appropriate fading pace depends on the learner and material; no universal sequence length is established here.
How Fading Worked Solution Steps Works—A Cognitive Load Perspective · Abstract
A 2025 programming study reported better algorithmic performance for its faded-example strategy without a significant difference in cognitive load.
This is a narrow result in programming instruction, not proof that fading always feels easier.
An Experimental Evaluation of Worked Example Strategies for Efficient Programming Instruction · Abstract