[Lessons from Game Design] Piggybacking

This is from a series of posts called Lessons from Game Design in which I apply some of the lessons of game design to the art of teaching.  For some background as to why I am doing this and why I think game design is relevant to teaching, see my Introduction post.

Piggybacking

Several years ago, the makers of Magic noticed that they were having a problem holding onto new players because of the growing complexity of the game.  The designers’ response was to take advantage of something known as “piggybacking”.  The idea of piggybacking is to design around an already well-understood concept.  This reduces the cognitive load required to process a certain concept.  Take the following Magic card text as an example of what something could look like without piggybacking:

Confused?  What does this card do?  There may be a lot of unfamiliar terminology and syntax here.  Let me show you the rest of the card to see if that clears things up at all.

Despite the fact that you still may not understand what some of those terms mean, you probably have a much better idea of what the card does simply because you are familiar with Medusa.  Medusa turns people into stone by looking at them.  Stones are perfectly capable of acting as obstacles, but they certainly can’t attack you.

Another great example of piggybacking (which is described in the linked article) comes from the game Plants vs. Zombies, which is an implementation of a game style called tower defense.  In a tower defense game, you must defend something from an incoming attack force by strategically placing immobile defense units.  As the game goes on, the attack force becomes more dangerous and you get access to more powerful defenses.  One of the particular defense units in Plants vs. Zombies is called the Pea Shooter, which shoots peas at incoming zombies.  The upgraded version of the Pea Shooter deals more damage, but as a designer how do you convey the fact that it deals more damage in clear, obvious way?  The solution was to call the upgraded version the Repeater, and it shoots two peas at a time.  The designers are piggybacking off of the familiar concept that two is more than one.

How can we use piggybacking in order to prevent our students from disengaging when they encounter difficult material?  Here are some ideas that come to mind, some of which may be obvious as established teaching methods, and some of which may be new to you:

  • Use metaphors and analogies.  Better yet, have students develop their own analogies.  That way, you don’t run the risk of dated pop-culture references — when discussing how I solve physics problems, I used to ask my students to imagine the blank white room from The Matrix; that reference is becoming less useful with time — and the analogy is more likely to be remembered by the student.  One of the most successful analogies in my years of teaching came from a student when we were talking about RC circuits; he said that a discharging capacitor was like a water balloon with a hole poked in it.  A thicker hole would cause the balloon to empty faster.  Similarly, a resistor with a large cross-sectional area will cause a capacitor to “empty” faster.  The subsequent exam showed an unprecedented level of understanding of RC circuits for virtually everyone in the class.  By the way, an important step to any analogy is also to discuss where the analogy starts to break down.

  • If a particular student is struggling, try to use what you know about the student to create a situation that is more familiar to that student.  For example, let’s say that Bob is having a difficult time doing a projectile motion problem involving a cannon shooting a cannonball off of a cliff.  You remember that Bob is on the basketball team, so you cosmetically change the problem to one where he is shooting a basketball into a hoop.  The effect of cosmetic changes like this may not be intuitive, but it is true nonetheless; I once talked to a New York State Regents physics exam writer, and he told me that they have a list of words and phrases that they are supposed to avoid because those words and phrases have been found to create demographic biases in scores.

  • Put the concept before the name.  Most lessons naturally build off of previous lessons; however, if you start the day by saying, “Today we are going to learn about something called X”, then you are creating a new chunk in the brain for “things related to X”.  If you decline to give the topic a name, then the student is more likely to try to understand the new information by assimilating it with what is already there.  This helps the student piggyback the new information with old information.  For example, let’s say that you want to introduce your students to the concept of multiplication.  One approach would be to ask the question “How many is five fours?”.  In the absence of a definition for multiplication and its rules, students are likely to answer the question in the only way that they know how, which is to do 4+4+4+4+4=20.  When the term “multiplication” is introduced after several examples, the term is more likely to be understood as a form of addition rather than a new operation with its own separate set of rules.

  • Introduce an idea with concrete examples rather than starting off in the abstract.  Dan Meyer has written a lot of excellent material on this subject, and I highly recommend it.  As teachers, often our goal is for students to transfer what they learn from one example to a wide range different (but similar) examples.  This requires having a general understanding of the topic/rule/law.  In other words, an abstract principle is applied across a variety of specific contexts.  A common teaching technique is to start off in the abstract, then demonstrate the utility of the abstract idea by working a concrete example.  The problem with starting in the abstract, though, is that the students have no prior knowledge with which they can piggyback the abstraction.  A solution that takes advantage of piggybacking would be to start off with a concrete example, then build up with an example that requires abstraction.  For example, lets say that you want to teach how to sum all of the integers from 1 to N.  The general answer is that the sum is N(N+1)/2.  You could start with the abstract notion of the sum as well as the generalized answer for the sum, then have the students work a concrete example.  Alternatively, you can start with a concrete example that piggybacks off of something familiar, say the number of bowling pins in a bowling triangle, then work toward the abstraction by showing this:

Who wants to count that?  They’ll be begging for a generalization.  Once again, Dan Meyer is a treasure trove of wonderful ideas in this vein, and I will be talking more about the Three-Act method in later posts.

Are there other ways you can think of to use piggybacking?