Software simulations
Show me, try me, test me: the three simulation modes explained
Show me, try me, test me is the most common way to teach someone a task in a piece of software. They watch it done. They do it with help. Then they do it alone and get a score.
Updated
The three modes
Show me
The task plays from start to finish. Each click is highlighted, and a caption or a voice says what is happening and why. The learner only watches.
Its job is to give the learner the shape of the task before they try it: where it starts, how many steps there are, what "done" looks like.
Try me
The same screens, but now the learner does the clicking and typing. A prompt tells them what to do. If they click the wrong place, nothing breaks. They get a hint and try again.
This is where the learning happens. Most people only find out what they did not understand when they try it themselves, and a wrong click here costs nothing.
Test me
The same task again, with the prompts and hints removed. Each step is marked right or wrong. At the end there is a score and a pass mark, and the result goes to the LMS.
Its job is proof. Before go-live, a project lead can see that 380 of 400 people passed "Approve a time off request", and who the other 20 are.
What each tool calls them
The labels differ. The pattern is the same.
| Tool | Show me | Try me | Test me |
|---|---|---|---|
| Articulate Storyline | View | Try | Test |
| Adobe Captivate | Demo | Training | Assessment |
| ClickLearn | Show Me | Try Me | Test Me |
| WalkMe Learning Arc | Demo | Practice | Test |
| dominKnow | ONE | Show me | Guide me, Try me, Practice | Test me |
| iorad | Watch | Try | Quiz |
| Recourse | Demo | Practice | Evaluate |
Mode names read from each vendor's own pages on 29 October 2026. Assima uses See it, Try it and Do it.
Other versions of the phrase
- Tell me, show me, let me try, test me. Adds a first step where the task is explained in words: what it is for and when you would do it.
- See it, try it, do it. The last step is doing the real task in the real system, sometimes with on-screen guidance.
- See it, try it, know it, do it. The four playback modes of Oracle UPK, a tool that is now retired but shaped how a generation of SAP and Oracle training was built. "Know it" was the test. See Oracle UPK alternatives.
They are all the same staircase: explain, demonstrate, practise with support, perform alone.
Why three modes and not one
Each one fixes a problem with the others.
- Only showing feels quick, but watching a task is not the same as being able to do it. People nod along and then freeze in front of the real screen. More on this in why most workplace training does not stick.
- Only practising can overwhelm a beginner. Someone who has never seen the screen spends their effort hunting for buttons. A short demo first lowers the load. See cognitive load theory.
- Only testing tells you who cannot do the task but does nothing to help them.
Not everyone needs all three. Let experienced users skip to the test. If they pass, they are done.
How to build each mode well
Show me
- Keep it under three minutes. If the task is longer, split it into two tasks.
- Say why, not only where. "Choose the cost centre, because this decides whose budget pays" beats "Click Cost Centre".
- Use data that looks real and contains nothing confidential.
Try me
- Write prompts as goals, not directions. "Approve Priya's request" makes the learner find the button. "Click the green Approve button at the top right" does not.
- Let hints build up. First a small clue, then a stronger one, then show the answer. Nobody should be stuck with no way forward.
- Include the typing. Entering a date or an amount in the right format is where real mistakes happen.
Test me
- Test the same task they practised. A test is not the place to add something new.
- Set a pass mark you can defend. A common choice is 80%, with 100% for steps where an error is serious, such as a payment amount.
- Allow a retake after more practice. The goal is that people can do the task, not that they fail.
- Report it. A score that never reaches the LMS proves nothing to an auditor.
A worked example
A hospital is moving to a new electronic health record. Every nurse must be able to record a set of observations.
- Show me (2 minutes). A narrated walkthrough: find the patient, open the observations form, enter the readings, save. The voice explains what the early warning score means.
- Try me (4 minutes). The nurse does it on a made-up patient. They type a temperature in the wrong box, get a hint, and correct it.
- Test me (3 minutes). A different made-up patient, no hints. Pass mark 100% on the readings, because a wrong value on a real chart matters.
Nine minutes each, done on a phone or a ward computer, with a record of who passed before the ward goes live.
Show me, try me, test me in Recourse
In Recourse the three modes are called Demo, Practice and Evaluate. You record the task once, with the built-in recorder or the Chrome extension, or upload a recording, and all three are generated for you to review. In Practice a stuck learner gets a hint, then a nudge, then the answer. Evaluate is scored against a pass mark and, on the Pro plan, reports to your LMS through SCORM.
The steps are in how to create a software simulation.
Questions people ask
What does show me, try me, test me mean?
What is the difference between try me and test me?
What are the simulation modes in Storyline and Captivate?
Do learners have to go through all three modes?
What pass mark should a test me simulation have?
Is show me, try me, test me only for software training?
Keep reading
Last reviewed 19 November 2026. Recourse publishes these guides for learning, customer education and change teams. Details drawn from public sources can change.