Teaching Decision-Making with Branching Scenarios

Some things can’t be taught by telling. You can explain what good judgement looks like, but learners only really build it by making decisions and living with the results. That’s what a branching scenario does: it drops learners into a situation, asks them to choose, and shows them where that choice leads. Here’s how to make one that teaches.

Start with a decision that matters

A scenario is only as good as its dilemma. The opening situation should present a genuine trade-off with no obviously correct answer — an ethics call, a safeguarding judgement, a customer complaint, an incident response. If the “right” choice is obvious, there’s nothing to learn.

Make every branch plausible

Each option should be something a reasonable learner might actually pick. The goal isn’t to trick people into a single correct path; it’s to let them explore the consequences of different reasonable-sounding choices. Weak, throwaway options waste a branch.

Let consequences do the teaching

Don’t mark a choice “wrong” and move on. Show what happens next — the follow-on situation, the new problem it creates, the door it closes. Consequences that unfold naturally teach far more than a red X ever could.

Play it as a team

Scenarios come alive when a group has to agree on a decision. The argument before the choice — weighing options, surfacing assumptions — is where much of the learning happens. One shared run per group keeps everyone in the same story.

Debrief with the decision map

Afterwards, show each group the path they actually took. Comparing routes across groups — “why did you go left here when they went right?” — turns individual choices into a rich whole-class discussion about judgement itself.

How to write one, step by step

1. Pick the judgement you want to build. Not a topic — a judgement. “When to escalate a safeguarding concern” is a scenario; “safeguarding” is a syllabus.
2. Write the ending you’d like and the two you wouldn’t. Knowing the good outcome and the realistic bad ones tells you what the branches have to lead to.
3. Set the opening scene with a role and some pressure. “You are the duty manager. It’s 4:50 on a Friday.” Learners decide differently when they are someone, somewhere, short of time.
4. Give two or three options at each point — each one something a sensible person might do.
5. Write what happens next, not whether it was right. The consequence carries the feedback.
6. Play it yourself, taking the worst options. If the bad route is dull, learners who take it learn nothing.

How big should the tree be?

Smaller than you expect. Three or four decision points with two or three options each is enough for ten to fifteen minutes of play and a proper debrief. The mistake is letting every choice open a completely new story — the tree doubles at every step and you end up writing dozens of scenes nobody will see. Let branches rejoin: different choices can lead to the same next situation, arriving in better or worse shape.

Keep score of the things that matter

Real decisions rarely fail on a single choice; they wear something down. A running score — budget left, a client’s trust, the level of risk — makes that visible. Each choice nudges the totals, learners watch them move, and the ending can depend on where the totals finish rather than only on the last choice. It teaches the thing that is hardest to say in a lecture: a decision that looks fine on its own can be the third small cut.

Scenario, case study or role play?

They combine well. A case study sets up the background, a branching scenario puts learners inside it, and a role play rehearses the one conversation the scenario turned on.

Where scenarios earn their place

• Health and social care: prioritising, escalation, consent, a worried relative.
• Business and management: a complaint, a budget cut, a team member underperforming.
• Cyber security and IT: an incident unfolding with incomplete information.
• Education and safeguarding: a disclosure, a behaviour incident, a concern about a colleague.
• Law and ethics: conflicts of interest, where every option has a cost.

With ColabYard’s guided scenarios, you describe a situation and AI drafts the full branching tree — which you then edit before it goes live. Groups play one shared run and replay their route on a decision map, a natural lead-in to a group discussion.