Too little help leaves a child stuck. Too much help does the thinking for them. Getting the level right is its own skill.
25 August 2026 · 5 min read
Think of a child learning to ride a bike with stabilisers. The stabilisers do a real job — they stop the bike toppling over while balance is still forming. But nobody expects a ten-year-old to still be using them. At some point they come off, not because the child suddenly stopped needing any support, but because the support that's left in place too long stops being help and starts being a crutch.
That's the whole idea behind scaffolding, and it applies just as directly to maths as it does to bike riding: support should exist to build a skill, not to replace the need for it.
A child who's genuinely stuck and gets no support at all doesn't usually push through to a breakthrough. More often, they start guessing, lose confidence, or quietly disengage. If a child has never seen how to find a common denominator, no amount of "have another go" is going to produce it from nowhere. That's not resilience-building — it's just leaving a gap unfilled.
The opposite failure is quieter and easier to miss, because it looks like kindness. A parent who jumps in at the first sign of hesitation, narrates every step, or simply does the working themselves while the child watches, is removing the exact struggle that would have built the skill. The child gets the right answer on the page in front of them and learns almost nothing that transfers to the next question. Too much help doesn't just fail to build the skill — it can quietly signal to the child that they weren't capable of finding it themselves.
The useful zone sits between those two extremes — slightly beyond what a child can currently do unaided, but well within what they can do with a small amount of support. Too easy, and there's nothing to learn. Too hard even with help, and the support doesn't do its job. The skill in scaffolding well is aiming for that narrow band in the middle.
Take a child who can recall 7 × 4 instantly but freezes on 7 × 8. The unhelpful extremes are either supplying "56" outright, or saying nothing and watching them guess. The useful middle: "You know 7 × 4. What's double that?" — a nudge that uses something they already have solid, to reach something they don't have yet.
The other half of scaffolding — the part that's easy to forget — is that it's temporary by design. The same child who needed "what's double 7 × 4?" this month should need less of that nudge next month, and ideally none of it by the time the times tables are secure. If the same amount of support is still required six months later, either the skill was never actually consolidated, or the help has quietly become a habit rather than a scaffold.
This is why generic worked examples tend to help less than ones built around the child's actual question — a point we touched on in should children be given the answer when they get a question wrong. Support that's specific to the problem in front of them is easier to fade out, because it was never a substitute for understanding — it was a bridge to it.
A rough rule that works well at home: give the smallest hint that could plausibly get them moving again, then pause and watch. If they run with it, that was the right amount. If they're still stuck, add one more layer of support — not the whole explanation in one go. It feels slower in the moment, but it's usually what separates a child who's learned a method from a child who's just been shown one.
Grasp Maths aims for that same narrow band automatically — offering the smallest useful hint first, adding a worked example only if that wasn't enough, and reducing how much support a skill needs over time as a learner's own responses show it's becoming secure.
Don't just practise more. Practise what matters next.
Try a free Grasp Maths practice session and see scaffolding sized to exactly what your child needs, no more.