Blog Post

Articles
8 MIN READ

Follow This Process to Create Software Simulations and Systems Training Like a Pro

CommunityTeam's avatar
9 years ago

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 recording tool of choice and capture the sequence. A professional product requires you to be deliberate.

So what’s involved? Quite a few things! You need to select the best app, do a task analysis, review product documentation, record your simulation, edit the video, and more. The easiest way to show you is with an example scenario.

You work as a training designer for a medium-size company called Widgets Inc. One of the directors, Fatima, needs you to deliver systems training on the company’s customer database, WidgetData, for the customer service representatives. 

Let’s assume you’ve already selected Storyline 360, so we don’t have to worry about the app-selection process. So let’s focus on the additional steps, as follows:

  1. Identify Tasks
  2. Perform Task Analysis
  3. Document the Processes
  4. Prepare Your Demo Data
  5. Prepare Your Recording Area
  6. Record Your Simulation
  7. Edit Your Recording

Step 1: Identify Tasks

You’ll first need to identify the tasks to cover. Since most software systems are multifunctional, you need to narrow down the specific processes to simulate in your course.

Start by interviewing the stakeholders, those people responsible for the processes, and the target audience (if it’s different than either of those two groups) to find out what they consider vital tasks to be covered in training. Once you’ve identified those processes, check to see if the software vendor or your internal teams (think the system owner, IT, etc.) have video or written tutorials you can reference or repurpose. 

Back to our example! Ask Fatima about the tasks she wants to cover in the systems training. Her response is that she wants learners to know how to do the following in WidgetData:

  • Add a new customer
  • Search the database
  • Edit a customer profile
  • Delete a customer

You also find out that the system was built in-house, so there’s almost no existing documentation and there are definitely no video tutorials. With that in mind, you next need to identify the step-by-step sequences for each of those tasks in WidgetData. It’s time to do a task analysis!

Step 2: Perform Task Analysis

In some cases, you might already know the step-by-step sequence for the processes you need to cover in the training. When that’s not the case, work closely with a subject matter expert (SME) who does.

A few tips to remember when walking through processes with SMEs:

  • Respect their time. Prepare a list of processes you’d like the SME to demo for you. If you can, send the list ahead of time.
  • Record the meeting. Use the recorder built into your e-learning authoring app. Better yet, meet virtually and record the session. A virtual meeting has the benefit of capturing not only the step-by-step process but any additional information you discover while chatting with the SME. The recording is what you’ll rewatch later to analyze each step.
  • Ask questions. Put yourself in the mindset of someone who’s never encountered the tool before. There are no stupid questions. As the training designer, you need to uncover as much information as you can to understand the “why” behind a process so you can pass that key information along to the learners. Build some scenarios around what’s being demoed to represent the real-life situations learners will encounter. When training has relevance for learners, they’re more engaged in finishing it.

At Widgets Inc. Fatima puts you in touch with Derrick, one of the company’s top customer service reps, to act as your WidgetData expert. You invite Derrick to walk you through each of the processes in the system while you record the screen. As he talks you through every click and keystroke, you ask questions like:

  • What happens if you forget to input this information?
  • What are the most important things to remember related to this process?
  • What would be the worst-case scenario if someone did this step or process incorrectly?

Asking these types of questions will help you gather critical contextual information about the processes.

Step 3: Document the Processes

Once you’ve identified the step-by-step sequence for each of the processes you’ll cover in the training, create a document that clearly lists each process. For our example, we’ll use a table format, but you can use whatever you’re comfortable with. It’s also helpful to add information you uncovered during your task analysis so that you can reference it during your demo recording. 

At Widgets Inc., you’re using the recorded video version of your meeting with Derrick to document each step of the processes you’ll need to cover in your WidgetData systems training. Here’s what you documented for the first task: 

Name of Task

Trigger for Task

Steps

Additional Info

Add a new customer.

A customer calls who doesn’t have a profile.

  1. Navigate to WidgetData home page.
  2. Click the Customers tab
  3. Select Create New Customer from the drop-down menu.
  4. Enter customer information in required fields.
  5. Click the Create button.

Enter information in all of the required fields or you’ll get an error message when you click Create.


After you’ve created a new customer, a pop-up confirmation message displays letting you know the account is created.


Step 4: Prepare Your Demo Data

