Scenario-based learning: design realistic decisions

Scenarios are strongest when learners must make judgements in context: handling customers, applying policy, managing risk, leading people, diagnosing problems or choosing between competing priorities.

If the outcome is simply remembering a fixed fact, a scenario may add unnecessary reading. Use context when context changes the decision.

Identify a decision people genuinely make and the mistakes that matter. Then build only enough situation around it for the learner to reason.

A useful design sentence is: “When ___ happens, the learner must decide ___ while considering ___.” This keeps the scenario anchored to performance.

Ask experienced staff for difficult cases, common shortcuts, ambiguous situations and examples where two rules appear to compete. Ask what a novice notices first and what an expert notices instead.

Remove identifying details and unnecessary drama. Realism comes from credible constraints and choices, not elaborate fictional biographies.

Every option should sound like something a real person might do. Use genuine misconceptions and shortcuts as distractors. Avoid one polished policy answer surrounded by obviously reckless choices.

Keep options comparable in tone and detail so learners cannot guess from writing style.

Feedback can reveal what happens next, explain the principle, or both. Where appropriate, let learners see the operational consequence of a decision before explaining it.

Do not punish experimentation in practice scenarios. The point is to make thinking visible and correct misconceptions before the final assessment.

Complex branching can become expensive to write, test and maintain. Often a short decision → consequence → debrief pattern teaches the same principle more clearly.

Use persistent branches when earlier decisions genuinely change later conditions. Map branches before authoring and define where paths rejoin.

A customer is frustrated because a promised service has not happened. The learner chooses an opening response. One option becomes defensive, one makes a promise outside the employee's authority, one acknowledges the concern and clarifies what can be checked, and one immediately transfers the customer without explanation.

Feedback explains both emotional impact and operational risk. A second decision then asks what information should be gathered before escalation. The scenario tests a sequence of realistic judgements rather than asking learners to recall a list of service principles.

• Is the decision tied to a learning outcome?
• Does the context contain only information needed for reasoning?
• Are wrong options genuinely plausible?
• Is there a defensible best response?
• Does feedback explain why?
• Can the interaction be completed with keyboard and assistive technology?
• Can future policy changes be updated without rewriting an enormous branch tree?

For planning the scenario inside a course, see the storyboarding guide.