Comparing Decimals

Activities to try

1. 1

   Order ragged decimals against a length model

   Why it works: The decimal with more digits is not automatically larger, and the one with fewer digits is not automatically larger either; size is decided by the highest place where the digits differ. A length/number-line model shows that more digits need not mean more length (0.38 is shorter than 0.4, but 0.87 is longer than 0.4). Annexing trailing zeros gives decimals the same number of decimal places without changing their value.

   1. Before using any model, predict the order of ragged decimals from smallest to largest and say why, e.g. for 0.4, 0.38, 0.312, 0.5.
   2. Represent each decimal as a bar or length drawn to a common scale (for example a Linear Arithmetic Block / bar model), then check your predicted order against the lengths.
   3. State the correct order (0.312 < 0.38 < 0.4 < 0.5) and justify it in place-value language: 0.312 and 0.38 both have 3 tenths, so they are smaller than 0.4 (4 tenths) and 0.5 (5 tenths); among the 3-tenths numbers, 0.312 (3 tenths 1 hundredth) is less than 0.38 (3 tenths 8 hundredths).
   4. Also compare the counterexample ragged pairs 0.4 vs 0.87, 0.9 vs 0.11, and 0.45 vs 0.405: predict first, then check each against the length model and in place-value words. These pairs deliberately trip both faulty rules — for example 0.45 vs 0.405 tempts longer-is-larger (405 looks bigger than 45), yet 0.45 (4 tenths 5 hundredths) is larger than 0.405 (4 tenths 0 hundredths 5 thousandths); and on the 0.4/0.38/0.312/0.5 set a shorter-is-larger learner can still land the right order.
   5. Locate the decimals on a number line and, where helpful, zoom between 0.3 and 0.4 to see 0.38 and 0.312 separated in the hundredths.
2. 2

   Name and resist the whole-number rule (correct vs incorrect cards)

   Why it works: The error is partly a failure to inhibit the whole-number rule, not only missing knowledge; naming the misconception and inspecting clearly-labelled correct/incorrect examples side by side helps a learner catch and override it.

   1. Look at side-by-side comparison cards, one clearly labelled correct and one clearly labelled wrong, e.g. '0.45 > 0.5' (labelled wrong) beside '0.45 < 0.5' (labelled correct).
   2. Say out loud which faulty rule produced the wrong card ('longer-is-larger: it counted 45 against 5') and explain why it fails here.
   3. Write or state the place-value reason the correct card holds (0.5 is 5 tenths; 0.45 is 4 tenths 5 hundredths; 5 tenths is more).
   4. Before answering each new pair, flag the rule you must NOT use, then compare correctly.
3. 3

   Show equivalence and area with hundredths grids

   Why it works: Decimals can be compared by area as well as by length, and both representations show that annexing a zero (0.7 = 0.70) preserves value while more digits need not mean more size. (Note: the source synthesis treats length as the clearest magnitude model for this topic; the grid is a complementary reference.)

   1. Shade 0.4 and 0.38 each on a 10×10 hundredths grid and compare the shaded areas.
   2. Shade 0.7 on one grid and 0.70 on another, and explain why seven tenths fills the same area as seventy hundredths.
   3. Use an aligned place-value chart (points lined up) to read each decimal digit by digit, starting from tenths, and state which decimal is larger and why.