Software simulation: show me, try me, test me

Teaching software by handing over the mouse

Training people on an application has a failure mode everyone recognises. Someone records their screen, narrates it for forty minutes, and the recording is never opened again. It is cheap to make and it does not work, because watching a cursor move is not the same skill as moving it.

A software simulation closes that gap by making the learner do the thing. This one covers an association management portal, a product with the kind of surface area that makes it a fair test: fourteen separate modules, from dues and accounting to board voting and a resident portal.

The three passes, and why the order matters

The pattern is old and it holds up. Show me demonstrates the task. Try me repeats it with the learner driving and a hint available. Test me repeats it again with the hints gone and the result recorded.

Each pass does something the others cannot. Demonstration alone produces recognition, which feels like learning and is not. Practice alone, with no demonstration first, produces guessing. Testing without either is just an exam. Run in order, the same task is seen, done, then proved, and the third pass is the only one that produces evidence worth putting in a record.

What makes the hands-on moments work

• The prompt names the control, so the learner is never hunting blindly
• Nothing advances until the right thing is clicked, so the step cannot be skimmed
• The spotlight dims everything else, which removes the hardest part of a busy screen
• Controls to pause, step back or skip, because an adult being taught software wants to set the pace
• Any single module can be opened on its own, so it doubles as reference after the first run

That last point is the one that gets underused. A simulation built in chapters stops being a course and becomes documentation people actually open, because finding the answer takes one link rather than scrubbing a video.

Built as a simulation, not a recording

This is a rebuilt interface rather than a screen recording, which is what allows the learner to click it. It also means no re-record when a button moves: the changed screen is edited and the surrounding steps stay. For a product on a release cycle that difference compounds quickly.

How it would be delivered

For a rollout the same simulation is published as SCORM or xAPI into your LMS. With test mode on, it reports who completed which module and where they went wrong, which is the evidence an audit or an onboarding sign-off actually needs. We also build these in Adobe Captivate, whose three recording modes map onto exactly this pattern.

It belongs to our custom e-learning development services, and often sits alongside the software training video for the same product, where the video covers the overview and the simulation covers the doing.