What is a branching scenario?
A branching scenario is an interactive learning activity in which each choice a learner makes leads to a different next step, so the story can follow several paths and reach different endings. Branching scenarios are used in e-learning and interactive training video to practice decisions and show their consequences.
Example
A healthcare provider’s training team wants nurses to practice escalating care for a patient who is getting worse. The scenario opens with a patient whose breathing rate has risen since the last check. The nurse can recheck in an hour, call the doctor now, or ask a colleague for a second opinion.
Each choice leads to a different scene. Waiting an hour leads to a patient who is clearly worse, and a second chance to act. Calling the doctor leads to a conversation where the nurse must give a clear handover. At the end, the learner sees how their path compares with the recommended one and why each decision mattered.
How it works
A branching scenario is one format of scenario-based learning. Instead of a single question with feedback, it is a map of scenes connected by choices.
Decision points, branches and endings
- Decision point: a moment where the learner must choose what to do or say.
- Branch: the path that follows one choice.
- Consequence scene: what happens because of that choice, shown to the learner.
- Ending: where a path finishes, usually with feedback on the outcome.
Common structures
- Full tree: every choice opens a new path that never rejoins the others. It is the most realistic structure, but the number of scenes grows very quickly, so it only works for short scenarios.
- Branch and bottleneck: paths split at a decision and come back together at set points in the story. This keeps the number of scenes manageable while still letting choices matter.
- Retry loop: a poor choice shows its consequence and sends the learner back to try again. It is the simplest structure and suits single, high-stakes decisions.
Tracking the path
Because each learner takes a different route, a branching scenario can record more than a score: which choices they made, where they went wrong and which ending they reached. When exported as SCORM, it usually reports completion and a score to the LMS, and some tools also report individual choices.
How to plan a branching scenario
- Start with one decision that matters. Pick a moment on the job where people often go wrong.
- Map it before writing it. Draw the choices, consequences and endings as a flowchart or storyboard, so you can see how big the scenario gets.
- Write realistic options. Each choice should be something a real employee might do, including the common mistake.
- Show, then explain. Let the learner see the consequence first, then give feedback on why it happened.
- Limit the endings. A few clear outcomes, such as best, acceptable and poor, are easier to build, test and maintain than many.
- Test every path. Click through each branch to make sure no path dead-ends or skips its feedback.
Branching scenarios in video
Branching works in text and image-based e-learning, but video makes consequences easier to see. The learner watches a customer get angrier or a colleague react instead of reading about it. In an interactive video, each choice is a button that jumps to a different scene. The cost is production, because every branch needs its own scenes, so video branching scenarios are usually kept short and planned tightly. Tools that generate video from a script make each branch cheaper to produce and to update when the policy behind it changes.
Why it matters for L&D teams
- Safe practice for real decisions. Learners can make mistakes with a patient, a customer or a regulator and see what would happen, without anyone getting hurt.
- Shows reasoning, not just recall. The path a learner takes shows how they apply a rule, which a multiple-choice quiz cannot.
- Feedback with a reason. Seeing the consequence of a choice play out gives the feedback that follows something concrete to refer to.
- Easy to extend. Once the scenario map works, teams can update a scene or add a branch without rebuilding the whole activity.
How Colossyan helps
In Colossyan, you build a branching scenario as an interactive video: each choice is an action button that jumps to a different scene, where the learner sees the consequence of that decision. You can add in-video quizzes, track clicks and quiz results in analytics, and export as SCORM 1.2 or SCORM 2004 to your LMS. Action buttons keep working in translated versions of the video.
See interactive video in Colossyan
