I hate it when this happens...
Nov. 30th, 2010 11:07 amAfter translating a few hundred words of the project due soon after noon today, it became apparent that I had run my eyeballs over identical text, and recently. As it turned out, the end client had submitted a document for translation to my client that I had translated almost three weeks ago for said client.
Now, there are translators of my past acquaintance who would yawn, calmly pour and drink a cup or two of coffee, maybe run their eyeballs over the previously translated text, stretch languorously, and then send off the document and invoice another payday, but the way I see it, taking advantage of an oversight like that—and it's an oversight even if it was made deliberately—is poor business.
I'll leave the preachy reasons for why this is so as an exercise for the reader, except for one that I call "the human element."
The client, you see, is not just some vague corporate entity at the other end of the cloud. In practical terms, there is a human at the other end of the connection who goes by a title such as "Translation Coordinator" or "Project Manager" and who is typically under more pressure to Get Stuff Done™ than a mongoose at a cobra convention.
If it turns out the end client goofed, you've given your client an opportunity to shine. If it turns out that the person who sent you the assignment made a mistake, then you've just saved them from getting chewed out by their boss. In either case, I've found that making the person at the other end of the connection look good translates (pardon the pun) into more assignments, made more frequently.
And what's really mind-blowing is this: In more cases than I care to count, after I've made clients aware of the situation, they've instructed me to continue with the assignment and to invoice it.
So now that half of today's to-do list is punched. I think I'll go for a walk.
Cheers...
Now, there are translators of my past acquaintance who would yawn, calmly pour and drink a cup or two of coffee, maybe run their eyeballs over the previously translated text, stretch languorously, and then send off the document and invoice another payday, but the way I see it, taking advantage of an oversight like that—and it's an oversight even if it was made deliberately—is poor business.
I'll leave the preachy reasons for why this is so as an exercise for the reader, except for one that I call "the human element."
The client, you see, is not just some vague corporate entity at the other end of the cloud. In practical terms, there is a human at the other end of the connection who goes by a title such as "Translation Coordinator" or "Project Manager" and who is typically under more pressure to Get Stuff Done™ than a mongoose at a cobra convention.
If it turns out the end client goofed, you've given your client an opportunity to shine. If it turns out that the person who sent you the assignment made a mistake, then you've just saved them from getting chewed out by their boss. In either case, I've found that making the person at the other end of the connection look good translates (pardon the pun) into more assignments, made more frequently.
And what's really mind-blowing is this: In more cases than I care to count, after I've made clients aware of the situation, they've instructed me to continue with the assignment and to invoice it.
So now that half of today's to-do list is punched. I think I'll go for a walk.
Cheers...