Writing
Meaning before procedure
Why I try to show students what an idea is for before I show them how to use it.
A lot of school mathematics arrives as a rule. The area under a velocity time graph gives you displacement. To differentiate, bring the power down and take one off. Find the shapes, add up the areas, write down the answer. Students can follow these steps and get the marks, and for a while that looks like learning.
The trouble shows up later. Change the question a little and the rule stops being enough, because the student never knew what it was doing. I suspect a lot of “I’m just not a maths person” starts here. Not from a lack of ability, but from carrying a pile of procedures with nothing holding them together.
So when I plan a lesson, I try to put the meaning first and the procedure second. Written down, it sounds obvious. In practice it is easy to skip, because procedure is faster to teach and easier to check.
Take the velocity time graph again. Before any rule, I would rather ask something like this: a car drives at 20 metres per second for 5 seconds, how far does it go? Most students can answer straight away. Then we draw it. The graph is a flat line at 20, and the distance is a rectangle, 20 high and 5 wide. The area is not a trick. It is just speed times time, drawn as a picture.
From there, a sloped line or a curve is a harder version of the same question, and cutting the area into thin strips becomes a sensible thing to try rather than a step to memorise. When the rule finally appears, it is a summary of something the class already understands.
That move, from a question students can already answer to the idea hiding inside it, is most of what I mean by meaning before procedure. It is also why I like to open a lesson with a question or a good example instead of a definition. A good example gives students something to think with. A definition gives them something to copy.
None of this means procedure doesn’t matter. Students still need to practise until a method is fluent, and exams still reward getting it right under time pressure. Once the meaning is there, I model the method carefully using R.A.P.S.: read the question, annotate what it gives you, look for the pattern, then solve. We do one together, then students try on their own. Practice is set by demand, so everyone starts on the core questions and moves on to application and challenge questions when they are ready. Practice comes after meaning, not instead of it.
The other half is paying attention to what went wrong. A short exit question at the end of a lesson is a quick way to find out which part of the meaning did not land. Those mistakes go into the warm up questions at the start of the next lesson, so the class meets them again while they are still fresh.
I don’t think I have this figured out. I am still training as a teacher, and some ideas are genuinely hard to motivate. Sometimes the honest answer to “why do we need this?” is that it becomes useful two topics later. But I would rather start from meaning and sometimes fall short than teach a set of steps and hope the understanding turns up on its own.
That is also what I want my notes, and this site, to do. Start with the question. Build the idea. Then give the method its proper place.