Feedback in scenarios: Let them think!

You’re at the county fair. Your kids are off watching the pig race, and you’re starving. There are only two food carts nearby. One sells deep-fried pork skins from a pot of bubbling grease, and the other sells sushi from a styrofoam cooler. You decide to buy the sushi.

As you hand over your money, a disembodied voice suddenly booms from the clouds above. “Incorrect!” it intones. “Unrefrigerated sushi can harbor zygodread, which can cause severe vomiting. You should never assume that a cooler at a county fair contains ice. It’s always safer to buy hot food that’s cooked in your presence, such as the pork skins. Try again.”

You’ve just met The Omniscient One. It’s the personality-free know-it-all that drones through most elearning. When it intrudes into decision-making scenarios, it sucks the life out of our stories and the brains out of our learners.

“I know everything, and you have no brain”

The Omniscient One (the OO to its friends) is a big fan of telling feedback, because it knows everything. It not only tells us whether it approves of our choice, it also explains exactly how we have sinned and what we must do to atone. Like the folks in your legal department, it believes that no adult can be trusted to draw even the simplest conclusion on his or her own.

An alternative: show the result

In the real world, we’d remember the sushi lesson best if we ate the sushi and then spent three very unpleasant days. In elearning, you could call this showing feedback because, well, the elearning shows (or at least describes) the results. The feedback isn’t a pronouncement from on high but is instead something like this: [Read more...]

Sample branching scenario + cool tool

Branching scenarios can be a pain to design. Happily, you can use a simple tool called Twine to easily draft the scenario and produce it. In this post we’ll look at a scenario that I wrote to demonstrate Twine’s basic features and to make a point about teaching through stories.

In the scenario, you’re a journalist in a hurry to get to a hot story in Zekostan, and your “guide” can’t speak English or drive. You have to quickly learn the necessary Zeko terms to navigate the roads and respond to events along the way. The scenario was inspired by a language-learning activity designed by Kinection.

Try the activity, keeping in mind that it’s a casual, unfinished experiment. Then come back here for more about Twine and my design decisions.

Twine

Twine works in Windows and on the Mac, it’s free, and it publishes scenarios in easily customized, accessible HTML. It’s based on TiddlyWiki, a lightweight information management tool.

Each scene in a scenario is really a small record in a wiki database. The links you create determine the path that the learner takes through the records. Thanks, Steve Flowers, for pointing out Twine in the Articulate forum.

Here’s the flowchart view, which Twine automatically creates as you link your scenes (click for a bigger image):

Screenshot of Twine flowchart view

Twine offers some advantages over other ways to write scenarios. You can:

  • Quickly switch between flowchart view and story-editing mode
  • Link scenes using simple text
  • Add images and sound files and otherwise use HTML
  • Export the story in text format for review and proofing
  • Publish the finished story in HTML
  • Use simple codes to keep track of variables or limit learners’ choices (not shown in the sample scenario)

[Read more...]

Elearning example: Branching scenario

You’re a US Army sergeant in Afghanistan. Can you help a young lieutenant overcome cultural differences and make a good impression on a Pashtun leader?

That’s the challenge behind “Connect with Haji Kamal,” a decision-making scenario that my cool client Kinection and I developed for the US Army. The online scenario is the homework part of a lesson plan that includes in-class discussion about how to build rapport across cultures. It’s part of a much larger effort in the Army to strengthen soldiers’ cross-cultural and peacekeeping skills.

Turn on your speakers and give it a spin, and then come back here if you’re interested in the design decisions behind the activity.

Connect with Haji Kamal

The goals

The activity is designed to be completed as homework before a culture class, and it includes a facilitator guide with debrief questions. Our goals were to model specific rapport-building behaviors and inspire class discussion.

To follow the “good” paths, you need to see things from Haji Kamal’s point of view, show respect and patience, and otherwise apply cross-cultural skills that will be discussed in class. You end up on less successful branches by making more ethnocentric choices. [Read more...]

How to steer your client away from an information dump

For a quick overview of the Action Mapping process described in this interaction, see Be an elearning action hero. For in-depth help with applying this process to your own materials, check out the Elearning Blueprint.

How I designed and built the scenario

Some people avoid creating branching scenarios because they seem too complex. In case it’s helpful, here’s the approach I took. [Read more...]