The scenario stack

What this lesson covers

1. 01

   Name the failure first

   A pattern chosen because the template is free in the library is decoration. Write the failure first, in one observable sentence: an unauthorised override, a skipped isolation step, a missed escalation. Then pick the single interaction that makes that failure visible. If you cannot name the failure, you are not ready to choose a slide type.

2. 02

   Failure type to pattern

   If the failure is. | Primary pattern

   A wrong judgment in a conversation | Branching dialogue

   A step skipped or out of order | Mission or ordered simulation

   Missing a cue in a document or scene | Spot-the-error or mini-scenario set

   Not knowing a detail that changes | Searchable job aid, no practice screen

   Several decisions over time with consequences | Longer branching scenario or simulation

3. 03

   One pattern per screen

   Stacking a branch, a game mechanic and a quiz on one screen splits attention and hides which decision you are measuring. Each screen should rehearse one decision with one pattern. If the action needs more, use more screens.

4. 04

   Mini-scenarios often beat long branches

   Long branching stories are expensive to write, review and translate, and each path is seen by few learners. Cathy Moore and others recommend mini-scenarios: one realistic situation, one decision, rich feedback, then the next situation. A set of eight mini-scenarios gives more varied practice than one long branch, and it is easier to keep accurate when policy changes. Save long branching for decisions whose consequences really unfold over time, such as a negotiation or an investigation.

5. 05

   Choose the pattern

   For each action on your map, write the failure in one sentence and the primary pattern from slide 2. If two actions share a pattern, consider whether one practice set can cover both.