You’re almost ready to start recording your systems training—but before you do, make sure you have all the data and information to complete your recording. Here are a few things you might need before you start recording:

  • Get access to a “sandbox” environment. A test version (“sandbox”) of the computer system software will enable you to complete your processes without impacting real data in the system.
  • Create an account or profile in the sandbox. You’ll want an account that gives you system access similar to that of your learners.
  • Add some sample data. You’ll need some dummy data that you can quickly input into the system for processes as needed.

In our Widgets Inc. example, Courtney in IT has given you access to a sandbox version of the WidgetData system as well as a fake account with the same admin rights as a Widgets Inc.’s customer service rep. Your interface looks exactly like the customer service rep’s, with the same available options. In this sandbox Courtney says you can create, edit, and remove customers without impacting any real data.

Step 5: Prepare Your Recording Area

Before you record, you’ll need to prepare your virtual environment. If you’re using a fresh sandbox, don’t add additional icons or customizations unless you need to better mirror your learner’s environment. If you’re using your own system, remove extra icons, bookmarks, and personal data and images. It should be free of distractions. Along those lines, make sure before you start recording that all external system notifications are disabled (unless you need to record them for the demo).

Additionally, you should:

  • Launch the applications and systems you’ll use in your recording before you start so that they’re ready to go when you need them.
  • Have all the data you need close at hand on the system where you’re recording.
  • Have your step-by-step document available as a hard copy or on a separate system from the one you’re recording. 

Next, access the sandbox that Courtney provided and make sure all extraneous applications are closed. Turn system notifications off to prevent pop-ups from interrupting your recording and launch WidgetData so you don’t waste any time waiting for the application to launch. Finally, check that your process document is close at hand so you can follow it step by step as you record.

Step 6: Record Your Simulation

With your prep work done, you’re ready to record your simulation! The steps will vary depending on the recording app you’re using, but you’ll start by selecting the size of the recording area. Then you’ll hit the Record button and click through the process step by step. 

Pro tip: Do a test recording to make sure the video quality is acceptable (just a few seconds; it doesn’t have to be the whole process). You don’t want to have to re-record a lengthy process due to a technical issue with your setup.

Depending on your project, the type of simulation you record will vary. It might be interactive, where the learner clicks through the simulation themselves. Or it might simply be a demo with captions along the way that describe what’s happening. It could even be a graded quiz game, where learners click through the process themselves and lose or gain points depending on where they click. Suffice to say, you have tons of options, depending on your project, your audience, and what you hope to achieve.

For Widgets Inc. you’re using Storyline 360 to record your processes in WidgetData. Once you’re finished, you can reuse that recording in any format you want, either as a single movie or as step-by-step slides.

Step 7: Edit Your Recording

No matter which recording app you use, you always have to do some amount of post-recording editing. As soon as you've finished recording a task or process, preview it from start to finish and see how it looks. Make sure you capture everything and that it flows logically.

Then, one slide at a time, make the necessary adjustments to the caption text, hot spots, mouse clicks, data entry fields, and other objects. If you’re using captions, here are a few tips:

  • Use consistent terminology and language across all captions.
  • If you use an abbreviation or acronym, even if it’s common knowledge to your audience, consider including the full term the first time it’s used. 
  • Be direct and concise; don’t use words you don’t need.
  • Start instructions with a verb, except for captions providing general knowledge or information, like defining a term.
  • Don’t hide important information with on-screen captions.
  • Don’t include wordy paragraphs in your captions. Omit anything unnecessary and break up longer chunks of text over several captions or slides. 

In addition to instructional and informative captions, you might need an introduction and summary caption for each task. If you have tips or additional information you noted during the documentation process, consider including them throughout the simulations as appropriate to provide added value for your learners.

For example, the introduction slide for each WidgetData task explains the context and trigger for completing that process in the system. The summary slide describes what happens at the end of the process and provides follow-up information. 

Wrapping Up

That’s how you create software simulations like a pro, from the initial request to the post-recording edits. Remember, planning is key. As you can see, if you want the best possible simulation, there are a lot of steps before you actually hit “Record.”

For more information about task analysis, check out our recently refreshed How to Do Task Analysis Like a Pro. For ideas on working with SMEs, check out this series on Everything You Need to Know About Working with SMEs as well as these awesome downloads from Sarah Hodge. If you’re looking to do even more with Rise 360, be sure to peruse this fantastic guide on creating software tutorials.

Follow us on Twitter and come back to E-Learning Heroes regularly for more helpful advice on everything related to e-learning. If you have any questions, please share them in the comments.

