For parents · 7 min read · 2026-05-20
How to talk to your kid about a wrong answer.
Your kid writes 7 × 8 = 54and your mouth is already open. The correction is right there, it's fast, it's kind — “no honey, it's 56” — and it's almost always the wrong move. Not because the number doesn't matter, but because the three seconds after a wrong answer are arguably the most valuable in the whole session, and a fast correction spends them on nothing. Here's what the research says about errors and learning, and the handful of sentences that keep a kid thinking instead of shutting the notebook.
The instinct that shuts down thinking.
Watch a parent help with math homework and you can almost set a clock to it. The kid writes a wrong answer; within a second or two, the adult says the right one. It feels like help. It feels like efficiency. It is neither.
When you supply the answer that fast, you end the kid's thinking before it finishes. The wrong answer wasn't random — it came from somewhere, a method or a slip or a half-remembered rule — and the instant you say “it's 56,” that somewhere becomes invisible. You can't fix a process you never saw. And the kid learns the real lesson of the moment: when I'm unsure, wait, and an adult will hand me the number.
The fix is almost embarrassingly simple. Pause.Three seconds — count them silently if you have to. The pause isn't a trick to make the kid squirm; it's the room a child needs to notice their own work, and the room you need to swallow the reflex to rescue. Most of the value in this whole article fits in that one beat of silence. Everything below is what to do with it.
What the research actually says about errors.
The reflexive view of a wrong answer is that it's a small failure to be erased as quickly as possible. The research view is close to the opposite: an error is information, and under the right conditions it's information that makes the eventual learning stick harder than if the kid had gotten it right the first time.
The clearest summary is Janet Metcalfe's 2017 review Learning from Errors, in the Annual Review of Psychology. Her bottom line, across decades of lab work: for neurologically typical learners, error avoidance is a counterproductive strategy — and for neurodivergent kids the picture is a little different, which is its own section below. Making an error and then getting corrective feedback generally produces better retention than playing it safe — providedthe feedback actually arrives and the kid is awake to it. The error isn't the problem. An error left uncorrected, or corrected so fast nobody noticed it, is.
One finding inside that literature flips a parent's intuition. The hypercorrection effect(Butterfield & Metcalfe, 2001) is the result that errors a person made with high confidenceget corrected more reliably than errors they were unsure about. The kid who insists “7 × 8 is definitely 54” and turns out to be wrong is, counterintuitively, the one more likely to remember the correction on a later check once they see it — the surprise of being confidently wrong makes the correction land harder. So when your child is sure and wrong, that's not a hard slog to brace for. It's the moment with the most upside, if you let the surprise work instead of flattening it with a quick “nope.”
A third strand deserves a careful mention. Manu Kapur's work on productive failure (Kapur, 2008) shows that letting learners struggle with a hard problem beforebeing taught the method can deepen understanding, even when the first attempts fail. It's a real and useful idea — but the caveat matters: Kapur's studies were largely done with older students on complex problems, and younger children generally need more scaffolding, not less. For an 8-year-old, “productive failure” does not mean “leave them to flounder.” It means a beat to wrestle, then stepping in with a question — not vanishing into the kitchen while they spiral.
Put the three together and the kitchen-table takeaway is small and concrete: the wrong answer is the raw material. Your job isn't to erase it. It's to make sure the correction lands — through the kid's own thinking where possible — instead of bouncing off.
Questions that beat corrections.
The move that uses the pause well is a question, not a statement. A good question does two things at once: it keeps the kid in the driver's seat, and it shows you the process that produced the wrong answer, so the two of you can find the actual slip. Here are the ones that work.
“Walk me through how you got that.”The workhorse. It's neutral — you'd ask it of a right answer too — so it doesn't telegraph “you're wrong,” and it surfaces the method. Often the kid catches the error themselves halfway through narrating it, which is the single best outcome available: the correction came from inside their own head, and that's the version that sticks.
“What made you pick that?” For when the answer arrived without visible work — an invitation to reconstruct the reasoning that treats the reasoning as worth hearing. Note the framing: not why (which sounds like an accusation) but what made you — the cause, not the character.
“Where could we check that?”Hands the kid a tool instead of a verdict. Estimate it, count it on fingers, add it back the other way, draw it. The point isn't just this one mistake; it's teaching that answers are checkable, and that checking is normal math rather than an admission of failure. “We” matters too — you're a partner in the checking, not the examiner.
“Does that answer seem big or small to you?”A number-sense nudge for answers that are wildly off. A kid who says a third of twelve is thirty-six can often feel something's wrong once you ask — and that felt sense of magnitude is worth more in the long run than the specific fix.
Notice what these share: none contains the right answer, and none contains the word “wrong.” You're not withholding the answer to be coy — only for the few seconds it takes the kid to do the part only they can do. If they truly can't get there, you tell them — warmly, plainly, no drama — then have them redo a similar one to make sure the correction took.
What not to do.
The questions above are the high-leverage half. The other half is subtraction — a short list of reactions that reliably make the moment worse, most of them nonverbal and most of them faster than thought.
- The sigh.The exhale, the micro-pause, the “okay…” in a flat voice. Kids read tone long before content. A sigh tells your child the wrong answer cost you something, and the lesson they take is to hide uncertainty next time rather than show it.
- The eye-roll, the look. Same channel, louder. Even a flicker of it teaches that being wrong is embarrassing in front of you specifically — which is the last place you want math to feel unsafe.
- “You JUST did one like this.”Maybe true. Completely useless. It adds shame without adding information, and it usually isn't even accurate — a kid who got the last one right and this one wrong is telling you something specific about this problem, not about their attention span.
- Speed-shaming.“Come on, this should be quick,” “you're taking forever.” Speed is not the same thing as understanding, and pressuring for it is the fastest way to eat the working memory the kid needs for the actual math. The clock is not your friend in this moment.
- Correcting before they finish.Jumping in mid-thought — even to help — teaches the kid that their reasoning isn't worth completing. Let the sentence land, even when you can see where it's going.
If you do exactly one thing differently after reading this, make it the removal of the sigh. It's the most common, the most automatic, and the most corrosive, precisely because neither of you usually notices it happening.
When the wrong answer isn't a concept gap.
One honest note for parents of neurodivergent kids, because the standard advice can mislead here. For a kid with ADHD or dyscalculia, a wrong answer is often notevidence that the concept didn't land. It's a working-memory slip: they understood the problem, started the right method, and dropped a digit, lost the carry, or mis-copied the number from one line to the next while holding three other things in their head.
The tell is in the gap between the explanation and the answer. Ask “walk me through it” and you'll often hear a completely correct method produce a wrong number — reasoning intact, execution wobbled. Reacting to that as a concept failure (“let's go back and re-learn this”) is both wrong and demoralizing: the kid knows they understood it, and now they're being made to relearn something they already have.
React to the process, not the number. “Your thinking was exactly right — let's just find where the number slipped” names the slip as a slip and protects the part the kid owns. It also points at the real fix, which is usually offloading working memory: write the intermediate steps down, do one step at a time, slow the copying. The concept may not need re-teaching. The working memory needs a support.
One last thing.
None of this requires you to be a math teacher. It requires you to be the calm adult who treats a wrong answer as the start of a conversation instead of the end of one — who pauses, asks “how did you get that,” and lets the kid do the part only they can do. That's the whole skill. It's also, for what it's worth, the philosophy we built Koda around: that the work a kid shows matters more than whether the number came out right, and that no child should feel ashamed of an honest mistake.
If you want to know when it's available, drop your email at the waitlist. We email a few times. Total. From a real person.