Branching scenarios in onboarding training: when they're worth it (and when they're not)

Branching scenarios are the part of e-learning everyone asks for and few teams scope well. Done right, they're the closest a new hire gets to practicing a real decision before they face it on the job. Done wrong, they're an expensive quiz with illustrations, or a maze nobody can update.

This post is about the call you have to make before anyone storyboards anything: does this onboarding module need a branching scenario at all, and if it does, how big should it be?

What a branching scenario is (and isn't)

In a branching scenario, the learner is placed in a realistic situation and makes a choice. The story then changes based on that choice: a colleague reacts, a problem gets worse or better, and the learner faces the next decision from where their last one left them. Feedback comes from consequences first, explanations second.

That's different from a multiple-choice question with a picture on top. If every option leads back to the same next screen with "Correct!" or "Not quite", it isn't branching. That's fine, but it should be priced and designed as a knowledge check.

When a scenario is worth it

In my experience, a branching scenario earns its cost in onboarding when most of these are true:

The hard part is judgment, not knowledge

New hires usually know the rule. What they struggle with is applying it when a friendly senior colleague suggests skipping it, when a customer is upset, or when two priorities collide on a Thursday afternoon. If the mistake you're trying to prevent happens despite people knowing the policy, practice beats explanation.

Wrong choices are tempting

A scenario only teaches if the wrong options are the ones real people actually pick, for reasons that make sense in the moment. "Ignore the safety alarm" isn't a tempting option. "Use your buddy's login just this once so the shipment goes out on time" is. If you can't write three plausible options for a decision, it probably isn't a good decision point.

Mistakes are costly or awkward to make for real

Data access, safety, customer escalations, expense rules and anything involving a manager conversation are good candidates. Letting someone make the mistake in a module costs far less than letting them make it in their first month.

You can describe what "good" looks like

The subject-matter expert has to be able to say what an experienced person would do, and why. If the honest answer is "it depends on the manager", the scenario will just teach one manager's preference. Fix the process first.

When it isn't

Skip the scenario, or keep it very small, when:

• The content is procedural. How to submit a timesheet or book a meeting room is better taught with a short walkthrough and a job aid people can find again on day twelve.
• There's one right answer and no temptation. A short quiz checks understanding faster and is easier to maintain.
• The process is about to change. Scenarios are full of specific details: names of systems, steps, who to call. If those change next quarter, a scenario is the most expensive part of the module to update.
• Nobody owns the "why". Without an expert who can explain the consequences of each option, the feedback will be generic, and generic feedback is where scenarios lose learners.

How to scope one that stays buildable

The most common scoping mistake is promising a sprawling tree. A scenario where every decision branches into three new paths has 27 endings after only three decisions. Nobody can write, review or maintain that well, and most learners only see one path.

A few patterns keep scenarios small and still meaningful:

Use a few decisions, and let paths rejoin

Three well-chosen decisions are usually enough for an onboarding scenario. After each choice, show the consequence and then bring the paths back to a shared next moment, carrying forward what matters (for example, a colleague who is now more or less trusting). The learner still feels the effect of their choices without the tree exploding.

Make the consequence the feedback

Instead of "Incorrect. Policy 4.2 says...", show what happens: the shift lead asks why the access log shows two logins at once, or the customer escalates. Then offer the explanation. People remember the consequence long after they've forgotten the rule number.

Keep the cast and setting consistent with the rest of the module

If the video introduces a new hire, their manager and their onboarding buddy, use the same people in the scenario. Learners already know them, so less screen time goes to setting up who's who, and the scenario feels like part of the same story rather than a test bolted on at the end.

Write down what you'll track

Decide early whether you only need "completed" and a score, or the specific choices people made. Choice-level data can tell you which temptation catches the most new hires, which is useful for managers, but it may require xAPI rather than plain SCORM. See SCORM vs. xAPI for onboarding for how to decide.

An example

The sample module on our site, built for a fictional logistics company, ends with a short scenario called "Your first Thursday". The learner is Sam, a new operations coordinator on day four. Her onboarding buddy offers to let her use his login to save time, and 3 decisions follow. The option the module rewards is to open a ticket and tell her lead, and each choice gets a visible reaction from the rest of the cast.

It's deliberately small: a single situation, 3 decisions and 8–10 minutes. It's there to check that people can apply one important rule under mild social pressure, not to simulate an entire week. You can open the scenario on the home page and play through it.

A quick decision checklist

Before you ask for a branching scenario, check that you can answer yes to most of these:

1. Is the mistake you want to prevent a judgment call rather than a gap in knowledge?
2. Can you write three options that real new hires would plausibly choose?
3. Is making the mistake for real costly, risky or awkward?
4. Can an expert explain the consequence of each option?
5. Will the process stay stable for at least the next year?
6. Do you know what you'll do with the results?

Mostly yes: a focused scenario with a few decisions is likely worth it. Mostly no: put the budget into a clearer guide, a better job aid, or a manager conversation in week one.

---

If you're weighing whether a scenario belongs in your onboarding module, book a 30-minute call. Bring the decision your new hires get wrong most often, and we'll sketch whether it holds up as a scenario.