…Oh Sorry about that. I just had to put the finishing touches on a proposal for an elearning project. Now comes the tough part: the waiting.
In the mean time, let’s get back to our topic on how to relate the “Show. Don’t tell” principle that get’s preached in screenwriting circles to our elearning projects.
One important mantra related to “Show. Don’t tell” is: “Get in late. Get out early.” Besides being my philosophy for shopping at Wal-Mart, the idea here is that you want to get people into the action as soon as possible while, at the same time, providing context and back story in the most efficient way possible without “telling” too much—hence the “get out early” idea.
Have you ever seen a movie that takes too long to get into the meat of the story or watched a scene that was drawn-out to the point where you thought, “Ok, ok…we get it!”? It’s painful. This type of thing is a sure recipe for a tuned-out audience because the story starts to drag.
Usually, writers of these scripts worry that the audience won’t get the back story or understand the subtle nuances of the character and so try and “tell” us what a character is like up front with lots of dialogue or flash backs before the story engages. Sure, the set-up to a story is crucial, and the first ten pages are the most important of the entire script, but it has to be carefully crafted and very succinct. A writer should only give the audience enough information to get them started so that they can build on their knowledge later in the context of the story. The main job of the set-up is to provide a hook that propels us into the heart of the story.
Let me illustrate. Put up your hand if you’ve seen the original Karate Kid. (Come on! I’m sure you’ve tried that crane -kick-move more than once!) Despite its cheesiness, screen writers often use this movie to illustrate good screen play structure. When we first meet Mr Miyagi in the first few pages of the script, we don’t know much about him other than: a) he is the superintendent of the building that Daniel lives in, b) he seems to like Daniel right off the bat, c) he is a bit mysterious, and d) he has a dry sense of humor.
We don’t find out until much later that he was a pilot during the second world war, knows Karate, and still grieves the loss of his wife over a bottle of Saki (sorry for the spoiler). Here, at the beginning of the story, we only get enough information to know that he will be important later on. If the writer would have had Mr. Miyagi explain his whole sordid history on their first encounter with Daniel, we would have totally lost our engagement with the main character and it would have taken away from the big picture of the story.
Now let’s relate this to eLearning. Face it, a lot of elearning titles are a little slow getting out of the gate. They take too long to get to the action, and by the time they do, we’ve lost interest in the content. Often this comes in the form of a long-winded introduction telling us what the course is about and the copious amount of time (usually in the form of text) spent describing the objectives. It may also come in the form of instructions on how to navigate the course, use the help, how to exit, and how to avoid repetitive stress syndrome while clicking through the course intro.
Don’t get me wrong, I’m all for objectives and I am not saying that we shouldn’t do some of these things (or maybe I am) but we need to be careful about front-end loading our learning so that it takes a half an hour just to find out how to use a course. At the very least, we should not force people to sit through everything if they don’t want to. We need to design our courses so that these things are self-evident. If we design for the ten percent who don’t know how to click a forward arrow, then we are in big trouble (and so is the ten percent). I think it’s always best to get our learners into the content early so that they can be hooked into it and get where they are going. If we don’t, we risk losing the ninety percent.
If you are wondering how to do this, go look at any popular kid’s video game and you will see some principles. The best ones, show kids how to use the interface while they actually do things in the game–while they are already engaged in the story. The designers of these games try their best not to take learning out of the context of the story in order to teach the kids how to do something. This takes some thought and solid user interface design but is worth it.
I have also come across elearning courses that teach how to use specialized software packages but spend more time up-front on how to navigate the software than on teaching how to use it to perform a job-related task (if they do at all). So first, you have to sit through pages on how to use the course, and then endure pages that teach you how to navigate the software. That’s just not a good use of time and it’s as boring as________. You fill in the blank. (You see what I did there? I made this blog posting interactive!)
I guess my point is, let’s teach people how to use the software to do their jobs and teach them how to use the “features” of the software in context of actually doing something. Let’s not always feel like we need to get in at the beginning, but rather, let’s get in late and get out early and maybe our learners will have some time left over to catch the next show. Besides, personally, I find that all that front-loaded information presented out-of-context just tends to get lost in the eternal sunlight of my spotless mind.
I remember fondly when I got my first Xbox. (I say “first” because I’ve had several since due to problems with the original one and the famous red-ring of death that plagued its successor). I also recall the intimidation I felt with the significant learning curve that faced me. My kids had been schooled in this technology from a young age but, you see, I was an old PC gamer from the days of “A Mind Forever Voyaging” and “Kings Quest” and couldn’t quite get a handle on the transition from mouse and keyboard to console controller. As a good father, however, I was committed to this paradigm shift. I didn’t want to be like all those TV dads who were never there to blow stuff up with their kids. I am proud to say that today, I am pretty comfortable with the console control scheme but I still tend to flail my arms around as if conducting an orchestra when playing more action oriented games. Consequently, I am not what you would call an elite player of console games.
One of the most popular games of all time soon found a happy place in our home. The Halo series by Bungie, featured an engrossing epic sci-fi story and iconic character called The Master Chief. Even though in the real world I am more committed to peace than Ghandi, for a brief time, after cleaning the bathroom on a Saturday, I could be the Master Chief – a Spartan super soldier. He didn’t have to take out the garbage or separate the compost from the recyclables. But, oh yes, he did take out the “trash” — in the form of our insidious galactic enemies.
Halo was a very popular game during its initial release, yet it wasn’t until after Bungie mastered the multiplayer aspect of the game in Halo 2 that it really took off. Bungie and Microsoft, through Xbox Live enabled large amounts of players to get into “maps” and play together. They could talk to each other with microphone and a headset, add friends to a list, and collaborate online — yes and shoot each as well. My son, (gamer tag: killer_emu) was a virtuoso with a controller and quickly ascended very high up in the ranking system created for the game. I remember watching him in awe while at the same time bemoaning the hand-eye coordination that age had pillaged from me.
Below is my fierce Gamer Tag
[iframe http://gamercard.xbox.com/Wonder%20Bunny.card 240 160]
What really got my attention, however, was when I noticed that my son and his online friends had suddenly abandoned the game as it was intended to be played and started to collaborate to do something completely new. To my amazement, they began to cooperate and take advantage of “glitches” in the system to do things the designers did not intend. These were not things you could accomplish on your own. You would need to stop shooting each other, at least for a while, and work together. Because the Halo 2 game mechanics were very physics-based, players could do some very creative and interesting things within the “sandbox” environment. They could get outside of the 3D map boundaries and get into and on top of places that they were not supposed to go. They found ways to fly across maps, perform amazing jumps with vehicles, and arrange spectacular acrobatic demonstrations complete with pyrotechnics. Teams of gamers would get together and record movies in which they displayed their creative prowess and post them on the internet. Some, like the people who did the Red VS Blue movies, even created short films using Halo as a Machinima tool.
Don’t get me wrong, I am not saying this was necessarily a new phenomenon. It had been done with other games before. But somehow I noticed it more. Here are a couple things I learned that relate to online learning:
Some people just like to break things — especially the rules. For an online learning environment, this means that we need to be aware that some learners are not content to be driven “along the rails” of our learning environment. They want to get off the ride and explore on their own. Sure, many will still follow the more linear narrative of our course like those who would play the single-player version of Halo; however, we also need to give them at least the opportunity to feel the freedom in some way. Web 2.0 has the idea of flexibility at its core. People want a multi-faceted learning environment where they can get their own information and not necessarily be forced into single-sourcing their experience.
This means that we need to provide learners with interactivity options. We should provide the freedom to navigate around so that learners can focus on what interests them at the time instead of always driving them to a destination. Obviously for some content, we want to make sure learners absorb critical information but we may provide branching paths or even the same information delivered in a different way to accommodate these freedom fighters. What it definitely means is that we need to be careful about forcing people to do stuff whether it’s forcing them to take multiple tries on a quiz before they can proceed, or forcing them to perform long “click this, type that” simulations in order to get to the next section. I am not just saying we need to provide the latest cool innovation, sometimes it means scaling back our dreams for a more conservative audiences who like a simple text-based elearning course with clearly presented, accurate and succinct content.
The Principle of Accommodation
When Bungie and Microsoft saw this growing community of “glitchers,” instead of totally clamping down on this new way of playing, they decided to build the Forge system into their next release of the game. This allowed users to customize maps by changing variables in such a way that those hosting the game could create very unique game experiences. Even in Halo 2, there was a lot of customization but with Halo 3, Bungie upped the ante. Bungie responded to what was happening instead of forcing people to play it like they wanted it to be played. Game companies that fail to respond to the new ways the community thinks about their experience will quickly find themselves losing ground in the industry. Too often this still happens in education. We force people to listen to audio with no way around or crowd the screen with reams of text not essential to the learning. We don’t provide good enough navigation so users can’t find what they are immediately interested in and we sometimes don’t provide enough options for different types of learners. Consequently learners tune out and miss some creative learning opportunities. I’m guilty of building this type of learning.
Community is King
A lot has been made of Social Networking these days. Many eLearning professionals are grappling with what this means for their training. The Master Chief taught me that people in community can accomplish things beyond what we can teach them through traditional methods. Once gamers were given the means to collaborate online, they shared information, planned, learned and cooperated instead of competed. What I think helped was the fact that the game integrated the social networking technology. Users didn’t have to leave the game in order to learn. They could just ask others how to do it or get them to show them. Users were involved in the material and could explore right then and there without going out of context. For me, this means that social networking technologies must be as integrated as possible into our learning environments for those who need it. If I am doing an online course, I might want others who are taking the same course be available to chat with me if I had questions. I might want an expert available to me at set times to get more detailed information. Maybe people need to start taking elearning courses “together” in some way. I’m not exactly sure how this would look given the various budgets and time constraints but it’s something to think about.
I realize that organizations often implement eLearning in order to cut costs and that having an online trainer available at all times might not work. But we must look for ways for people to learn from each other. When that happens, creative solutions arise. Learning should not be single-sourced. Maybe, in large companies, we need to build in incentives for subject matter experts to share with others and the mechanism to make that possible. Maybe it’s regularly scheduled time to work on a Wiki, moderate a discussion forum, or conduct an online web seminar. Can we make teaching others part of everyone’s job instead of leaving it to the trainers? Whatever way we can do it, we need in some way to provide that social aspect to learning for those who learn that way. Good software will enable this – but an organizational mindset that makes learning everyone’s responsibility is essential.
So these are a few things I learned from The Master Chief.
Now, anybody know what I can learn from Mario?