Forum Discussion
Decision Trees: Exploring the Road Not Taken
We ask learners to make decisions all the time. But how often do we give them the opportunity to see what would have happened if they'd made a different choice?
That's one of the things I like most about decision trees.
Instead of presenting a question, collecting an answer, and moving on, a decision tree allows learners to explore how one choice influences the next. They can follow a path to its conclusion, return to an earlier decision, and discover how a different choice changes the outcome.
Sometimes the most valuable learning happens when they explore the path they didn't take.
When would I use a decision tree?
Decision trees work particularly well when decisions have consequences that aren't immediately obvious.
A few examples:
- Troubleshooting: Explore how different diagnostic decisions lead to different solutions.
- Customer service: Follow the consequences of different responses to a customer situation.
- Leadership development: Examine how communication and management decisions influence team outcomes.
- Compliance and policy: Apply policies to realistic situations where context influences the appropriate response.
- Process training: Understand how an early decision affects subsequent steps, responsibilities, or outcomes.
Why does this work for learning?
What I particularly like about decision trees is that they encourage learners to examine the relationships between decisions and consequences.
They're practicing more than recall.
They're applying information, analyzing cause-and-effect relationships, comparing alternatives, and evaluating outcomes. These are the kinds of thinking we want learners to develop, particularly when the goal is sound judgment rather than memorizing information.
There's also value in being able to backtrack. When learners revisit an earlier decision and explore another branch, they can compare outcomes and reconsider their original reasoning.
And unlike real life, a poor decision doesn't require an incident report.
About this interaction
The example in the GIF explores decisions surrounding a compliance training problem. Learners follow different paths, examine the consequences, and return to explore alternatives.
I built the interaction as standalone HTML, so it can be embedded into Articulate Rise 360 using an Embed block or incorporated into Storyline 360 as a web object.
The content and visual design can be customized for different learning scenarios.
I'm curious how others are using branching activities. Do you typically guide learners toward one correct outcome, or give them the freedom to explore multiple paths and compare what happens?
1 Reply
Hi there agenovese . I like what you've done here
I've done this quite a lot now for branching activities, and I tend to offer complete freedom, but offer context and considerations along the way. If it's a branch and activity after they've had the information/knowledge, then it is a little bit more gated and measured to let them know that they've maybe not made the best choice, because sometimes there isn't always a correct or incorrect answer in these branching scenarios.
If it's before an event to assess their current understanding or to benchmark, then I'm a little bit more guiding, a little bit more support and context, with the ability to use the "flux capacitor" and circle back to something they now know a little bit more about.
Made a few of these and also made them situational, so adding different roles, responsibilities, and scenarios as a trigger point at the start, so they can decide, "okay, I'm in this role, I do this thing", and then the branch and scenario pulls that out.
I will say HTML and CSS is far easier to do that, usually with generative AI, to scope out those scenarios once you've got the base level, and to make sure the links happen, you don't get an e-learning dead end that sometimes happens with these branching scenarios.
I've started to incorporate multimedia options too, with voiceover and images where relevant, but it tends to really "bloat" the files for uploading - not so much an issue in Rise360 anymore due to the connected packages, but an issue for asset control and other LMS'
