THE TRAINER POINT OF VIEW

Having said in an earlier post that the smaller the learning unit gets the better the trainer needs to prepare such a topic, I would like to share with you how I approach the creation of a new video.

1. Select the topic

This sounds much easier than it actually is. The topic should not be too big or small. You need to be able to cover every angle of it within a maximum of 15 minutes. Also, if this topic ties in with other topics, there needs to be a logical sequence or each topics needs to be self-explaining to be able to stand alone.

Example: Topic = XML in translation

Too big -> split up into: XML basics, XML filter creation, XML in tool A, XML in tool B, multilingual XML, specialized XML like XLIFF or TMX, details in XML (attributes, elements, conditions, entities)…

2. Decide on the sequence.

Decide on the general structure (for learning purposes, it is useful to have the same structural setup for every video). Here is what I came up with:

  • Introduction (what is it good for, when do we use it, what will you learn to do…)
  • Setting the stage (give the basic background information a user needs to understand the following explanations: examples of when such a feature would be used, describe the situation when this feature might come in handy…)
  • Technical groundwork(information on what the feature does, what kind of input it needs and what kind of output is to be expected)
  • The show (video or slides with screenshots of the process)
  • Conclusion (summarize the process, what goes in, what happens, what goes out, when is it useful)
  • But wait, there’s more (additional information on pitfalls, things to consider, mistakes that can be made, things this feature cannot do)

Example: This is roughly what I would do, if the topic was “Analysis Statistics”.

Introduction
  • To create word counts and match statistics
  • Used for pricing in translation projects
  • Estimation of workload
Setting the stage
  • What does the statistic do (count words, compare source language sentences/segments)?
  • Where and when can you run the statistics?
  • How do the results look like?
Technical groundwork
  • What is a word and how do different tools count words
  • What is matching and what different match values are there
The show
  • Select files in a project and start the statistics feature
  • Go through the settings and explain what they mean
  • Create the statistics
  • Explain how to read the outcome
  • Export the statistics
Conclusion
  • What do you use the analysis for?
  • When do you run the statistics?
  • What can the statistics tell you and what not?
But wait, there’s more
  • What settings can influence the number of words or segments?
  • What other settings can influence the match values (penalties on TM segments or alignments…)
  • What if the statistics tell you there are more words in the file than there could be (pitfalls, mistakes that can happen…)?

What do you think? Looking forward to your feedback.

 

Angelika

(Trainer for translation tools since 1997)