Adding any two whole numbers whose sum is 100 or less is a core second-grade skill. Students develop fluency through multiple strategies: the standard regrouping algorithm, counting on from the larger number, making tens, decomposing addends, and using number-line jumps. The goal is flexible, efficient computation — choosing the best strategy for a given pair of numbers.
Rotate among strategies rather than drilling one. Pose pairs like 48 + 25 and ask students to solve two ways and compare. Hundred charts are excellent for building intuition about how numbers relate. Games like 'race to 100' with base-ten blocks build fluency through repetition in context.
You already know how to add two-digit numbers when regrouping is needed — that's the foundation this topic builds on. Now the goal shifts from just getting the right answer to choosing the *best* strategy for a given problem. Not every pair of numbers calls for the standard algorithm. With 50 + 30, mental math (just add the tens) is far faster. With 48 + 25, the algorithm works well. With 37 + 43, making tens (37 + 3 = 40, then + 40 = 80) is elegant. Recognizing which approach fits is what this topic is about.
The making tens strategy is especially powerful. It exploits the structure of our base-ten system: once you reach a multiple of ten, adding becomes much easier. To add 48 + 35, notice that 48 needs 2 more to reach 50. Take 2 from the 35, leaving 33. Now 50 + 33 = 83. You haven't changed the total — you've just reorganized the parts into friendlier pieces. This is called decomposing an addend, and you can do it with either number.
The counting on strategy works best when one addend is small. To compute 76 + 8, start at 76 and count up 8: 77, 78, 79, 80, 81, 82, 83, 84. It's slower for large addends, but it reinforces number-line thinking — you're locating 76 on a mental number line and hopping forward. The hundred chart makes this visual: moving right adds 1, moving down adds 10, so 48 + 25 is five steps right and two steps down from 48.
All these strategies are equivalent — they always give the same answer because addition is commutative and associative. Fluency isn't about memorizing one procedure; it's about owning number relationships well enough to navigate flexibly. The test of fluency is being able to solve a problem like 63 + 28 two different ways and explain why both work. That flexibility — not speed alone — is the real goal.