‍Tools used:

Articulate Storyline 360, Google Docs, Mindmeister, Vecteezy.com

‍Design Process: 

I am the content expert in this matter, so I didn’t need to interview anyone or get that information from anywhere. I have used a rondo before in training (I love coaching soccer), and I knew the basic requirements to setting one up. With most things, the sweet stuff is in the details, but this would be a good introduction to the rondo as a concept for someone who has never heard of it before.

I created my eLearning storyboard while simultaneously drawing out what I imagined the final map of the course would look like. I knew the first three questions were essential to know in order to understand the very basics of a rondo, so the user has no option but to keep practicing until they get them correct. From there, you can lose points on the slider for incorrect answers, including the drag and drops.

There’s a point where there are two correct answers for a question, and your answer choice (you can only choose one on purpose) determines where you go in the scenario. I wanted to challenge myself to make this because I had never done something like that. A wrong answer disqualifies you from getting maximum points on the scenario, but you’re still able to pass.

After creating the storyboard, I had to recheck the math on my slider (multiple times) and then figure out what images I needed for this to be a successful learning scenario.

I had the character images and backgrounds created on Fiverr, as I do not currently possess the ability to make those on my own. From there, I created several iterations of what question slides, the Pep slides, the buttons, the transitions, and the drag and drops would look like on Storyline. I consulted with multiple people about what looked best and other visual feedback, and I settled on the final designs after that.

Development Process:

I built out the final product on Storyline. I split the scenario into four scenes: a welcome scene, question scene, and each drag and drop got its own scene, with the review portion being added on to the passing drag and drop scene.

I wanted to make each Pep slide and fail slide a layer on a question slide, but the transition was rough because the background changed. So I decided to add fades and make everything its own slide. This meant I needed to create variables so that points wouldn’t be added to the slider every time you went to the Pep slide or the Fail slide.

I built the question slide (including the slider) on the slide master to save myself some time. From there my primary focus was making sure the design was consistent within the question slides. Copying & pasting slides definitely helped with this aspect of the development. 

The drag and drop for the back foot concept is actually one of the best ways to teach back foot. It can be a confusing concept when teaching it to children, but the visual representation makes it super clear about how you’re expected to receive a pass or play a pass.

‍Features:

Mentor Character, Drag & Drops, Multiple Pathways, Review slide, Slider

Reflection: 

I (once again) learned a lot about the importance of planning ahead of time and making sure all of my ducks were in their proverbial row. My biggest struggles were with the transitions from one slide background to another and how to solve that visually. I was able to iterate on what I wanted the slides to look like, but I overlooked what I wanted the slides to do. This was definitely a good lesson to learn as I had to go back and (time-consumingly) fix transitions and variables within multiple parts of the question portion of the scenario.