Skip to main content

For Global Leaders - When Culture does not translate

Last year at Global leadership summit I heard Erin Myer professor at INSEAD, Paris talking about her book 'The Culture Map'. I recommend it highly as the read is rich in data points analyzed by professor Myer's research on implicit and explicit communication;  and how different cultures
communicate and understand the same things differently. For Global leaders understanding these nuances of high context and low context, cultures is an important skill to have when they are leading cross-cultural global teams.

In a summarized  HBR article 'When the culture doesn't translate'  Erin gives 5 approaches a global leader should be aware of when managing cross-culture communications. These are:

1. Identify the dimensions of difference
2. Give everyone a voice
3. Protect your most creative units
4. Train everyone in key norms.
5. Be heterogenous everywhere.

Communication breakdowns can be avoided as we plan for international cultures. Asian cultures like Thai's and Indians make decisions by consensus compared to their American counterparts. I have experienced this as well though being Asian my work life has primarily been in the west and it's easy for me to talk out loud, interject and speak up on an agenda that was just given an hour ago. The Thai's, on the other hand, would be flustered as they didn't get time to prepare or discuss in between themselves before the meeting. Some other examples she cites are when Google tried to impose its culture in the Google France office where negative criticism during appraisals is expected so a form that cited 10 good things you did well do not necessarily work; or a French company like L'Oreal in its own cultural context of communication ambiguity is expected within their creative teams but the same ensures for confusion to its American teams.

Erin suggests for global managers to be effective making sure the agenda is sent beforehand, assigning someone to recap the discussions and put it in writing and checking in every 10 minutes during an international call if everyone is on the same page are helpful things one can do to increase collaboration and understanding. A follow-up email summarizing the meeting, decisions made and timelines are very helpful for creating accountability horizontally and vertically.

Power distances, gender, and age gaps are variables that add noise in distant cultural communications for them to go haywire and create misconceptions which in turns lowers productivity and leaves project and program objectives incomplete. So training everyone to adopt some of the local norms and implementing non-negotiable organizational norms goes a long way in cross-cultural collaboration to become successful.

Thoughts,

Dr. Sam Kurien

Comments

Popular posts from this blog

IT as a Innovation Partner in Business

Usually in Business organizations and especially in organizations where R&D is a separate department itself a tension persists on keeping the IT department away from any decision when it comes to innovation or process improvement. In short the IT department is generally seen as less of a help and more of a hindrance to innovation efforts. One of the main reasons is traditionally information systems are designed to impose structure on process, achieve pre-defined goals, produce metrics and minimize need for human interaction (in some case over maximize human interaction leading to nothing but "meetings").

While Innovation activities are highly unstructured and emergent, IT cannot be ignored or kept in isolation because IT can help in visualization tools, data mining efforts, uncover hidden relationships between data and create tools of knowledge management/information repository that so desperately is needed cross functionally but especially by the innovators within a org…

Analysis of SAP’s Platform Strategy

The software industry has been through high and lows up with the constant advent of new technological innovations and rapid changes in the global economic landscapes. SAP is the leading enterprise application software giant started by Hasso Plattner. The rise of Enterprise application industries started in early eighty’s with organizations needing one single software program that was capable of serving the multiple needs and functions of various departments. One single enterprise-wide application software means integrating applications that fused together for the smooth exchange and extraction of information. For example when customer services sold a product and got stock updated in the inventory by the warehouse people and the same data could be pulled by the Finance department. Enterprise Application software’s were designed exactly to do the latter mentioned processes seamlessly. SAP started by break away engineer’s Plattner and group build the company on strong engineering fort…

How Dashboards can mislead

Read an interesting article from John Shapiro professor at Northwestern Kellog on how dashboards can mislead executives and I cannot agree more. To be honest, I love visualization of data and have pushed my data architects and report writers to give me snapshots of various measures but how often the rich data didn't mean anything as it did not align with organizational goals. Even more, what information is important to me is not necessarily relevant to other executives in the organization.  Data analytics visualized on dashboards typically describe existing measures on past phenomena, some better ones predict future events and past data and the best one prescribe a course of corrective or strategic actions.

Shapiro talks about three types of traps executives can fall for:

1. The Context Trap:  We equate empirical data to the objective. I have blatantly used the cliche "numbers don't lie." But this belief can be dangerous because we can track wrong measures or metrics…