March 3, 2010
For most software product managers I know, localisation can be a four-letter word. Localisation is the process of adapting software for non-native environments, usually other nations and cultures. Localisations take a long time and require significant development effort, but they are usually necessary if you want to sell into foreign language-speaking markets. Typically the localisations are of the software user interface, and the documentation and training materials.
While working in product development, I occasionally hear the suggestion that we can have one of the developers or field engineers that speaks the local language localise the product. Although this seems like an efficient solution, there are many reasons to avoid it; here are a few:
- Inconsistencies. Localisation vendors use a database, called a Translation Memory (TM). If you don’t have an existing TM, the localization is likely to be inconsistant. If you do have an existing TM, the developer wouldn’t likely have access, which requires the purchase of a license, their translation may be inconsistent with what already exists. Also if your company does have an existing TM, there is a cost to update the TM with the internal localisation.
- Overhead of coordinating internal localisation. Most people with experience know that this is a non-trivial task; the localisations need to be reviewed and corrected, and this all takes time.
- Opportunity cost of paying engineers to localise rather than code.
- Lack of local knowledge. The developer may not be familiar with regional variations/style.
If you are only looking at a few sentences and are in a screaming hurry, localising internally and then updating the TM is an option, but for the reasons outlined above, you may find it’s less efficient than planned.
Leave a Comment » | 
Translations | Tagged: Development process, localisation, product support management, translation memory, Translations | 
Permalink
Posted by kevinbarefoot
February 26, 2010
Brian Solis’s ebook on customer service provides some good examples of organizations using social media to reach out for customer service.
From the book:
“You can bet that for every inbound customer inquiry, that there is a significant
percentage of existing and potential customers actively discussing the same
topic out in the open, simply looking for guidance, feedback, acknowledgment,
and/or information. And usually, these discussions transpire without company
participation, leaving people to resolve issues and questions on their own.”
Some organizations mentioned: Southwest, Freshbooks, ACDSee
Leave a Comment » | ebooks | Tagged: Brian Solis, customer service | Permalink
Posted by kevinbarefoot
February 17, 2010
I’ve recently been rewriting some blog bios and wanted to capture key points to include. It’s generally good to have a bio of varying lengths (one sentence, 100 words, 250 words, etc). Numbers 1 and 5 below are required and can be squeezed into one sentence if necessary.
- The first sentence should include your name and clarify what you do, and for whom (your audience).
“My name is Kevin Barefoot, and I am a technical writer and product support manager who operates Barefoot Consulting, a freelance business that helps Vancouver-area software companies plan and manage documentation and support.”
- The second sentence should indicate key professional achievements (including awards, degrees, memberships)
“I hold a degree in writing from the University of Victoria, and for the past ten years have worked at Creo and then Kodak as a technical writer and product support manager where I ensured that software products met business goals by managing service through the stages of alpha, beta, and production.”
- The third sentence should indicate what differentiates you from the competition.
“I have spent significant time learning from and helping end-users, and defining an overall support plan covering areas such as: service risks, tools, and profitability; beta programs; end of life or migration; documentation; training; translations; call reporting; and maintenance requirements.”
- The fourth sentence should indicate what you are working on now, or interesting side projects.
“Lately I’ve become interested in using social media tools to deliver service and support.”
- The fifth sentence should include your contact information.
“You can reach me at kevin dot barefoot at gmail dot com or @kbarefoot.”
Leave a Comment » | Blogosphere | Tagged: author biography, Blogging, writing bio | Permalink
Posted by kevinbarefoot
