Tag Archives: written instructions

The post where I remind myself that written instructions for computer tasks stink.

It's not so much that I can't follow written instructions. I'm human and I miss steps occasionally, but with everything written down, it's easy to retrace steps and figure out where I went wrong if I did miss something. The big issue is that written instructions are not the best way to show someone how to do something. Text is good for some specific things, but defining steps for completing a task on a computer is not one of them.

Today I showed my students the following video at the start of class.
GEO-U6D2.1-Constructing Parallelogram in Geogebra

I also gave them this image on the handout, which I wrote last year, but students only marginally followed:
Screen Shot 2013-02-27 at 5.53.31 PM

It was remarkable how this simple change to delivery made the whole class really fun to manage today.

  • Students saw exactly what I wanted them to produce, and how to produce it.
  • The arrows in the video identified one of the vocabulary words from previous lessons as it appeared on screen.
  • My ESOL students were keeping up (if not outpacing) the rest of the class.
  • The black boxes introduced both the ideas of what I wanted them to investigate using Geogebra, and simultaneously teased them to make their own guesses about what was hidden. They had theories immediately, and they knew that I wanted them to figure out what was hidden through the activity described in the video. Compare this to the awkwardness of doing so through text, where they have to guess both what I am looking for, and what it might look like. You could easily argue this is on the wrong side of abstraction.
  • I spent the class going around monitoring progress and having conversations. Not a word of whole-class direct instruction for the fifty minutes of class that followed showing the video. Some students I directed to algebraic exercises to apply their observations. Others I encouraged to start proofs of their theorems. Easy differentiation for the different levels of students in the room.

Considering how long I sometimes spend writing unambiguous instructions for an exploration, and then the heartbreak involved when I inevitably leave out a crucial element, I could easily be convinced not to try anymore.

One student on a survey last year critiqued my use of Geogebra explorations saying that it wasn't always clear what the goal was, even when I wrote it on the paper. These exploratory tasks are different enough and more demanding than sitting and watching example problems, and require a bit more selling for students to buy into them being productive and useful. These tasks need to quickly define themselves, and as Dan Meyer suggests, get out of the way so that discovery and learning happens as soon as possible.

Today was a perfect example of how much I have repeatedly shot myself in the foot during previous lessons trying to establish a valid context for these tasks through written instructions. The gimmick of hiding information from students is not the point - yes there was some novelty factor here that may have led to them getting straight to work as they did today. This was all about clear communication of objectives and process, and that was the real power of what transpired today.