Lisa’s Method: A New Arrangement For Finding Slope
The National Council of Teachers of Mathematics continues to advocate for more student-centered mathematics teaching (NCTM, 2000). One of my dreams as a mathematics teacher and tutor is to have a student come up with an innovative approach to doing or thinking about some mathematics. And one of my nightmares is hearing of or seeing a student do something creative and be ignored or slapped down by an insensitive or ignorant instructor who fails or fears to consider that a student’s ideas about something might be of value. One of the worst aspects of “sage on the stage” mathematics teaching is its propensity for minimizing opportunities for students to do any thinking in class that strays from the teacher’s directed and generally very beaten path.
Recently, I had one of those much-desired opportunities to see a student spontaneously come up with what was, to me at least, an original approach to something that is easy for and familiar to many, but distressingly hard for a significant number of students: calculating the slope of a straight line given two points. My student, Lisa, had been working her way through a computer-based first semester geometry course and came to me unsure about how to find slope. As I anticipated, her problem centered the question of where to put the x- and y-coordinates in the slope equation. She was given the points (3, 2) and (-2, -4) with a picture of the graph, so I began by asking if she could tell from the graph whether the slope would be positive or negative. Once she was clear that the slope of a line that went up from left to right had to be positive, which was indeed the case with the line in question, I modeled for her how to draw a right triangle by extending a vertical segment down from (3,2) and a horizontal one to meet it from (-2, -4). I then asked her to find the lengths of the two legs of this triangle (5, and 6, respectively): an advantage for many students of this graphical approach is that lengths are positive regardless of the presence of negative numbers amongst the coordinates, and it is relatively easy for them to see or be convinced that adding the distances left and right or above and below the axes, respectively, as all positive numbers will get the correct lengths.
We then turned to the question of which of these numbers was the numerator of the slope. I offered the idea that slope represents a ratio of change between the vertical change of the line, positive, negative or zero, to its horizontal change from left to right, using the notation Dy/Dx, which Lisa responded to as something she knew from her physical science courses, stating, “Yes, that was how Ms. Acree [her science instructor] showed me.” I wasn’t sure, however, if Lisa saw that this was just a compact way of showing what we had looked at graphically, as well as indicating what calculations had to be done. When I asked if she knew what to do next, she said, “I’m not really certain.” I wrote Dy/Dx = (y2 - y1)/(x2 - x1) and asked her if that made sense. At that point, she said, “Oh, now I see why I keep getting the problems wrong: I’m putting the x’s on the top.”
Of course, this error is one all-too-familiar to mathematics instructors around the world. Countless students have lost untold numbers of points on exams due to this simple and understandable error. After all, x comes before y in the alphabet. And the x-coordinate precedes its partner y-coordinate in every ordered pair. Why wouldn’t it “come first” when writing the ratio for slope?
While we can all sagely agree that students “shouldn’t” make this error based on the underlying meaning of slope, as I pointed out to Lisa before going to notation, it is useless to speak about what is supposed to happen given what so often does. Much as it is important to try to get students to think clearly about the meaning of the mathematics they write and calculate with, it is difficult to ensure that this particular error, one I sometimes start to make myself if I’m not careful, does not occur.
To check her understanding, I posed a second problem to Lisa, giving her the points (3, 9) and (1, 1). She solved the problem graphically first, but was still a little unsure about doing it algebraically, so I did the usual set-up, writing m = (9 - 1)/(3 - 1) = 8/2 = 4.
Lisa looked at what I’d written down and suddenly took the paper and wrote something down, saying, “Couldn’t you do it like this?” (See Fig. 1)

