TL;DR:
Writing a problem one step at a time lets you check each step before building on it.
The pace matters: one step, then the reason, then a pause for you.
Check the whole answer at the end by multiplying back.
You can follow a finished solution and still be unable to do the next problem. The finished page hides the part that matters: what the person was thinking at each point, and what they checked before moving on. Watching a problem get built one step at a time puts that thinking back.
The short answer
A blackboard-style solution shows one step, says why, and stops. You see the work appear in order, so the reason for step three is visible before step four exists. That is the opposite of a finished answer pasted in whole.
What happens step by step
The problem is written out in full so you and the assistant are looking at the same thing.
The first step is written and explained in a sentence.
It pauses. You can say "go on", ask why, or try the next step yourself.
Each new line is placed so earlier lines stay visible.
At the end, the answer is checked, not just stated.
Walk-through: a long division worked one step at a time
Take 1,092 ÷ 12.
12 does not go into 1, so look at 10. It does not go into 10 either, so look at 109.
12 × 9 = 108, and 12 × 10 = 120 is too big. So write 9 above the 9 of 1,092. Subtract: 109 − 108 = 1.
Bring down the 2 to make 12. 12 × 1 = 12, so write 1 above the 2. Subtract: 12 − 12 = 0.
The quotient is 91, with remainder 0.
Now check by multiplying back: 91 × 12 = 91 × 10 + 91 × 2 = 910 + 182 = 1,092. It matches the start, so the answer is right. The check is the step students most often skip, and it is the one that tells you whether you can trust the other four.
Why the pace matters
If a solution arrives too fast, you nod along and learn nothing. One step with its reason gives your brain time to predict the next one. Predicting and being right is how you know you understand; predicting and being wrong shows you exactly where to look.
Try the next step first: Before the assistant writes a step, say what you think it will be. A wrong guess is useful information, and costs nothing.
Why long division is a good test case
Long division looks like one operation, but it is a loop of smaller ones: estimate, multiply, subtract, bring down. Students who get the right answer by memory often cannot say which part they are doing at any moment. Writing it out in order exposes the loop.
Look back at 1,092 ÷ 12. The estimate step was "12 times what is close to 109 without going over?" The multiply step was 12 × 9 = 108. The subtract step was 109 − 108 = 1. The bring-down step made 12. Four named moves, repeated twice. When you can name the move you are on, you stop getting lost.
Checking each step, not just the end
After an estimate: is the product less than or equal to the number you are dividing into?
After a subtraction: is the remainder smaller than the divisor? Here 1 is smaller than 12, which is right.
At the end: multiply back, as above.
The middle check catches errors early. If a remainder ever came out as 13 when dividing by 12, you would know at once that the estimate was too small, without waiting for a wrong final answer.
Using it for other subjects
The same method suits solving an equation (one operation to both sides per line), balancing a chemical equation (one element at a time), or reading a graph (one feature at a time). In each, the value is the same: a visible order and a reason for each move.
A second problem to try yourself
Try 1,254 ÷ 6 on paper, and say each move out loud as you go. 6 goes into 12 twice, so write 2 and subtract 12 − 12 = 0. Bring down 5: 6 goes into 5 zero times, so write 0. Bring down 4 to make 54: 6 × 9 = 54, so write 9, remainder 0. The answer is 209. Check: 209 × 6 = 200 × 6 + 9 × 6 = 1,200 + 54 = 1,254.
The zero in the middle is where many people slip. Seeing the "goes in zero times" step written down makes it hard to forget, which is another gain from writing every move instead of doing some in your head.
Say the move before you write it.
Write the check at the bottom every time.
If the check fails, find the first line that looks off, not the last.
What it can't do
Do your exam for you. It can show a method, but you need to practice the steps yourself.
Guarantee it is right. Do the check at the end. Multiplying back, substituting into an equation and estimating all catch slips.
Know what your teacher wants shown. Some classes require a particular layout. Ask your teacher.
Privacy and control
DuckyHelper has a blackboard where it works a problem out with you. It listens and looks only while the pill is open (fn on a Mac, Ctrl+Shift+Space on Windows and Linux) and for that answer, and it is not watching when idle.
Try it yourself
Pick a problem you got wrong last week. Ask for it one step at a time, and stop it after step one to say what step two should be. Then do the multiply-back check yourself.
Frequently asked questions
Is a step-by-step solution just giving me the answer slowly?
Not if you take part. The pauses are where you predict, try, and ask why. If you only watch, the benefit is small.
How do I know a step is right?
Check the result against the original: multiply back for division, substitute for equations.
Get started
