Skip to content
caprivideo

E-learning and training

From watching a lesson to using it at work

Make training useful beyond the final screen. Connect your explanation to a task learners can complete and check whether they can apply it at work.

Capri Video · Updated · 5 min read

Key takeaways

  • Plan a learning video around an observable objective, such as choosing the right queue for a request, rather than a vague goal like understanding a process.
  • A worked scenario that shows the reasoning behind one decision teaches more than a tour of the whole policy or company handbook.
  • Put a check question with feedback beside the video, since a video file alone does not create an assessment or send results to a learning management system.
  • Completion only shows that playback reached a point, so judge the video by whether learners answer the check question correctly and for the right reasons.

The course is complete. Every slide has been covered, the narration sounds good and the final screen says “Well done.” Then a learner encounters a slightly different situation at work and cannot decide what to do.

Before planning the film, ask what someone should be able to do after watching. “Understand our process” is difficult to check. “Choose the right queue for a customer request using the two routing criteria” gives the film a job, the writer a boundary and the course designer a useful assessment question.

Start with an observable objective

For course designers: “Given a fictional customer request and a routing guide, select the appropriate team and explain the choice.” This is a manageable brief for an introductory film. “Master customer support” is not.

Then decide what the video must teach to support that action. If a paragraph does not introduce the situation, demonstrate the decision or explain the reasoning, consider moving it into an optional reference. A comprehensive script is not always a useful lesson.

A worked scenario beats a tour of the policy

Here is a hypothetical training scenario for a fictional support team. Its routing guide distinguishes between account-access requests and product-how-to questions. The objective is to use that guide, not memorize an entire company handbook.

The storyboard follows one request from arrival to a reasoned choice:

  • Situation: A customer says they can sign in but cannot find a reporting feature.
  • First observation: The learner sees two relevant facts highlighted: access works; the question concerns using a feature.
  • Decision: The film compares the two possible queues using the fictional routing guide.
  • Explanation: The request goes to product support because the problem is about feature use, not account access.
  • Practice: A new request appears, and the course asks learners to choose a queue before revealing feedback.

A short narration passage might say: “Start with what the customer can already do. They can sign in, so this is not an access problem. Their question is about using a reporting feature. Under this team's routing guide, that belongs with product support.”

The explanation makes the reasoning visible. It avoids presenting a rule as a magic answer that learners must simply remember.

Put a check question next to the video

For this fictional example, a follow-up question could be: “A customer cannot get past the sign-in screen. Which queue should receive the request, and which fact supports your choice?”

The expected answer is the account-access queue, supported by the inability to sign in. Useful feedback explains that connection. “Correct” alone leaves less for the learner to apply to the next situation.

Place the question in the surrounding course, a facilitator guide or another agreed learning surface. An ordinary video file does not by itself create an interactive assessment or send results to a learning management system. Specify those requirements separately and confirm who will implement them.

Plan captions and supporting text early

Treat captions and a transcript as planned deliverables, with an owner and a review step. Ask for the required format before production. Decide whether captions will be a separate track, visible within the image or both for different destinations.

Review names, specialist terms and timing. If a diagram carries essential information, make sure the narration or accompanying text also explains its meaning. A transcript containing only “as you can see here” is not a useful substitute for that explanation.

Design the screen so that labels and captions have space. Keep the key distinction visible while it is discussed, and avoid requiring viewers to read a dense paragraph while listening to different wording. Test the result in the actual player and on the devices your learners use.

What to put in the brief

  • One observable objective and the intended learner's starting knowledge.
  • A realistic, fictionalized scenario with no unnecessary personal information.
  • Approved subject matter and a named specialist reviewer.
  • A worked explanation and a separate practice question with feedback.
  • Language, caption, transcript and player requirements.
  • A content owner, version label and review trigger.

If you are teaching a software workflow, align the script with an approved product version. Our One task tells a better software story discusses choosing a workflow that viewers can follow without seeing every feature.

Costs and updates belong in the same conversation

The work involved depends on more than the length of the film. Several scenarios, language versions, custom illustrations and multiple subject reviewers all affect the cost. So does the condition of your source material: a signed-off procedure is different from three contradictory slide decks.

Ask how later updates will be handled. Keep changeable interface labels and policy details easy to identify in the script. Record a version and review date outside the spoken narration where appropriate, so that an administrative date change does not automatically require a new voice recording.

For a series, agree consistent terminology and visual conventions before producing the full set. Keep a small content register listing each video's objective, owner, source version and publication locations. When a process changes, this makes the affected lessons easier to find.

Measure the objective, then inspect the film

Completion tells you that playback reached a point; it does not prove that the learner can perform the task. Compare answers to the check question, look at the reasons learners give and note repeated misunderstandings.

Avoid attributing a change in workplace performance to a video without considering other changes in the course or working environment. Start with the narrower question you can examine: can this audience apply the distinction the film teaches?

A few practical questions

How long should each learning video be?

Long enough to explain and demonstrate its objective without unrelated material. Estimate the length from a spoken read-through and the time needed to inspect visuals. Split the lesson when it contains separate decisions that need separate practice.

Can an explainer replace a complete course?

Usually it covers one part of the learning design. Practice, feedback, reference materials and any required assessments still need their own place. Define the video's role before commissioning it. Our guide to corporate training videos shows how a series of lessons fits together.

Can the same film work in German and English?

Plan separate language versions, including on-screen text and reviewed terminology. Allow for different sentence lengths and check each version with the intended audience. A translated script still needs a timing and meaning review.

You can browse our styles and tell us about the lesson. Bring the learning objective and the material you use today. For technical subjects, read about Explain the machine beyond the sales meeting.

See your offer as a video

We create a free watermarked video for your business from your website. Once it’s ready, you decide whether to keep it with a subscription.

Create my video