Localization in the Flat World

You need to understand the localization process - even if you're in denial about it - because the world is flat (apologies to Thomas L. Friedman) and the sooner you see how the process goes, the sooner you join the ever-flattening world.

Do you see your company in the following scenario?

We're bringing a prospective new client into the flat world. Up to now, they've dealt with translations, in which somebody overseas says, "We need to be able to read this document in our own language." Recently, though, the folks overseas are saying, "We need to be able to use your product in a way that makes sense to us." The unspoken rest of the sentence, of course, goes, "...or we'll find a different one and use it."

They are on the road to localization. What's next?

1. Demystify the process. What's really involved in creating a localized product? How much will it affect this organization?
2. Identify and talk to all stakeholders. Inform them of what's coming and what will be required of them.
3. Figure out exactly what needs to be localized: software strings, documentation, help, Web pages, installer strings, sample files, etc.
   
4. Create a project plan. Much of it will be wrong the first time out, but as long as you know it's a living document, it will serve its purpose.
5. Appoint or find a project manager. The localization project needs a champion (some might say a lightning rod), because it won't all happen on its own.