Decimals in P4: The Three Misconceptions Every Teacher Sees

When the HK primary curriculum introduces decimals in P4, most children cope fine with tenths (0.1, 0.3, 0.7). The problems begin with hundredths — and they get worse, systematically, in ways that follow three very predictable patterns.

In my 15 years teaching P4 in Kowloon City, I could identify these three misconceptions on the first day of marking the decimal unit test. And because they're predictable, they're preventable.

Let me describe each one, explain why it forms, and tell you what to do about it.

Misconception 1: "More Digits = Bigger Number"

What it looks like: "Which is larger: 0.8 or 0.16?" Child answers: 0.16 (because "16 is bigger than 8")

This is the most prevalent decimal misconception and it appears in every P4 cohort I ever taught, in every year. Students who haven't fully grasped place value apply the whole-number rule: longer number = bigger number. 16 > 8, therefore 0.16 > 0.8. But 0.16 = 16/100 = 0.160, and 0.8 = 8/10 = 80/100. 0.8 is five times larger.

Why it forms: In whole numbers, adding digits does make numbers larger. Children overgeneralise this rule. The decimal point, which changes everything, hasn't been internalised as a game-changer.

How to address it: Use equivalent fractions as a bridge. Ask: "What is 0.8 as a fraction? (8/10 = 80/100). What is 0.16 as a fraction? (16/100). Now compare 80/100 and 16/100. Which is bigger?"

After 5–6 examples of this conversion, the place value understanding builds and the "more digits" misconception usually dissolves. Then revisit without the conversion step to check it's genuine understanding, not dependency on the procedure.

Also effective: Place both decimals on a number line between 0 and 1. 0.8 is near the right end. 0.16 is near the left. Visual representation overrides the digit-counting misconception.

Misconception 2: The Floating Decimal Point

What it looks like: Column addition:

  0.3
+ 0.14
------
  0.44   or   0.17   or   0.44 ← various wrong answers

The correct answer is 0.44, but for the wrong reason here. Let me explain with a clearer example:

  1.7
+ 0.84
------
  1.154   ← wrong (student treated as two separate integers: 17 + 84 = 101 with decimal inserted arbitrarily)

Correct: 1.7 = 1.70; 1.70 + 0.84 = 2.54.

Why it forms: Students know they need to "line up" numbers in column addition, but some haven't grasped that it's the decimal point (and therefore the place values), not the last digit, that must be aligned. They right-align the numbers as if they were integers.

How to address it: Explicitly teach decimal-point alignment as the rule, not right-alignment. Draw a vertical line for the decimal point column first. Every decimal point must sit on that line. This physical habit prevents the floating decimal error.

Immediately also teach the "trailing zero" strategy: 1.7 = 1.70. Adding a zero after the final decimal digit doesn't change the value but makes alignment errors much less likely. This is the most practical single habit for decimal arithmetic.

Practice activity: Write six mixed-decimal addition and subtraction problems. Have your child first draw the decimal-point column, then fill in the numbers (adding trailing zeros where needed), then calculate. The drawing step is the key.

Misconception 3: Decimal-Fraction Disconnection

What it looks like: "Write 0.25 as a fraction." → Student writes 25/10 or 1/4 without connection to why. "Write ¾ as a decimal." → Student writes 0.34 or 3.4.

This misconception is subtler than the others because students can often perform the conversions if prompted with the right procedure, but they don't understand the relationship. They've memorised "move the decimal" or "divide numerator by denominator" as separate rules, without connecting them as the same operation.

Why it forms: Fractions (introduced in P3) and decimals (introduced in P4) are taught as sequential topics. The explicit connection — that 0.7 is 7/10, not just "looks like" 7/10 — is often implied rather than stated. Students store them as two separate number systems rather than two representations of the same quantities.

How to address it: The most effective single intervention is the Fraction-Decimal-Percentage triangle (see my article on percentages and decimals). But for P4 specifically, focus on the Fraction-Decimal leg:

Start with visual representation. A 10×10 grid: shade 25 squares. That's 25/100 of the grid, or 25 out of 100, or 0.25. The decimal notation literally means "25 hundredths."

Then: shade 7 out of 10 squares (a 1×10 strip). That's 7/10 = 0.7. Write both side by side, emphasise they describe the same shaded region.

Once the visual connection is made, the procedural conversion (divide numerator by denominator) makes conceptual sense: 7 ÷ 10 = 0.7 because the fraction literally means "7 divided by 10."

The Common Thread

All three misconceptions share a root: children are applying whole-number rules or memorised procedures without the conceptual understanding that would allow them to check whether those rules are appropriate.

The fix for all three is the same: go visual and concrete before drilling procedures. Number lines, grids, fraction strips, and physical representations provide the conceptual anchor that prevents these misconceptions from forming in the first place.

If your P4 child is already showing one of these errors, don't respond by drilling more decimal problems. Respond by going back to concrete representations and rebuilding the understanding from there. The procedural fluency will follow — but only on top of sound understanding, not instead of it.