Data point 2: Number of Edits per Word/Segment
Tracking a % of how many edits per word or per segment gives you the picture of how much time your editors spend. You can probably assume that the longer they take, the more likely there might be a quality risk.
NOTE: In this case, I see that I have a high percentage of segments needing edited from Arabic, Somali, and Spanish.
Understanding your true cost for each language will help you make decisions that will enable affordable translations.
Data Point 3: Issues per Cost
By tracking the cost per language against the number of issues tracked will give you a huge data point and gives you a sense of what you’re paying for. For example, if you are paying a premium for Spanish and still having a lot of issues, you may consider negotiating the price with your vendor or even switching the vendor for that language.
Note: In the above example, I track my expenses as negative numbers. So, Russian was my most expensive language, but there weren’t a lot of issues, so possibly worth the value! Arabic had several issues, but low cost, and Japanese had Low issues and Low cost.
There are many other data points that could be established. It’s really up to the imagination.
Naturally data just gives you a part of the picture. There are so many factors that go into providing quality translations. Ultimately, if your end-user is happy with the result, that is good quality! However, understanding the effort you spend to get there will help you make decisions even if you don’t know a word in that language!
If you’re Interested in learning more about using data, I’m going to be discussing at our next Google Live Stream. You can sign up to join live or get the link to watch it later.