This past summer, our forward-thinking math-teacher-centric friends at Desmos released Activity Builder into the wild, and the collective creativity of the math world has been evident as teachers work to find exciting classroom uses for the new interface. Many of these activities are now searchable at teacher.desmos.com – you’re welcome to leave now and check them out – but come back…please?
Its easy to get sucked in to a new, shiny tech tool and want to jump in headfirst with a class. I’ve now created a few lessons and tried them with classes which range from the “top” in achievement, to my freshmen Algebra 1 students. In both cases, I’ve settled upon a set of guiding principles which drive how I build a lesson.
- What do I want students to know?
- What path do I want them to take to get there?
- How will my lesson encourage proper usage of math vocabulary?
- What will I do with the data I collect?
- How does this improve upon my usual delivery?
It’s the last question which I often come back to. If making a lesson using Activity Builder (or incorporating any technology, for that matter) doesn’t improve my existing lesson, then why am I doing it?
One recent lesson I built for my algebra 1 class asked students to make discoveries regarding slopes and equations of parallel and perpendicular lines. Before I used it with my class, a quick tweet 2 days before the lesson provided a valuable peer-review from my online PLC. It’s easy to miss the small things, and some valuable advice regarding order of slides came through, along with some mis-types. The link is provided here in the tweet if you want to play along:
The class I tried this with is not always the most persistent when it comes to math tasks, but I was mostly pleased with their effort. Certainly, the active nature of the activity trumped my usual “here are bunch of lines to draw – I sure hope they find some parallel ones” lesson.
As the class finished, I called them into a small huddle to recap what we did. This is the second lesson using Activity Builder we have done together. In the first, the students didn’t know I can see their responses, nor understand why it might be valuable. In this second go-round, the conversation was much deeper, and with more participation than usual. In one slide, the overlay feature allowed us to view all of our equations for lines parallel to the red line:
We could clearly see not only our class successes, but examine deeper some misunderstandings. What’s happening with some of those non-parallel lines? Let’s take a closer look at Kim’s work:
What’s going on here? A mis-type of the slope? The students were quite helpful towards each other, and if nothing else I’m thrilled the small group conversation yielded productive ideas in a non-threatening manner – it’s OK to make errors, we just strive to move on and be great next time. The mantra “parallel lines have the same slope” quickly became embedded.
The second half of the lesson was a little bumpier, but that’s OK. Before questions regarding slope presented themselves in the lesson, storm clouds were evident when the activity asked students to drag a slider to build a sequence of lines perpendicular to the blue line. Observe the collective responses:
So, before we even talk about opposite reciprocal slopes, we seem to have a conceptual misunderstanding of perpendicular lines. I’m glad this came up during the activity and not later after much disconnected practice had taken place. In retrospect, I wish I had put this discussion away for the day and come up with a good activity for the next day to make sure were all on board with what perpendicular lines even look like, but I pressed ahead. We did find one student who could successfully generate a pair of perpendicular lines, and I know Alexys enjoyed her moment in the sun.
What guiding principles guide you as you build activities using technology? How do they shape what you do? I’m eager to hear your ideas!