Why Floundering Is Good
Wednesday, 25 April 2012
Trying to figure something out on your own before getting help actually produces better results than having guidance from the beginning
The learning paradox is at the heart of “productive failure,” a phenomenon identified by Manu Kapur, a researcher at the Learning Sciences Lab at the National Institute of Education of Singapore. Kapur points out that while the model adopted by many teachers and employers when introducing others to new knowledge — providing lots of structure and guidance early on, until the students or workers show that they can do it on their own — makes intuitive sense, it may not be the best way to promote learning. Rather, it’s better to let the neophytes wrestle with the material on their own for a while, refraining from giving them any assistance at the start. In a paper published earlier this year in the Journal of the Learning Sciences, Kapur and a co-author, Katerine Bielaczyc, applied the principle of productive failure to mathematical problem solving in three schools in Singapore.
With one group of students, the teacher provided strong “scaffolding” — instructional support — and feedback. With the teacher’s help, these pupils were able to find the answers to their set of problems. Meanwhile, a second group was directed to solve the same problems by collaborating with one another, absent any prompts from their instructor. These students weren’t able to complete the problems correctly. But in the course of trying to do so, they generated a lot of ideas about the nature of the problems and about what potential solutions would look like. And when the two groups were tested on what they’d learned, the second group “significantly outperformed” the first.
The apparent struggles of the floundering group have what Kapur calls a “hidden efficacy”: they lead people to understand the deep structure of problems, not simply their correct solutions. When these students encounter a new problem of the same type on a test, they’re able to transfer the knowledge they’ve gathered more effectively than those who were the passive recipients of someone else’s expertise.
In the real world, problems rarely come neatly packaged, so being able to discern their deep structure is key. But, Kapur notes, none of us like to fail, no matter how often Silicon Valley entrepreneurs praise the salutary effects of an idea that flops or a start-up that crashes and burns. So, he says, we need to “design for productive failure” by building it into the learning process. Kapur has identified three conditions that promote this kind of beneficial struggle. First, choose problems to work on that “challenge but do not frustrate.” Second, provide learners with opportunities to explain and elaborate on what they’re doing. Third, give learners the chance to compare and contrast good and bad solutions to the problems. And to those students and workers who protest this tough-love teaching style: you’ll thank me later.
By Annie Murphy Paul
© 2012 Time Inc. All rights reserved