The Times Tables War: What Finally Worked in Our House (After Everything Else Failed)

The times tables war in our house lasted fourteen months. Fourteen months. My son is not unintelligent. He is not even particularly maths-averse — this was before the anxiety set in. He simply could not commit the times tables to memory, and I could not understand why, and the gap between his inability and my incomprehension drove both of us to the edge of reason.

Let me tell you about the six approaches we tried. Five of them failed. One of them worked.

Method 1: Traditional drilling. Failed.

This is how I learned times tables. You sit down, you say "six times seven is forty-two" out loud, repeatedly, until it is in your head. I tried this first because it was what I knew. We did fifteen-minute drilling sessions every morning before school for three weeks. He could recite them in sequence. He could not retrieve them out of sequence, which is the only form in which they are useful. "What is seven times eight?" — pause, count on fingers, work backwards from a sequence he'd memorised. No use. Drilling had built a ladder he could only climb from the bottom.

Method 2: Times tables songs. Failed.

There are YouTube videos. There are many YouTube videos. We watched them. He liked some of the songs. He can, to this day, sing you a song about the nine times table. He cannot use the nine times table. The song is stored somewhere entirely separate from the mathematical function. I have no scientific explanation for this but I observed it empirically.

Method 3: Times tables apps. Mostly failed.

We tried three apps over several months. The apps were visually engaging. He was good at the apps, in the sense that app-completion metrics went up. On a written test, performance was unchanged. The apps had trained him to respond correctly in the app environment — with sounds, colours, visual cues — but that learning did not transfer to a silent classroom. Possibly this is a specific-learning-environment problem. Possibly the apps were just games with a thin educational coating. Either way: no transfer.

Method 4: Times table grid on the wall. Partially failed.

I printed a large times table grid and put it above his desk. The idea: passive exposure adds up. What actually happened: he used it as a reference tool and stopped trying to memorise anything, because the answer was always on the wall. I had accidentally created a crutch. Removed the grid. He was furious. His recall was still no better.

Method 5: Rewarding correct answers with points and prizes. Failed expensively.

I set up a chart system. Every correct answer in a random-order quiz was a point. Every ten points was a small reward. He was motivated — briefly, furiously motivated — to get points, and he worked out that the most efficient strategy was to memorise the smallest times tables (two, five, ten) extremely well and attempt the others as guesses. His incentive optimisation was impressive and entirely beside the point. He had gamed my system. I was frustrated and also, privately, a little proud.

Method 6: The thing that worked.

A friend — whose son had gone through the same battle a year earlier — told me about a specific approach: break the tables into groups, spend one week on each group, do very short sessions (three minutes, not fifteen), and crucially, only ever practise with random-order cards so that the recall is always non-sequential from day one.

The specific detail that made the difference: my friend said her son's tutor had explained that the problem with sequential learning is that the number pair "six times seven" doesn't live in the brain next to "forty-two" — it lives as a sequence that starts from "six times one." To retrieve "six times seven" quickly, you need a direct association, not a chain you have to walk down every time. The only way to build the direct association is to practise the retrieval non-sequentially, every time, from the very beginning.

We made physical cards. Old-fashioned index cards, not an app. One question per card, random order every time, timed with a two-second limit per card. Short sessions. Three minutes, twice a day. The two-second limit was important — it forced him to either know it or skip it, preventing the counting-up behaviour he defaulted to.

Six weeks later: fluent times tables. Not perfect — the sevens still sometimes cause a moment of hesitation — but fluent. Genuinely retrieved, not calculated.

Why does this battle feel so outsized in Hong Kong specifically? I think it's because the primary maths curriculum here moves fast and the times tables are foundational infrastructure. If a child is still calculating six times eight by adding six eight times, they have no working memory left for the actual problem. The tables need to be automatic. The school assumes fluency by P3. If a child doesn't have it, every subsequent maths lesson is harder than it needs to be, and the problem compounds.

We fought this battle for fourteen months. Six weeks of the right method resolved it. I have complicated feelings about that arithmetic.

The cards are still in a drawer. I'm keeping them.