Nothing! Yes I said nothing! Let me elaborate.
In conversation today I was asked, “What is wrong with an algorithm?” I get this question a lot. Now this question was asked because like us all we were taught to do an algorithm so we always do what is familiar for us. The question also came about because they were afraid of teaching their child the wrong way.
This inspired me to write this blog post. There is nothing wrong with learning an algorithm; there are some risks in only learning this but there is nothing wrong.
An algorithm was first invented in order to make math easier to do. We have to remember that calculators were not invented at this time and may people were using abacuses and basically counting by ones or a base 16 system. With the use of an algorithm counting became procedural and easier to do. However, those using it understood mathematical foundations of why the algorithm worked.
This is the problem with introducing the algorithm to early. Let’s just reflect on our own understanding of basic addition. We honestly did not learn how to add by using an algorithm first and to be fair our first insistence of remembering an algorithm (at least in my guess) was probably around grade three maybe four. This means that for four-five years, depending if you were in the pre-school or JK error you had a lot of experimentation and exploring in counting, saying numbers, ordering numbers and subitizing. The problem is that we often forget all of the steps it took us in learning an algorithm.
For the past ten years I have been looking closely at how students learn mathematics. One of the foundation research pieces have been Fosnot and Dolk’s landscape of Learning (2000). (full file)
I know that the picture is small but you can see all of the learning that a student has to go through in order to get to an understanding of algorithms.
Now here is my problem with starting with algorithms to early:
1) It doesn’t teach proper number sense:
Now you may question me on this but in my honest opinion it doesn’t teach proper number sense. The problem is that when a person does an algorithm it forces you to only look at numbers from 1-9. There is no true understanding of our base ten system. Students do not really understand why or how 1 group of ten can be ten things yet 1 ten. This is often seen when you ask a student tell you the value of a two digit number (let’s say 24). When you point to the ten’s column they will say the value is two. They will even go as far as counting 24 objects then pulling two of them to signify the value. This can also be seen when students use base ten blocks and they count the rods as two instead of twenty.
2) Basic procedural errors:
By allowing my students to explore, question and develop their number sense they are better mathematicians and yes we have discussed an algorithm, we have developed an understanding of how to use it but my students make less mistakes with a number line then with an algorithm. And to be honest they much prefer the number line then the algorithm, most of the time they do this because that is what they think they need to do.
One of the biggest problems in our math programs today is that we often jump to far into the abstract without thinking about the concrete work that people need to develop in order to understand these concepts.
What do you think? When and where should algorithms be taught? How do you develop number sense? Love to hear your thoughts.
For further reading I recommend reading:
1) Fosnot, C. T., & Dolk, M. L. A. M. (2001). Young mathematicians at work. Portsmouth, NH: Heinemann.