May 07, 2006
Ajax and Hebrews
For the past three months or so I've been teaching a Sunday School series on the book of Hebrews. And, of course, like a good Presbyerian my preferred mode of communication has been the lecture. I have been doing my best to describe what the book is about on a very theoretical level. I have tried very hard to articulate the historical background of the book because understanding it is so vital to understanding the book as a whole. To that end I have spent a lot of time repeating myself and reminding the class not to forget the peculiars of the historical background. I feel compelled to do so because I know prone I am to take each passage in isolation. Besides, isn't repetition the best way to make concepts stick in our brains? If I want my class really to understand the book, I just need to repeat myself over and over and over again, right?
A few weeks ago, I had a wonderful revelation from a most unexpected source. I was reading the introductory pages of a book I recently got on Ajax (asynchronous JavaScript and XML), a relatively new web development method. Obviously, I wasn't looking for tips on teaching my Sunday School class from a computer book. After all, teaching the Bible must be done by a hallowed lecture, right? Yet, the author was describing my challenge as a teacher of the Bible to a tee. I may be able to get the point across to give my class understanding. But then my question is, do we remember those theoretical concepts? If I understand something, what good does it do me if I don't remember it?
This dillema was answered in large part by the methodology that this book is promoting. Let's look at what Brett McLaughlin is saying.
So what does your brain do with all the routine, ordinary, normal things you encounter? Everything it can to stop them from interfering with the brain's real job--recording things that matter. It doesn't bother saving the boring things; they never make it past the "this is obviously not important" filter. [Boring? ouch!]
How does your brain know what's important? Suppose you're out for day hike and a tiger jumps in front of you; what happens inside your head and body?
Neurons fire. Emotions crank up. Chemicals surge.
That's how your brain knows...
This must be important! Don't forget it!
But imagine you're at home, or in a library. It's a safe, warm, tiger-free zone. You're studying. Getting ready for an exam. Or trying to learn some tough technical topic your boss things will take a week, ten days at the most.
Just one problem. Your brain's trying to do you a big favor. It's trying to make sure that this obviously non-important [again, ouch!] content doesn't clutter up scarce resources. Resources that are better spent storing the really big things. Like tigers. Like the danger of fire. Like how you should never again snowboard in shorts.
And there's no simple way to tell your brain, "Hey brain, thank you very much, but no matter how dull this book is, and how little I'm registering on the emotional Richter scale right now, I really do want you to keep this stuff around" (xxiii).
As I said, McLaughlin sets out to solve this challenge. He asks the question, "So just how DO you get your brain to treat Ajax like it's a hungry tiger?" Here's his answer:
The faster way is to do anything that increases brain activity, especially different types of brain activity. . . More neurons firing = more chances for your brain to get that this is something worth paying attention to, and possibly recording.
No, he hasn't hit upon anthing that is completely revolutionary. I suspect that the reason we so rarely witness this type of education is that it takes extra work. It is easier just to gather the facts, organize them, and lecture them. (Zzzzz) I got inspired when I saw some of the practices McLaughlin impliments in his book.
Some of the Head Rush learning principles:
Make it visual. Images are far more memorable than words alone, and make learning much more effective (up to 89% improvement in recall and transfer studies). It also makes things more understandable.
Use a conversational and personalized style. In recent studies, students performed up to 40% better on post-learning tests if the content spoke directly to the reader, using a first-person, conversational style rather than taking a formal tone. Tell stories instead of lecturing. Use casual language. Don't take yourself too seriously. Which would you pay more attention to: a stimulating dinner party companion, or a lecture?
Get the learner to think more deeply. In other words, unless you actively flex your neurons, nothing much happens in your head. A reader has to be motivated, engaged, curious, and inspired to solve problems, draw conclusions, and generate new knowledge. And for that, you need challenges, exercises, thought-provoking questions, and activities that involve both sides of the brain, and multiple senses.
Get--and keep--the reader's attention. We've all had the "I really want to learn this but I can't stay awake past page one" experience. Your brain pays attention to things that are out of the ordinary, interesting, strange, eye-catching, unexpected. Learning a new, tough, technical topic doesn't have to be boring. Your brain will learn much more quickly if it's not.
Touch their emotions. We now know that your ability to remember something is largely dependent on its emotional content. You remember what you care about. You remember when you feel something. No, we're not talking heart-wrenching stories about a boy and his dog. We're talking about emotions like surprise, curiousity, fun, "what the...?", and the feeling of "I Rule!" that comes when you solve a puzzle, learn something everybody thinks is hard, or realize you know something that "more-technical-than-thou" Bob from engineering doesn't.
This is good stuff. Again, not revolutionary, but so rarely implemented. So I decided to try something new, something different, something surprising. I have created a fictional, though realistic story of a young man named Simon from Troas, who lived in the time of the writing of the book of Hebrews. In fact, he was one of the typical recipients of the letter. Then, I turned that story into a reader's theater drama to be acted/read by members of the Sunday School class. We have done it for two weeks now, and though my drama writing skills can stand plenty of improvement, I think the people have enjoyed it. And, I'm pretty sure they understand the material and will remember it much better than they ever would have before. If I get the time and inspiration, I will post the first two episodes of "Simon's Dilemma" in the next few days.
Posted by jhyink at 03:58 PM | Comments (1)