How to use multi-language for global ERP deployments
Global companies have vast user bases with different cultures and languages. Deploying a global ERP for such large international audiences can be challenging. One of the most common questions that come up is the usage of multi-language functionality within the ERP system. As you know, all Tier 1 systems support dozens of languages. The system can be configured to invoke different languages based on user profiles. Does this mean that we should deploy multiple languages for all the users? Well, the answer is not a simple one. There are a few things to consider.
Most global companies pick a standard "official" language for their management teams to operate under. For example, a USA-based company may require the management layer residing in Mexico, France, Japan to use English for global communications. This standardization helps the company share information more efficiently across the countries. The company can also move its management people around the globe easily. This language preference then trickles down through the management layers across the organization. Thus, it is very common to see it being picked up as a starting point.
Eventually, these global companies realize that the official language may not be appropriate for all the users - especially at the operational level. Such companies employ hundreds of users executing most of the transactions in the system. Imagine the production workers on the manufacturing floor, warehouse personnel in the distribution centers, sales associates in the retail stores. So, in what language should the Standard Operating Procedures (SOPs) be written? In what language should we train the end-users?
This operational level is where the multi-language functionality can be utilized to its full potential. Even though the management level can standardize on the official company language, it is important to accommodate the local languages at the operational level. This will reduce confusion, decrease errors and improve efficiency. These resources do not move across regions and may not be multi-lingual to start with.
In short, you need to have the right balance on how to deploy the multi-language function. Each language introduces new documentation and training requirements to the project. This can get easily out of hand. Imagine the case where you need to replicate 30 SOPs written for warehouse processes across three languages. By the way, you need to maintain them going forward as well. On the other hand, you cannot force down a single language to the lower levels as it will cause confusion, errors, and inefficiencies. The loss in productivity can easily justify the additional administrative work on documentation and training.
If you are interested to learn more, please connect with me on LinkedIn, follow me on Twitter, or watch me on YouTube.
My name is Cem and this has been another gem.
