Decision Trees: Exploring the Road Not Taken

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'