A training manager is shortlisting three blended learning platforms. Every vendor shows her the same thing: a tour of menus, a dashboard and a list of features. At the end she can say what each product contains. She cannot say what a new sales hire would experience in the first week, or what the trainer would do on the day of the live session. So she asks a different question: "Show me one learner going from preparation, through practice, to a live session."
This is an illustrative scenario, not a documented customer case. It is the right question, and this guide shows how to answer it. It is for heads of L&D, instructional designers and training managers who need to demonstrate a blended learning platform workflow, or who are about to watch one. It covers five steps: define the buyer task, show preparation, show practice, show the move to a live session, and explain follow-up and dependencies. It ends with a scorecard you can use as the buyer or the presenter.
What is a blended learning platform workflow?
A blended learning platform lets you combine self-paced learning with live, facilitated sessions around the same goal. The workflow is the sequence a learner and an instructor actually go through: what the learner does alone, what they practise, how the instructor picks that up in the live session, and what happens afterwards.
A feature list describes parts. A workflow shows whether the parts fit together. That is why a demo built around one task tells you more than a tour of the product.
Quick facts
| Question | Short answer |
|---|---|
| What should the demo follow? | One real task, from preparation to follow-up, not a list of features. |
| Who should be in the room? | The person who will run the live session, not only the buyer. |
| What counts as proof? | Something shown working in a real environment, with its settings visible. |
| What should be labelled? | Anything that needs another tool, an integration or extra configuration. |
| How long should it take? | About 20 to 30 minutes for one task, plus questions. |
| What does a demo not show? | Whether learners will perform better at work. That needs a pilot. |
1. Define the buyer task and the demo scope
Choose one task your learners must do, in one sentence. For example: "A new account manager handles a customer objection about price using the approved discovery questions." Then list the capabilities the buyer wants to see for that task, such as a preparation check, a practice activity with feedback, a live session and a view of results.
Agree the scope before the demo. State what will be shown live, what will be described only, and what is out of scope. A buyer who knows this in advance can tell the difference between a working function and a promise.
One rule keeps the demo honest: show only what is available in a real product environment today. If a function is on a roadmap, say so and do not demonstrate a mock-up as if it worked.
2. Show the self-paced preparation
Start with the learner. Show what they open, what they are asked to review and how long it takes. Keep it to what the later practice needs: the rules, the terms, the approved questions.
Then show the check. A short diagnostic before the live session tells the instructor who arrives ready. Be clear about what it proves. A recall check confirms that prerequisites are in place. It does not show that anyone can do the task.
If the product is described as adaptive, ask to see what that means in practice. What changes for the learner, based on what, and who configured it? Look for actual behaviour or a visible setting. A claim about an unseen engine is not something you can evaluate.
3. Show the interactive practice
Now show the activity itself. The buyer should see the question or case the learner receives, the choice they make and the feedback they get. Ask three things:
- Does the learner commit to an answer before seeing the group's or the right one?
- Is the feedback specific to the choice, or the same for everyone?
- Which parts does the platform do, and which need an external tool?
The third question matters most. Simulators, video role-play, AI features and integrations with other systems are often described alongside a platform. Treat each as external or unconfirmed until you have seen it working in the demo. For more on designing the practice step, see our guide to matching learning activities to Bloom's Taxonomy, which helps you choose an activity that fits the thinking you want to see.
4. Demonstrate the move to a live session
This is the step most demos skip, and the one a trainer cares about most. Show what the instructor does between the online stage and the live session:
- What they can see about the group before the session starts.
- How they open the session and bring the same material or case into it.
- How participants respond in the room, and what the instructor sees as they do.
- How they get back to individual or group responses afterwards.
The test is coherence. The learner should recognise the case they prepared for, and the instructor should not have to rebuild it. Our guide to connecting self-paced preparation with live coaching sets out what to hand over at each stage, and when to use adaptive, interactive and live learning can help you decide which stages need a live facilitator in the first place.
Ask the presenter to run the live stage with a few volunteers rather than screenshots. A short run with real responses shows you timing and what the instructor does when an answer surprises them.
5. Explain follow-up and dependencies
Close the journey. Show the follow-up and reporting that exist today, and show them for this task. What can the instructor see, who can they share it with and in what form? If the buyer needs something that is not shown, write it down rather than assuming it is possible.
Then ask about dependencies, before you decide:
- Prerequisites. What accounts, content and permissions need to be in place?
- Configuration effort. Who sets this up, and how long did it take for the case you just saw?
- External tools. Which parts of the journey run outside the platform?
- What would change. What would you need to adapt for your own content and learners?
End with a task-specific next step rather than a general sales call: a short pilot on your own task, with agreed measures. A demo shows the journey can be run. It cannot show it will change performance at work.
A worked example: a demo scorecard
Illustrative. A practitioner who runs this training should review the case and the scorecard before use.
The case. A buyer asks how one learner moves from preparation through practice to a live session. The presenter takes the account manager task from step 1 and runs it end to end.
Use this table to plan the demo, or to take notes as a buyer.
| Stage | What the learner does | What to look for in the demo |
|---|---|---|
| Preparation | Reviews the rules and approved questions, then takes a short diagnostic. | The check is shown working. The presenter says what it confirms and what it does not. |
| Practice | Chooses a response to a realistic case and receives feedback. | Learner commits before seeing the answer. Feedback relates to the choice made. External tools are named. |
| Live session | Meets the same case in the room and discusses an ambiguous choice. | The instructor opens the session without rebuilding content and can see responses as they arrive. |
| Follow-up | Completes a new case or a supervised work task. | Reporting shown is real and specific to the task. Gaps are written down. |
Then score the demo on three criteria, each from 0 to 2.
| Criterion | What to record |
|---|---|
| Task execution | The presenter completed the journey for the chosen task, and you can name the action and the evidence at each stage. |
| Reasoning | The presenter explained constraints, alternatives and what is uncertain, including what needs another tool. |
| Boundaries | The presenter separated what is confirmed from what is planned, external or unproven. |
Anchors: 0 means absent or unsupported, 1 means partial with relevant omissions and 2 means complete and justified against agreed criteria. Treat a claim that cannot be shown as a critical error and record it separately, because an average score should not hide it. This scorecard is a proposal, not a validated standard, so adapt the criteria with someone who knows the work.
Where interactive delivery helps
A demo is itself a live session, so the format you are evaluating is one you can feel. When each person in the room commits to an answer before the group result is shown, you see how the practice and live stages behave under real responses. AhaSlides supports interactive learning and moving between live and self-paced delivery, so the same material can be used in preparation and in the room. Check any specific authoring, feedback or reporting function you plan to rely on against your own workflow, and treat AI, simulation and integration features as external or unconfirmed until you have seen them work.
What does the evidence say?
Be careful with claims that blended learning works better. A 2009 meta-analysis for the US Department of Education reviewed studies from 1996 to 2008 that compared online with face-to-face teaching. On average, students in online conditions did better, and the difference was larger when blended conditions were compared with face-to-face only. But the analysts noted that the blended conditions often included additional learning time and instructional elements the comparison groups did not receive, so the positive effects should not be attributed to the medium alone (Means and colleagues, 2009). The review drew mostly on studies in higher education and medical training, so treat it as context for the design, not as evidence about any one platform.
Measure what changed
Decide in advance what evidence would show that learners can do the task. The US Centers for Disease Control and Prevention separates evaluating learning from evaluating whether people apply it at work, and suggests assessing both (CDC, evaluate training: measuring effectiveness). For a pilot after the demo, compare performance on a new, unseen task with a baseline, and define who is included, the denominator and the timing. If scores improve, check what else changed in the same period before crediting the platform or the course.
Constraints that may remain
A good demo does not remove these:
- Set-up effort. The case you saw was prepared for the demo. Your content and your people will take time.
- Tools outside the platform. Anything marked external still needs to be bought, connected and supported.
- Instructor skill. A smooth live stage depends on the person running it, not only on the product.
- Transfer. Completing the journey is not the same as performing at work. Check transfer after suitable work exposure.
Plan for each of these and say so to sponsors. A demo reduces risk in the choice. It does not guarantee the outcome.
Frequently asked questions
How long should a blended learning platform demo be?
About 20 to 30 minutes for one task, with time for questions. A longer demo usually drifts back into a feature tour.
Who should run the live stage in the demo?
Ideally the person who will run it in your organisation, or a presenter who can show exactly what that person would do and see.
What if a feature I need is not shown?
Write it down and ask whether it exists today, whether it needs another tool and what the set-up involves. Do not assume it from a feature list.
Does a good demo prove the platform improves performance?
No. It shows the journey can be run. Whether it improves task performance and transfer needs a pilot with a baseline and an unseen task.
Where to start
Pick one task and write it in a sentence. List the four stages, preparation, practice, live session and follow-up, and write what you want to see at each. Ask any vendor you are considering to run that one journey, then score it with the table above before you compare prices.
To see how a preparation check, an interactive practice round and a live session could run for your own task, explore AhaSlides.
