I am pretty new to the E-Learning world and would love some suggestions / resources to help me decide when to use a video vs. software simulation. I am part of a roll out of a companies first Electronic Health Record system. Many of the learners are reluctant to this change and have low computer skills.
Have you considered doing a little bit of both? Maybe a video/narrated screencast to demonstrate and explain the interface (layout, key features, etc.—similar to what Judy mentioned above), then build simulation for the parts that learners will use most and/or those that they are likely to need practice with?
Personally, I would be inclined to create as many simulation pieces as I was comfortable with and scheduling allowed for. Considering your learners' reluctance to the change in tandem with lower computer skills, they may truly appreciate a chance to "work" on the new system with no/low pressure. That chance to interact with the software may even help alleviate some reluctance in some folks...? (...it's possible!)
Videos are a good option for explaining simple "how-tos" and are easy for people to reference later. Software simulations are a strong fit for when people need low-stakes practice to get comfortable with a skill or process. This article on the difference between screencasts and software simulations goes into even more detail on when to use each one.
But one of the great things about instructional design challenges like this is there are usually multiple solutions that work. Chances are either option you're considering would help your audience. Veronica Nalley's suggestion is also worth considering: use both together. Use videos to share how the new system processes work and then let people practice what they just learned in a software simulation.
A few other things to consider:
You said the audience isn't excited about this change. I'd second Judy Nollet's suggestion to open with what's in it for them. That can get them to care more about your content, whichever way you choose to present it.
You mentioned this audience has low computer skills. Chunking your content so it breaks down new processes into smaller tasks could get people comfortable faster. It would also make your resources easier to revisit if they get stuck when using the new system.
Software simulations are excellent for practice. But they do take time to go through, so consider if your audience needs that level of assistance. Depending on the complexity of the system, they might be equally well supported with something like a one-pager on system process steps and be happy the training took less time.
I hope this was helpful and let me know if you have any follow-up questions!
4 Replies
Hi, Corey,
One of the nice things about Storyline is that you insert a screen recording (aka software simulation) in multiple ways in the same project:
You can find out more here:
https://community.articulate.com/series/articulate-storyline-360/articles/articulate-storyline-360-user-guide-how-to-insert-screen-recordings
It'd probably also be useful to present a basic overview of the software, e.g., show a screen and point out the main areas and what they're used for.
You might also want to include an optional scene that covers computer basics and terms.
And be sure to start out with WIIFY ("what's in it for you"). Let them know how they will benefit from using the software.
Good luck!
Corey,
Have you considered doing a little bit of both? Maybe a video/narrated screencast to demonstrate and explain the interface (layout, key features, etc.—similar to what Judy mentioned above), then build simulation for the parts that learners will use most and/or those that they are likely to need practice with?
Personally, I would be inclined to create as many simulation pieces as I was comfortable with and scheduling allowed for. Considering your learners' reluctance to the change in tandem with lower computer skills, they may truly appreciate a chance to "work" on the new system with no/low pressure. That chance to interact with the software may even help alleviate some reluctance in some folks...? (...it's possible!)
Best of luck to you. đŸ™‚
- Veronica
Hi Corey and welcome to the community!
Videos are a good option for explaining simple "how-tos" and are easy for people to reference later. Software simulations are a strong fit for when people need low-stakes practice to get comfortable with a skill or process. This article on the difference between screencasts and software simulations goes into even more detail on when to use each one.
But one of the great things about instructional design challenges like this is there are usually multiple solutions that work. Chances are either option you're considering would help your audience. Veronica Nalley's suggestion is also worth considering: use both together. Use videos to share how the new system processes work and then let people practice what they just learned in a software simulation.
A few other things to consider:
I hope this was helpful and let me know if you have any follow-up questions!
Very good point! In my experience, people working on a new software system tend to love a good quick reference guide or similar job aid. :)