Tools used:

Articulate Storyline, Google Docs, mindmeister, Snagit, typecast

Design Process: 

In full transparency, I set out to create a software simulation because I hadn’t seen a lot of them in the portfolios I’ve reviewed, and I also wanted to demonstrate some Storyline skills in the process.

I started by jotting down some thoughts in a notebook, which I won’t post here because of my egregious handwriting. I then moved to mindmeister to build a flow chart (ish).

I knew I wanted to have a guided learning module and an independent learning module for those who already knew what to do. Nothing is more annoying than having to take a course when you already know the answer, so I figured I’d give people an option to test out. This had absolutely zero hints, so if users were unable to find success, they’d have to return to the menu and complete the guided practice.

When working in mindmeister, I began to get ideas about what the narration needed to be and what type of animation I would need to do in order to complete it. You can see some of these half ideas within the mindmeister document.

From there, I built my storyboard. The storyboard and final project don’t totally line up (because I choose to add some more things as the project developed). However, the vast majority of the project comes from what I created on the storyboard.

After completing the storyboard, I assembled a list of all required screenshots and was able to capture them and resize them with Snagit.

I did not create a visual mockup as I did not have a SME to consult with or get approval from. I also felt comfortable diving into the final project because it wasn’t incredibly overwhelming in terms of the number of scenes or slides.

Development Process:

I built the final project in Articulate Storyline 360 while getting audio from typecast. I started by building out the “Test Out” portion so that I could copy, paste, and modify the course for the “Guided Learning” part.‍

Features:

Interactive menu, Guided Learning with audio, Test out section without audio

Reflection: 

I learned a lot about the importance of planning ahead of time and making sure all of my ducks were in their proverbial row. I could have saved a bit of time if I did this, and I am looking to develop or find a framework to make sure I set myself up for success in the future. I enjoyed problem-solving a couple parts where my variables weren’t doing what I was expecting them to do. This was both helpful and humbling. Finally, I know I need to develop my visual design skills. I think that this is a big next step for me, and it’s definitely something I will continue to work on.