If you’ve ever recorded a software simulation for soft skills or systems training courses, you know there’s a lot to consider. If you want a polished result, you can’t just launch your screen...
Published 9 years ago
Version 1.0
Blog Post
8 MIN READ
Follow This Process to Create Software Simulations and Systems Training Like a Pro
Awesome article, Nicole. I will be passing this on to coworkers who need to hear these tips. For the majority of my Instructional Design work, I've been building software simulations for programs like SAP and ADP, and these tips are spot-on. I wish someone had handed me a checklist this precise years ago. Thankfully, through hundreds of recordings, and lots of trial-and-error, I've come up with a very similar process.
Articulate Storyline has been my whole world for this type of training, and it is amazing at creating realistic-feeling interactions. I began with Storyline 1 years ago, and now use Storyline 2. However, there is one thing I'll mention to anyone needing to build software simulations: Storyline 2 is NOT good at accomplishing text interactions.
When Articulate upgraded from Storyline 1 to 2, the software almost completely lost the ability to use the Enter Key to submit text interactions. This seemingly simple task worked like a charm for the first several hundred training courses we produced, but as soon as SL2 was released, we lost this ability. That's right, if the simulation calls for the user to type in a text box and press Enter, Storyline 2 wants you to instead require the user to type in the text box and click the Submit button with their mouse. This task will now only work if you publish to LMS. If your job application requires you to publish to Web or CD (as ours did), it's just "tough luck".
I've discussed this several times with Storyline support staff over the last year and a half. They have agreed that the problem exists, and that I'm doing everything correctly; but they passed it on to the black hole that is the Articulate - Quality Assurance team about 16 months ago. Seven software builds later, and no answer is on the horizon. The temporary work-around solution is always "just use the 'submit' button".
I still think SL2 is a great program, and I still recommend it for most types of eLearning. However, I feel that this is something to take into consideration if a designer is deciding to purchase a tool for software simulations.
Articulate Storyline has been my whole world for this type of training, and it is amazing at creating realistic-feeling interactions. I began with Storyline 1 years ago, and now use Storyline 2. However, there is one thing I'll mention to anyone needing to build software simulations: Storyline 2 is NOT good at accomplishing text interactions.
When Articulate upgraded from Storyline 1 to 2, the software almost completely lost the ability to use the Enter Key to submit text interactions. This seemingly simple task worked like a charm for the first several hundred training courses we produced, but as soon as SL2 was released, we lost this ability. That's right, if the simulation calls for the user to type in a text box and press Enter, Storyline 2 wants you to instead require the user to type in the text box and click the Submit button with their mouse. This task will now only work if you publish to LMS. If your job application requires you to publish to Web or CD (as ours did), it's just "tough luck".
I've discussed this several times with Storyline support staff over the last year and a half. They have agreed that the problem exists, and that I'm doing everything correctly; but they passed it on to the black hole that is the Articulate - Quality Assurance team about 16 months ago. Seven software builds later, and no answer is on the horizon. The temporary work-around solution is always "just use the 'submit' button".
I still think SL2 is a great program, and I still recommend it for most types of eLearning. However, I feel that this is something to take into consideration if a designer is deciding to purchase a tool for software simulations.
Daniel: Just curious if the "Enter vs. Submit" issue has been resolved. I don't have access to Storyline on my machine, so I can't test it myself.
I'm considering a series of interactive videos for an upcoming project and trying to decide which tool(s) to use.
I'm considering a series of interactive videos for an upcoming project and trying to decide which tool(s) to use.