3 cool ideas to steal for your training scenarios

Here are some sample scenarios showing different ways to provide background information, plus a unique way to show the consequence of a decision. Learn more.

Branching or mini scenario: which do you need?

What type of scenario do you need? Will a one-scene mini-scenario be enough, or do you need a branching scenario? Learn more.

3 ways to help people learn from mistakes in branching scenarios

I’m in your branching scenario, and I’ve made a bad choice. Can I go back and change my decision, or do I have to continue, looking for ways to recover from my mistake? It depends! Learn more.

Scenario design: The process

Want to write a scenario? Don’t just jump in. You’ll save time and create a stronger story if you follow this process. Learn more.

How to design software training, part 2: Practice activities

Here’s an alternative to traditional software training: Create self-contained activities that help people learn by doing, and make the activities available on demand. Learn more.

What’s the real cost of eye candy?

“We need eye candy!” But at what cost? If we spend too much time on images, we don’t have time to create challenging activities. Will people really reject a text-only activity? Learn more.

7 ways to make dialog sound natural

Do your scenario characters sound like robots? Try these 7 powerful tips to write natural dialog and give your characters some character. Learn more.

Scenario example: Chainsaw training!

Your new client wants you to design training for chainsaw users. But what does he really need? And could I possibly be serious about this scenario? Learn more.

Scenario mistakes to avoid #2: “Eat! Eat! You need to eat!”

Do we really need to force-feed people information before they can try a scenario? Learn more.

Scenario mistakes to avoid #1: Eager-beaver feedback

When is feedback helpful in a scenario, and when is it annoying? Should we immediately tell people what they’ve done wrong and what they should do to fix it? Learn more.