Published 9 years ago
Version 1.0
  • This article was extremely helpful! I also loved the tip about pacing and using next buttons. I love creating learning that works for every learner! Great job!
    • NicoleLegault1's avatar
      NicoleLegault1
      Community Member
      Happy to hear this is helpful for you Kristie! Thanks for leaving a comment :)
  • 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.
    • KeithShull's avatar
      KeithShull
      Community Member
      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.
  • JuliePatno's avatar
    JuliePatno
    Community Member
    Tess and Dianne- Thank you for your insight and tips! Similar to Tess, that's how I've done it in the past- recorded the screen while talking through the steps to myself, then recorded the audio in Audacity while watching the video back. For timing purposes, I was hoping there was a way to record audio at the same time as watching the screen recording back in Storyline. From Dianne's feedback, it sounds like it's not doable in Storyline. I was just hopeful that there was a workaround that I wasn't aware of. Thanks for your help!
    • JeremyStiffler-'s avatar
      JeremyStiffler-
      Community Member
      I do the exact same thing. It seems to be the best way to get the highest quality results in the shortest time with the resources available.

      I have found that recording into a development tool like Captivate or Articulate reduces the audio quality so much so that it's distracting to learners.
  • KarenCarver's avatar
    KarenCarver
    Community Member
    I use Articulate Replay for my screencasts. Does anyone use it?
  • CateSheehan's avatar
    CateSheehan
    Community Member
    If doing this training as part of a system upgrade/change, reaching out to the IT folks managing UAT scripts is a great resource. I have been able to create simulation tasks from UAT scripts that already mapped out all the critical tasks end users needed to do as well as process flows. You still need your SMEs and other input from all stakeholders, but don't overlook the other departments in your org who may have a lot of info that can save you time!
  • BrianSilver's avatar
    BrianSilver
    Community Member
    The "What’s the best way to teach employees new software?" link goes to an internal doc instead of the conversation. Please fix
  • JuliePatno's avatar
    JuliePatno
    Community Member
    Thank you for the tips! I have a question about adding narration- What is the best way to add audio to the screen recording? I would like to record the screen muted first (so I don't capture the sound of the mouse clicks or any other outside sounds) then add the narration after. Is it possible to record the audio as I play back/view the screen recording? Any tips or best practices would be appreciated!
    • TessRichardson1's avatar
      TessRichardson1
      Community Member
      Hi Julie, When I'm faced with that situation, I will record only the screen while reading the narration script to myself, so that the pacing of the screen demonstration is going to be as close as possible to the audio. Then I record narration using Audacity while watching the video playback, and sync both visuals and audio on the SL timeline. This is not always a seamless process, and I'd love to hear from anyone who has a better method!
      • DianneHope's avatar
        DianneHope
        Community Member
        This is something I've been working on lately Tess - there are a couple of ways I've done this. I pretty much never record the narration while I'm recording the screen - although as a technology trainer I should be able to do this, but I find it a very different situation when you know you're recording something as opposed to showing learners in a face-to-face training session.

        So, I firstly go through the process a few times before I start recording. Then I do the screen recording using SnagIt (which I use a lot and find an absolutely brilliant program). Then I bring this .mp4 file into Camtasia where I edit it (sometimes quite heavily). I then record the audio while I'm watching the edited file - this is really easy to do in Camtasia. This way it's easy to synch the audio with what's on the screen - or work with both a little to get this right after I've finished the recording the audio. Then I publish the Camtasia file into a new .mp4 and import this into Storyline.

        I wish I could do all of this in Storyline, but the draw-back with doing this whole process in Storyline is that even though you can record audio directly from a slide in Storyline, you can't watch the video as you're recording the audio.

        I really like your concept of using some static images amongst your video footage - I'm going to try this myself. I have also done some screen recordings with narration where I have added pop-up messages, such as relevant keyboard shortcuts or additional tips on things that I may not have narrated in the audio. Too many of these can be quite off-putting, but sometimes these can be very useful and add to the visual engagement. I have done this in both Camtasia while I'm editing the video and audio, and also in Storyline by adding these to the timeline at the relevant points along the video.

        As far as being a seamless process, I'm not sure that one way is any better than another - I find that the more I stick to one method, the more familiar I become with the process and then it becomes more seamless.
  • asifraja's avatar
    asifraja
    Community Member
    Yup replay for screencast but I prefer not to use any video clips at all and use static shots instead,
  • This was fantastic, Nicole! It really is all about planning. Thank you for the detailed and well organized steps!