Whether you’re new to building software simulations or desire a checklist to make yours better, these tips may help you avoid rework, whichever authoring tools you’re using.
1. Use a scenario. Even a simple training scenario with a learner focus will increase engagement. If you are able to include a story around your scenario, all the better. For example, establish a problem the learner will resolve by completing the scenario, for example “Try out this as you enter the profile info for Mr. Smith.”
To change this into a simple story, add a few details, for example”John Smith is a brand-new employee of X organization. Help Mary finishes his worker profile and avoid any errors or duplicates. Or, farther increase engagement by expanding this story to make the learner empathize with Mary. By Way of Example, introduce additional particulars an overbearing boss, such as Mary’s stress, a Crucial co-worker, etc:
“Although Mary is a competent worker, she becomes nervous when she has to find out a new system. Today is her first day inputting worker profile information with MemberPlus. Help Mary gain confidence working with the new system as she passes John Smith’s information.”
2. Practice the job (s). Since your objective is to help students become proficient with the program, run via the software task process(es) several times as you plan the simulation. The more familiar you’re with the process(es), the better your simulator will be. This can help you pinpoint the details that you need to emphasize, in addition to those that are not as significant. And, even though your SME should help you identify pain issues, you might be able to find additional issues a newcomer might encounter.
3. Plan your simulation info. In most cases you’ll want to disguise actual info, although the data in your simulator should be realistic. An employee might not need their name promoted in your training, and a client might not want their data broadcast that is real. Before you record the real screens, planning the info will save you time.
You can also plan to emphasize the advantages of the software or pain points the learner as you plan the information. For example, if the process includes choosing from a list of codes, then you could include choices for codes and supply appropriate responses for each choice. If you use a story around your scenario, you might even incorporate effects, for example Mary’s boss’ reaction to an error.
4. Plan for resources. Job aids or resources the learner may need at work. If possible, include context-sensitive links to those sources. This is likely to make your simulation more closely resemble the work process.
5. Record a draft. If you record a video or a draft simulation before finishing all your simulation screens, it can be used by you as a manual. You will be able to make sure that you don’t miss any steps, and you’ll identify steps you may consolidate.
6. Promote interaction. Emphasize them once you do identify those essential training points. Allow the learner to undergo the process.
7. Getting stuck in a simulation is frustrating for a learner. Use hints, feedback, and “try again” choices in your simulations for incorrect answers to produce the navigation idiot-proof.
8. No one should need to squint to view software screens in a simulation. Guarantee that the simulation screens are equally large enough and clear enough. If there are a lot give a summary of the shot of the screen then focus on regions of the display. By revealing the screen filled 29, you can achieve it by creating a succession of slides that reveal only part of the display and then end the arrangement. Including a zoom into the display with information that is completed will offer an opportunity for the students to review.
9. Avoid info that is extraneous. Help the learner focus. Use blur tools to block info that is unnecessary on each simulation display or contours.
10. It’s a given that you’ll receive your SME to review the content, however reviewers of a simulation can help you find issues you might not know about. You try to break it and also need to examine your several times. Before the simulation is deployed, it’s definitely better to fix a problem.