Fig 1: Lisa’s Method
After looking at this for a few seconds, I thought that I understood what Lisa’s intentions were. However, I could see problems with her notation. To check, I asked what the symbols between the numbers in parentheses meant and she made clear to me that they were dashes, not subtraction signs. I asked about the slash and she said, “Oh, that means that you divide the two into the eight to get four, which would be the slope.”This was what I thought she meant, but I asked her if it seemed possible that most people would be confused by what seemed like indicated subtractions, and if she felt that math teachers would be very distressed by the idea that what she’d written at the bottom should be read the way she intended. She said, “Oh, I see what you mean about the dashes. But I don’t see what’s wrong with the bottom part.”
I said that in fact she appeared to be claiming that two divided by eight equaled four rather than one-fourth. But I believed that I saw an easy fix to what she had done. I then wrote below her figure (see Fig. 2)
This seemed more consistent with what was intended and didn’t use any non-standard or misleading notation. I asked Lisa if what I had done made clear what she wanted; she agreed that it did. The logical continuation would then be to perform the indicated division to get the slope (See Fig. 3)

Fig. 3 Teacher’s Version Completed
This correctly completed the solution for finding the slope of the line that contained the two given points.Lisa said she agreed with the changes I’d made. At this point, I said: “I have never seen anyone find slope like this. Did another teacher show you this?” She answered, “No, but when I saw how you did it, it just seemed to me that this would work. It seemed natural to me.”
I asked her explain why this seemed like a good way to her. She said, “Well, we always did subtraction problems like that: it seems easier to me when the numbers are lined up this way.”
I told her that I thought she might have invented an original approach that made sense, and that I was going to write up what she’d done for publication so that other teachers would have a chance to share it with their students. I think she believed I was pulling her leg, and though I tried to make clear that I was serious, even when I told her again at the end of class that I was definitely impressed by her approach and was going to write it up, she appeared skeptical.
What seems useful about Lisa’s method is that it solves the typical problem of forcing students to put the y-coordinates “first,” out of alphabetical order, when they may still be struggling to simply get a handle on what slope is and how to interpret it. So many students learn (and are often taught) mathematics in a mechanical, procedural way, and in the case of calculating slope, there is something counterintuitive about how we set up the ratio, even though we would like it to make sense. Clearly, solving the problem using her approach avoids putting students in a position where many will lose points on exams and become frustrated with this vital part of dealing with linear equations and their graphs. In the long run, I would expect that when they have a firmer understanding of slopes as ratios of change and of what it is that is changing relative to what (dependent variable relative to unit change in independent variable), they will become more comfortable and effective with the traditional approach. And of course, some students will be perfectly fine with the usual way of finding slope and will likely eschew Lisa’s alternative. However, as another possible way to set up this important calculation, it seems to have promise for struggling students.
Of course, I don’t mean to suggest that her method (or any approach) is a panacea for all possible student difficulties. Naturally, students still need to know how correctly subtract signed numbers. While my work with Lisa suggested that she was comparatively clear on integer arithmetic (based on work we did previously), most of my students are typical in struggling greatly with both the procedures and concepts in this regard. That is one reason I would strongly suggest that teachers have students find slopes of lines with points in the first quadrant and/or on the axes defining that part of the Cartesian plane. Further, it seems an aid to reviewing the requisite arithmetic to then have students solve problems graphically (using right triangles as I demonstrated to Lisa) before doing the symbolic arithmetic when including points in the other three quadrants.
For Lisa, the question of finishing the problem with dividing a smaller positive integer into a larger one was unproblematic. Further experimentation with numbers of opposite signs or with two negative numbers caused her no difficulty either, and she successfully concluded in cases that resulted in both proper and improper fractions that as long as she reduced to lowest terms, no further adjustment was needed to the results she calculated with her method. However, it is not at all obvious that this would be the case for all students, so further investigation along these lines will be important.
If nothing else, what Lisa has done can be shown to students as an example of creative solutions to simple but annoying sticking places for many teachers and students. I’ve personally never been happy with the “rise over run” idea, though I offer it to students as a mnemonic, because the word “run” doesn’t communicate horizontal motion to me clearly, even though it does to some students. I also worry sometimes that it locks students into thinking of slope too literally as restricted to a graphical interpretation, rather than keeping open the idea of slope as a ratio of change between dependent and independent variables.
Lisa seems to have spontaneously created something that for me might solve a nagging pedagogical problem: how to teach students to calculate the slope of a line from two given points without having to do something that for many does not come naturally. The key here for me (and I hope for teachers reading this article) is that I was open to seeing Lisa’s ideas and that we had established the kind of relationship where she felt comfortable sharing what seemed like a spontaneous burst of creativity with me. While it is far easier to be receptive to student thinking in the one-on-one teaching I often do as a consultant, coach, guest teacher, or in full-time work as a Title I mathematics teacher, I believe it is vital that teachers in more typical group and whole-class teaching situations remain open to opportunities to explore student ideas. As the work of teachers like Ball (1993) and Lampert (1985) shows, teachers must make dozens of decisions about such moments, and it is easy to lose them under the pressure to “cover the curriculum.” But if we are serious about teaching mathematics in ways that value and promote independent student thinking and active participation in a mathematical learning community, we cannot afford to miss the unexpected. At worst, we need to note when students have provocative, promising mathematical ideas so that we can revisit them later with their authors and other students. It’s not always possible in the heat of a lesson to see whether an idea warrants taking a detour from the official planned route. Even if something needs to be put on the back burner, it is important that students know that their ideas are valued, and vital that the teacher get back to the student to discuss and explore such insights and speculations further. And of course, it is necessary that teachers have adequate mathematical knowledge to recognize the potential significance of their students’ ideas (Ball, et al, 2005). But the more teachers take their students seriously as sources of rich mathematical ideas, the more likely it is that students will engage more fully in mathematics and indeed produce surprising and fruitful ideas.
References
Ball, D. L., Hill, H.C, & Bass, H. (2005). Knowing mathematics for teaching: Who knows mathematics well enough to teach third grade, and how can we decide? American Educator.Ball, D. L. (1993). With an eye on the mathematical horizon: Dilemmas of teaching elementary school mathematics. Elementary School Journal, 93 (4), 373-397.
Lampert, M. (1985). How do teachers manage to teach?: Perspectives on problems in practice. Harvard Educational Review , 55 (2), 178-194.
National Council of Teachers of Mathematics (NCTM). Principles and Standards for School Mathematics. Reston, VA: NCTM, 2000.




