How to Write Scenario-Based eLearning That Doesn't Feel Fake

Why Most eLearning Scenarios Fall Flat

You've seen them. "Meet Sarah. Sarah is a new manager. Sarah needs to give feedback to an underperforming employee. What should Sarah do?" Then you get four options, three of which are obviously wrong, and the correct answer is whatever HR would put in a policy handbook.

That's not a scenario. That's a multiple-choice question wearing a trench coat pretending to be a scenario.

Real scenario-based eLearning puts learners in situations where the right answer isn't obvious, where they have to think through consequences, and where they might actually make the same mistake they'd make on the job. Here's how to build those instead.

Start With the Mistake, Not the Content

Cathy Moore's Action Mapping framework flips the typical course design process. Instead of starting with "what content do we need to cover," you start with "what do people actually do wrong on the job?"

Talk to managers and supervisors. Look at incident reports, support tickets, performance reviews. Find the specific moments where employees make bad judgment calls. Those moments are your scenarios.

For example, I was building a data privacy course for a healthcare company. Instead of covering HIPAA regulations section by section, I asked the compliance team: "Where do employees most often slip up when handling patient data?" Their answers were gold: sharing screens during video calls without checking what's open, forwarding emails with patient info to personal accounts for "convenience," and discussing cases in elevators. Each one became a scenario.

Mini-Scenarios vs. Branching: Pick the Right Format

Not every scenario needs to be a choose-your-own-adventure epic. Cathy Moore distinguishes between two types, and knowing when to use each saves you from overbuilding.

Mini-scenarios are single-decision exercises. You present a situation, the learner makes one choice, and they see the consequence. Done. These work when you want focused practice on a specific judgment call. "A patient's family member asks you for test results over the phone. What do you do?" One decision, immediate feedback, move on.

Branching scenarios are multi-decision paths where one choice affects what happens next. Use these only when decisions genuinely cascade, where making a mistake early creates a different situation later. A customer service escalation where a bad opening response makes the customer angrier is a good branching scenario. A forklift safety checklist is not because each check is independent.

The common mistake is building branching scenarios for everything because they feel more impressive. But a well-crafted mini-scenario that nails one tricky decision teaches more than a sprawling branching scenario where learners are just clicking through to see what happens.

Write Characters, Not Cardboard Cutouts

The fastest way to kill a scenario is to populate it with Generic Employee #4 and Angry Customer Template B. Learners check out immediately because nothing feels real.

Give your characters names and one specific detail. Not a full backstory, just one thing that makes them human. "Marcus has been with the company for 12 years and knows the old system inside and out" tells you everything about why he might resist a new process. "Dev is covering for two people who are out sick and has a client call in 15 minutes" explains why she might take a shortcut with data entry.

Here's the trick: write dialogue the way people actually talk. Not "I am concerned about the project timeline and would like to discuss potential mitigation strategies." Instead: "Hey, I don't think we're going to hit Friday's deadline. Can we talk about what to cut?"

Read your dialogue out loud. If it sounds like something you'd hear in a meeting, keep it. If it sounds like a corporate communications email, rewrite it.

Make the Wrong Answers Tempting

This is where most scenario designers fail. They write one correct answer and three obviously wrong ones. "A customer is yelling at you. Do you: A) Listen calmly, B) Yell back, C) Walk away, D) Call the police." Nobody is picking B, C, or D. The scenario teaches nothing.

Good distractors are things people actually do. They're reasonable on the surface but wrong in a specific way. Using the customer example: maybe one option is to immediately offer a refund (seems helpful but skips diagnosis), another is to apologize and promise to fix it (sounds right but makes commitments you can't keep), and the best option is to ask questions first before solving anything.

Each wrong answer should have a plausible real-world consequence. "You offered the refund immediately. The customer is happy, but your manager asks why you gave away $200 without investigating whether the product was actually defective. Now you need to have that conversation." That's feedback that sticks.

The Feedback Is the Learning

In a well-built scenario, the feedback after each choice does more teaching than any content slide ever could. Don't just say "Correct!" or "Incorrect, try again." Show what happens next.

For wrong answers, show the realistic consequence. Not a punishment, but what would actually happen if someone made that choice at work. Then briefly explain why the better option works. For correct answers, show the positive outcome and reinforce the principle behind it.

Moore calls this "intrinsic feedback" vs. "extrinsic feedback." Extrinsic feedback is a popup that says "Wrong! The correct answer is B." Intrinsic feedback is the scenario continuing in a way that shows you the natural result of your decision. A customer getting angrier. A project falling behind. A compliance violation being flagged. That's what makes learners internalize the lesson.

Try This Today

The Payoff

Scenario-based eLearning takes more upfront effort than a slide deck with bullet points. But it's one of the few approaches that actually changes behavior on the job, not just passes a quiz. When your learner is standing in front of a real angry customer or staring at a real data entry shortcut, you want them to think "wait, I've seen this before" instead of "what was on slide 14 again?"