Maths Is Fun Multiplying Decimals

The thing about teaching decimal multiplication to kids is it sounds easier than it actually is

Most people think multiplying decimals is just a matter of moving the decimal point around. Kids can follow that part if you explain it in one direction, but the moment they encounter something like 0.47 times 0.13, the whole system starts to unravel. That's when you end up with answers like 0.611 instead of the correct 0.0611, and the kid stares at you like you've personally betrayed them. I see this exact mistake constantly, even from well-meaning tutors.

The actual method works fine if you treat it as a three-step process rather than a single trick. Multiply as though the decimals don't exist, then count the total decimal places in both original numbers, then apply that count to your result from the right side. The key insight nobody really emphasizes is that you should ignore the decimal points entirely during the multiplication phase. Treat 0.47 times 0.13 as 47 times 13. The multiplication gives you 611, and then you go back and figure out where the decimal goes. You count the decimal places in each factor: 47 has two places, 13 has two places, so that's four total. Starting from the right side of 611, you move left four spots and get 0.0611. This approach removes the cognitive load of managing multiple decimals simultaneously. The kid only has to handle the multiplication algorithm they already know, then do a simple counting exercise afterward. Separating the steps makes it manageable.

I ran into a specific edge case recently that I hadn't considered before. A student was working through 2.5 times 0.004 and came up with 0.1000, which actually isn't wrong, but the teacher told her to reduce it. The issue was she didn't understand that trailing zeros after the decimal point don't change the value, so she ended up confused about whether her answer was right or not. The workaround was straightforward: once you've placed the decimal point using your count, you strip any trailing zeros and the answer is clean. In this case it's just 0.01.

Another thing that trips people up regularly is when the product has fewer digits than the total decimal places require. Take 0.03 times 0.007. The multiplication gives you 21, but you need five decimal places total. You can't just slide the point in because there aren't enough digits, so you pad with zeros: 0.00021. Kids forget to add those placeholder zeros, and the answer comes out completely wrong. The most persistent error I've observed is miscounting decimal places because students count the zero in numbers like 0.04 as a place when it actually just needs to be treated as padding. The number 0.04 has two decimal places, not one. That zero after the decimal point counts. It's a detail that gets glossed over too quickly. Another realistic problem involves estimation. If a student multiplies 3.8 by 2.1 and gets 79.98, that's immediately wrong but they have no way to catch it without a sanity check. The workaround is always to estimate first: 4 times 2 is 8, so the answer should be close to 8, not nearly 80. This catches roughly half of common placement errors before the kid submits the work.

The downside to this method is that it requires comfort with the standard multiplication algorithm. If a student hasn't mastered multiplying whole numbers first, decimal multiplication will feel like a maze. There's no shortcut around that prerequisite. I've seen this create gaps that make recovery slow, usually taking an extra couple of weeks to build the foundation back up.

What actually works for kids who struggle with this

Some learners benefit from visual models before they ever touch the standard algorithm. A grid or area model helps them see why the result gets smaller when you multiply two numbers less than one. Drawing a 1 by 1 square and shading 0.47 of the width and 0.13 of the height makes the intersection area clearly tiny. It takes longer to set up, maybe ten to fifteen minutes for a single problem, but the conceptual grasp it builds tends to stick. For pure speed, the standard algorithm remains faster once the kid has internalized it. The visual approach doesn't scale well to problems like 15.7 times 3.42, where the grid becomes unwieldy. At that point, the counting-decimal-places method is what you fall back on, and the student should already know how to execute it without hesitation. If you're looking for practice material, the Maths Is Fun website has a dedicated section on this topic that walks through examples with worked solutions. It's one of the more straightforward resources available for this subject, and the examples cover the common failure modes I mentioned above. You can find it at their main domain under the maths section for decimals.

The overall pattern I've noticed across years of helping kids with this is that they can usually follow the algorithm if you keep the explanation to one step at a time. Trying to explain the estimation check, the zero padding, and the place value reasoning all in the same conversation just floods them. One idea per session, repeat it until it clicks, then move on. It's slower than you'd like, but it actually works.