19 comments:
Interesting. I agree with some of your methods. For example, I have had math teachers dock me points when I came up with short hand notation *even* when I defined the notation in the problem's solution.
Indeed, my wife, who is studying to be a math teacher (after a long career as a computer scientist and a very high aptitude in mathematics) just about bit my 7 year old son's head off when he made a mistake similar to what Lisa made Lisa. He had looked at the equation "3*-3=-9" and said the answer was -18. My wife gasped (he's a very smart boy), but I patiently asked him to explain why. Turns out he had simply missed the equal sign, and thought the problem was "3*-3-9=".
Regarding slope, my 7th grade math teacher taught me, first, the simple mnemonic, slope is "rise over run".
What is rise? Change in elevation (y).
What is run? Change in range (x).
Perhaps you can comment on why you don't do the "rise over run" mnemonic. It is tried and true.
Then you might want to read my latest article and comment on it. In it, I take on a book used by math teachers to learn how to teach math. My view is it is atrocious.
Like you, I am often frustrated with the way math is taught, though I suspect you and I may think somewhat differently (as my background is engineering, in which we consider math to be a tool, and not an end unto itself).
I do use rise over run, but not exclusively and I don't find it to be anywhere near to adequate for a lot of the kids I've worked with. Possibly that's a reflection of literacy levels with at-risk students (the majority of my K-12 work has been with at-risk high school kids and with teachers of at-risk K-8 kids, as well as with developmental students at the community college level). It communicates to some folks and not to others, so I need other metaphors and models. I don't like it for ME as a learner, but that's just because in my mind, "run" is not clearly related strictly to horizontal motion.
As for your piece, of course I'd be interested. And I'm not a mathematician, so don't assume too much about my viewpoint.
Okay, great, it's at Why students in the United States perform poorly in math, and how to fix it.
What a great method!
It may end up in a textbook sometime in the near future. ; )
This is yet another good reason to understand fractions as division expressions, and vice versa.
JD: Given the rather cold reception this piece received from readers at a certain journal for math teachers, I wondered if I failed to do justice to Lisa's clever approach. If it shows up in any textbooks, that would be great. It's not a panacea and I thought I made it explicit in the piece that it isn't, yet I got some very odd feedback from folks who seemed to fail to understand why anyone would want to teach this (or who belittled its value if it were taught because it wouldn't be as valuable to kids who hadn't thought of it themselves).
I have to say I find that rather bizarre. Indeed, I got the sense from some comments that because this was simply procedural that it wasn't of interest or significance. Silly me to think otherwise.
The other thing that stuck in the craws of a few readers was my comment about "insensitive or ignorant teachers." Apparently, it's not okay to mention that we have these people in our profession. Naturally, no one who reviewed the article or the editor of that journal would fall into either category, nor would they likely be aware that we have either sort of teacher out there.
And maybe I'm a Chinese jet pilot.
The other thing that stuck in the craws of a few readers was my comment about "insensitive or ignorant teachers." Apparently, it's not okay to mention that we have these people in our profession.
Even if that were NOT okay (which, of course, it is), your context--"one of my nightmares"--is hypothetical.
Sheesh.
Workspace math--as I call it--is (mostly) what this is, and it is certainly not an irrelevant area of inquiry in mathematics education, especially for those of us who are old assessment hands, and/or anyone who cares about error reduction/prevention.
For example, errors made by students while trying to remember, or "keep track of," numbers and their positions in, say, multidigit multiplication problems and long division problems I refer to as "tracking errors." And in workspace math, tracking errors are, in my experience, among the most common.
In fact, errors like these are why many state tests (Florida comes to mind) use an ABCD - FGHJ format for multiple-choice answer sheets.
The "workspace" aspect of slope problems presents tracking difficulties as well. Even in a simple slope problem where two ordered pairs [say, (1, 3) and (2, 4)] are given, and students must find the slope of the line that connects them, there are opportunities for tracking errors (same thing with FOIL), especially when students are usually expected to convert the horizontally oriented ordered pairs into a vertical setup.
At the very least, Lisa's method could help reduce these tracking difficulties.
I have seen a set of these for slope, distance, and midpoint. I'm not crazy about increasing the number of formulas in use, but if a kid uses it well, or just needs a little correction, that's fine.
I usually introduce, especially with weaker or younger students, distance vs time graphing (this is New York, I use sequentially numbered streets - 1st 2nd, 3rd... - for the y-axis).
Kids find speed without difficult. It makes for a very easy transition to slope, without an early introduction of any formula, standard or non-standard.
Jonathan
Two comments - I tried a couple of days ago to leave comment but I don't think it worked...
First, what's the point in teaching formulas in a math class, particularly in those classes that reflect the vision of the NCTM? It seems like mnemonics (FOIL, PEMDAS, etc.) or any other support that help students "remember" formulas seems to be inconsistent with the vision of the classroom. In those classrooms, what's important about formulas is the process of deriving them. It seems like for things like determining slope or multiplying 2 binomials, there is no need for a formula or mnemonic.
Second, I think many teachers agree that "we can learn from our mistakes," but they don't always teach students how to learn from their mistakes. If a class never confronts mistakes head on, comparing and contrasting incorrect solutions with correct solutions, students will not going to learn to learn from their mistakes - mistakes will then become simply something to be avoided at any cost.
(a) How is Lisa's method a different "formula"? It's just y2 - y1 / x2 - x1. The fact that it's in long division format doesn't change that.
(b) It seems like mnemonics (FOIL, PEMDAS, etc.) or any other support that help students "remember" formulas seems to be inconsistent with the [NCTM'S] vision of the classroom.
Yeah. It does SEEM like that. : )
(c)Mistakes will then become simply something to be avoided at any cost.
My bad. Let's alter all of procedural mathematics to make the methods as confusing as possible.
Gimme a break.
A few follow-up thoughts in no particular order relative to recent comments.
First, the point of my article was more to encourage teachers to pay attention new ideas from kids of any kind (including erroneous ones), to be prepared to think about the implications of new ideas and methods kids come up with - whether on the spot, as a basis for future class explorations, an investigations for one or more students, or some other avenue of contemplation and experimentation - which means being knowledgeable about the mathematics one teaches, how it fits to previous and upcoming mathematical ideas beyond one's immediate grade band, and open. If you never listen to kids, or fear to do so, or don't take what they say seriously, or simply are not convinced it's possible or valuable to spend class time on heuristic examples of student thinking, you're selling everyone in your classroom short (including yourself).
That said, I don't see Lisa's Method as something that HAS to be taught, but it would make for an interesting pedagogical experiment to see how students respond to this alternative (or another, if you've got one at hand). Further, I think that if her method IS in fact effective for some kids and reduces their errors in calculating slope, how can it be bad? That doesn't mean you wouldn't continue to strive for conceptual understanding of slope (from algebraic, numerical, and graphic-geometric perspectives), but merely that you might save SOME kids a significant amount of frustration and grief if you give them an approach that works FOR THEM.
I don't know that there's really any single official "NCTM" viewpoint on algorithms, mnemonics, etc., nor do I frankly care if there is one and I'm running counter to it. My frustration in part with the response reviewers and editors gave my paper was that it seemed in no small part to be dismissal BECAUSE it was "merely" focusing on a procedure. Duh. Procedures ARE part of doing math. I certainly wasn't suggesting that this method or ANY other be taught devoid of conceptual understanding. But the fact that it looks at an original STUDENT procedure makes it pedagogically important (or potentially so). The negative response felt dogmatic and doctrinal, as if one or more readers feared to take the piece seriously for fear of being in violation of some religious precept: THOU SHALT NOT CONSIDER PROCEDURES, ALGORITHMS, OR MNEMONICS!
Of course, I may have that wrong. But it smelled kind of funny to me, especially given the positive response the piece got from several knowledgeable readers - a high school teacher, and the editor of another math teaching journal, to name two. Funny that neither of those readers was put off in the least by the specific math topic.
Frankly, I think I got robbed. More importantly, I think kids and teachers and Lisa got robbed, which is why I decided to go ahead and publish the piece on my blog rather than try to figure out how I would have to redo it to please the folks at the appropriate NCTM journal. (And yes, I'd love some cheese with this whine: anything in a nice cheddar would be swell).
probably one shouldn't expect
math ed journals to be interested
in comprehensible discussions
of mathematics or education--
of *course* you got robbed.
with that said, what interests me
*most* about this piece is:
having, first of all, congratulated
lisa on some creative (and correct!)
mathematics, and if at all possible,
sharing her technique with her class
(with heartfelt public praise to her),
can i go *on* to convince even some
of the class that the issue of
procedures-versus-"formulas",
there can *be* no right "answer".
coming up with one's own approaches
is vital--it's what we call
"doing mathematics", indeed.
but one darn well has to be sure
to try to understand the "standard"
notations (and algorithms etc.)
when they exist. we shouldn't hope
to *replace* "rise over run"
[or (y_2 - y_1)/(x_2 - x_1)]:
lisa's method is as much a method
for *understanding* slope (*and*
the formula that defines it) as
for computing it. thanks for
an interesting post; keep 'em guessing.
http://vlorbik.wordpress.com
J.D.
I wrote, "Mistakes will then become simply something to be avoided at any cost."
You then said, "Let's alter all of procedural mathematics to make the methods as confusing as possible."
Could you care to explain how you are getting this conclusion from what I said? I am totally perplexed.
Sure, Tad.
The discussion going on here is about a student's (Lisa's) "method" for calculating slope.
Michael points to the fact that this method might be beneficial because it makes the calculation a little easier:
I asked her [to] explain why this seemed like a good way to her. She said, “Well, we always did subtraction problems like that: it seems easier to me when the numbers are lined up this way.” I told her that I thought she might have invented an original approach that made sense, and that I was going to write up what she’d done for publication so that other teachers would have a chance to share it with their students.
And of course the gist of MY comment was to back up Lisa's idea with some arguments related to error reduction/prevention.
After all this (and having had two tries at it), you said:
I think many teachers agree that "we can learn from our mistakes," but they don't always teach students how to learn from their mistakes. If a class never confronts mistakes head on, comparing and contrasting incorrect solutions with correct solutions, students will not going to [sic] learn to learn from their mistakes - mistakes will then become simply something to be avoided at any cost.
If your statement above has anything to do with the discussion at hand, then it would almost certainly be an attempt to argue that Lisa's method (or, rather, a method that might reduce/prevent error) actually undermines the lofty goal of letting students "learn from their mistakes" or "confront mistakes head on."
It's not too hard to follow from this that ANY method used in an elementary or middle school classroom that helps to reduce/prevent error in workspace mathematics would, according to your reasoning, undermine this goal.
What you are suggesting (or implying) then is that we should make all of procedural mathematics as confusing as possible to students.
THAT'S how I "get this" from what you are saying. Because you said it.
Thank you, JD.
So, as you quoted, I said,
I think many teachers agree that "we can learn from our mistakes," but they don't always teach students how to learn from their mistakes. If a class never confronts mistakes head on, comparing and contrasting incorrect solutions with correct solutions, students will not going to [sic] learn to learn from their mistakes - mistakes will then become simply something to be avoided at any cost.
As I read Michael's description of his work with Lisa, what struck me was that she confronted her mistake and invented a new procedure (actually it is more like a new notational system as someone else pointed out, what she is doing, i.e., her procedure, is really the same as what is indicated by the traditional notation). So, to me, the key in this episode is her reflection on her own errors.
If you, then "transfer" this notation system to someone else just as you would teach the traditional notation system, I don't see much benefit in helping students understanding what is going on.
What I said is that if we don't confront students' errors - by explicitly making it a focus of discussion and reflection, whether done individually or as a group, then, we are not helping students to learn from their mistakes. If we don't consider mistakes as potential sources of learning and just teach procedures that may reduce those errors even if students' don't understand why, then, we aren't really helping students learn. I am advocating allowing students to make errors and having them discuss the errors instead of simply teaching "short cuts."
So, I do not get to the same conclusion as you do.
p.s. nice redesign.
you might wanna lose
the "bush countdown" ...
Let me first say that the ideas involved in this discussion have set off my "I'm going to post about this" button. So, um, I'm going to post about this.
Second, I'd like to point out this "seeming" contradiction (italics for emphasis are mine).
First we have this:
What struck me was that she confronted her mistake and invented a new procedure (actually it is more like a new notational system as someone else pointed out, what she is doing, i.e., her procedure, is really the same as what is indicated by the traditional notation).
Then we have this (again, ital is mine):
I am advocating allowing students to make errors and having them discuss the errors instead of simply teaching "short cuts."
(1) How is it that this "new notational system" is both (a) "the same as what is indicated by the traditional notation" and (b) a "short cut" that would, apparently, disallow discussion of errors?
(2) What kind of valuable "discussions" would you imagine students having when they find that they make errors in substituting horizontally written coordinates into (vertical) ratio formats?
If you encourage this sort of stuff, it pops up, and with some regularity.
Point out what's new or different. Discuss what's easier, harder, better, or worse. Most importantly, make sure to identify it as correct, if it is, not so, if it is not. And make certain kids know how general it is, or is not.
Of course I have an advantage: I have each kid in my classes putting up 1 - 4 homework problems, of their own choosing, each week. I add to the advantage - they get credit no matter how good or bad, correct or incorrect, standard or strange their work is.
Means there's lots of material to discuss. Lots of variation that will occur. Lots of opportunities to reflect on different correct approaches.
In addition, when something really does look different, but is okay, we name it after the 'inventor' - gives a little extra ownership to the kiddies.
And then there are those kids who intentionally choose to grab their classmates' methods, to be different from me (and sometimes the book - we can always discuss where the teacher and the book diverge).
I end up seeing and (re)naming student-generated variations, I'd guess once or twice a month. In that sense, what Lisa did did not seem to me at all extraordinary. I wouldn't dismiss it, and I would absolutely celebrate it in class. And I would certainly encourage kids to continue to share alternates that they find/use.
But I don't think I would introduce this method elsewhere.
Anyhow the point of your article:
"... was more to encourage teachers to pay attention new ideas from kids of any kind (including erroneous ones)"
is a good point, and matches, I think, some of my practice. But it takes a lot of confidence in a teacher's mathematics to be willing to consider student ideas. And as mathematical knowledge is often lacking, especially at the lower grades, so is that confidence.
Jonathan
I really like Lisa's procedure for finding slope. I think that in many ways, this is a great tool. It works like how I calculate slope in my head: I work with points and not with discrete numbers as the "(y2-y1)/(x2-x1)" formula does. Also, the fact that the points are placed together should help students see whether the slope should be positive or negative as a double check on their work.
You said:
"First, the point of my article was more to encourage teachers to pay attention new ideas from kids of any kind (including erroneous ones).."
I have always found this a discouraging trait of math teachers. I do not think that teachers are not paying attention to students or want to stifle their creativity in mathematics, but the problem is that their knowledge of mathematics is simply not deep enough for them to consider any process other than what they know.
I had a fellow math teacher come into my room the other day to question an alternative approach to factoring that was shown in our textbook. He has been teaching for about twenty years and is considered a very good teacher who really knows the material he teaches. He asked me if the method was correct (although both yielded the same result on problems) and when I confirmed that it was correct mathematically, he asked me if he was teaching it wrong with his method and if he should start teaching the process like the book showed it. He was genuinely concerned that he was teaching students incorrect thinking and couldn't work out for himself that both methods obeyed the laws of mathematics.
It is when situations like that are placed in front of me that I am reminded why students ideas are stifled and mathematics is taught in a "do it my way or fail" way. I don't think that teachers who really understand math would ignore a new solution method because they understand how creative mathematics is and they can evaluate whether or not the method is correct. It is incredibly sad that most teachers seem to have a shallow understanding of mathematics because students then don't get to experience the beauty of finding a deeper way to understand the material that they are being presented.
My apologies to those who have been kind enough to make useful comments on this post. I've been more than a little behind in my work when it comes to responding (or even reading and thinking about) what has been added lately.
That said, I will merely add to the most recent comment that my suggesting that some teachers are either unwilling or unable to process what kids come up with in class was deemed too harsh by the editors and reviewers at the NCTM middle school math teachers journal (one of the countless sins that prevented them from publishing the piece). My take was and remains that I cut a little too close to the bone for their liking with that remark, and I'm 100% confident that my observation was true and on-point. That it was too threatening speaks volumes about far too many teachers. But what it says about the establishment at NCTM is telling, too. Heaven forfend an article should threaten those teachers who need to rethink their practices. Might lose some subscriber/members!
Of course, my other great sin was talking about something that was "merely" procedural. But I don't invent incidents to suit NCTM dogma, and procedures are indeed part of math class. A clever idea by a student on how to do a calculation or even just to set one up is still an example of what teachers need to both be able to respond to intelligently and sensitively, and to encourage.
What those reviewers who complained that I'd promised a piece on concepts and delivered one on procedures seem to have missed was that: a) I had promised nothing of the sort, and b) there is a point where it makes very little difference whether a student is being clever about concepts or procedures: the important thing is that this was about a student in an at-risk program who was actually THINKING AT ALL about mathematics, and who was willing to take a risk by suggesting that there was another way to do something besides that given in "received wisdom." Had I been someone else, I could readily have put her down subtly or more directly by failing to look and take seriously what she'd done. Thinking is thinking is thinking. I don't believe she came up with a new proof of Fermat's Last Theorem or an original piece of mathematics. But so what?
Post a Comment