My Learning Blog

If localization is the key part of the project, as designers, it is important to know how will we localize? Would we outsource the solution to a vendor or build it inhouse. For larger projects, typically, English language is done inhouse and the solution is outsourced to translation companies for other languages. If the solution is smaller, say the content needs to be localized in one or two other languages, organizations might want to bring the localization experts inhouse so that the teams can work closely. Here are some general guidelines I learnt while working on localization projects: General Think globally. Keeping data and functionality location independent. Different languages convey the same thought differently. Also, some languages are longer than others. Therefore, always, always, always leave room for text expansion in the page while designing space for text in buttons, menu items and paragraphs. Stick to the examples that have similar interpretation globally...

Strategy: Work out the curriculum and course level instructional strategy. Identify consistent elements for the entire curriculum - what are the look-and-feel elements and functionality what will remain same for the entire curriculum. Identify the disparate elements - what look-and-feel elements and functionality will change for a specific course within the curriculum so that the learner interest is maintained. Work out a higher level assessment strategy for the entire curriculum. Decide if pre- and post- assessment will be provided at curriculum level, course level or both. Scripting: Maintain a comprehensive style guide. Keep the document alive. Maintain a glossary document that houses the glossary terms and descriptions for all the courses, as they develop. You will be able to easily reference this document for newer courses. Make sure the design changes as a result of content variation is aligned to the curriculum look and project scope. Keep an eye on the word count to make sure t...