Hear One, Understand What Exactly?
Ignoring for now the irony of writing about non-verbal communication and trying to illustrate it with compelling and watertight examples, let’s continue our discussion of this key ‘map.’ More specifically, in this article let’s consider how this Low/High Context difference comes about and what it means for us as business people.
There is no doubt that Japanese people have a tendency to be High Context, but are they born that way? Is young Tami-chan from Ooimachi in Tokyo, barely one month after her second birthday, High Context or Low Context, for instance? Overall, although she doesn’t have many words at her disposal, she is fighting to verbalise thoughts. Every day she adds more words to her vocabulary and delights in making herself understand more efficiently and effectively. Her ‘antenna’ are not yet fully developed, and when her mother communicates with her, the focus of that communication is on explicit verbal messages. She is Low Context.
If Tami-chan is reaching for a sharp kitchen knife, for instance, or if she throws her food bowl on the floor, her mother does not talk to her in a High Context way: “Er, Tami-chan, I sharpened that knife just the other day and it’s made of the very best Japanese steel, so to be honest, it might be better to think about playing with something else like this cuddly toy frog…” or, “You may not be all that fond of buckwheat soba noodles, but they’re filling and fairly nutritious, and on top of that, I’ve had a long day, so picking food off the floor and mopping up liquid is not high on my list of things that I’d like to do right now, and anyway, you have to eat something before you go to bed, so I’d really rather you didn’t do that.” Rather, her mother will tell her in a Low Context manner, “NO! Tami-chan, no. Don’t do that. Stop. NOW!”
However, interesting research shows key differences in the education of infants at pre-school in Japan and the United States (Tobin, Wu, and Davidson, Yale University Press, 1991). Respondents were asked, “What are the most important things for children to learn in preschool?” - while 31% of Japanese made “sympathy, empathy, concern for others” their number one choice, only 5% of Americans did the same. In contrast, the top answer for Americans was “self-reliance, self-confidence” (34%), which was chosen as most important by a mere 11% of Japanese. At the same time, then, that very young Japanese children are being encouraged to listen to others and try to understand what they want, Americans are being told to say what they want clearly using words.
When we talked about this research to a Japanese group of middle managers recently, one burst out laughing: “Yeah! You know, my wife told our five-year-old daughter the other to ‘Ba wo yome!’” (“Read the situation!”). At the same time, American, Canadian, and German seminar participants have told us about how their parents urged them to say what they meant when they were young children: “Look at me, Thomas. What do you want? Just tell me. I am not a mind-reader. Speak to me.”
When pre-schoolers move up to grade school, their education systems (designed to create fully functioning adults for their respective societies) continue to push them in different directions. Elementary school students in Western countries have to write simple essays on a weekly basis. Their teachers check spelling and grammar, of course, but also they encourage students to use conjunctions, structure their writing in logical paragraphs, and most important of all, to have a clear main point for each essay. From a young age, then, children in countries such as Canada and New Zealand are being asked, “What’s your POINT?!” If they have a clear point supported by evidence, then they are praised and rewarded (“Your writing is easy to understand. Well done!”). However, what is happening in Japan? In their kokugo (“country language,” i.e., Japanese) classes, Japanese students at elementary school aged only eleven and twelve are given texts and then asked to interpret those texts together with the teacher. The writing often structured in a ki-shou-ten-ketsu (起承転結) manner, with the conclusion coming only at the end after a lengthy introduction (ki), assorted examples of some as-yet-unstated point (shou), an example from a different angle (ten), and then (finally) the main point (ketsu). This kind of training continues throughout school education in Japan, and is a feature of entrance examinations. Students are taught to read between the lines, then.
John Hinds developed this idea with his research into “reader-responsible” and “writer-responsible” cultures (1987, “Reader versus writer responsibility: A new typology” in U. Connor & R. B. Kaplan (Eds.), Writing across languages: Analysis of L2 text (pp. 141-152), Reading, MA: Addison-Wesley). “Reader-responsible” cultures expect the reader to interpret a written text, whereas “writer-responsible” cultures put the onus on the writer to leave nothing between the lines. Chinese, Bulgarian, Koreans, and Japanese, for instance, are said to be “reader-responsible.” Ideas are often pitched at a fairly abstract level, and often conjunctions (such as “Because of this” or “On the other hand”) are omitted because they are implied and understood by the High Context reader (or listener, as we will see below). A sentence taken at random from the November 2008 NHK Radio Chinese textbook provides an example of the High Context nature of the Chinese language: “Zhege xingqitian wo qu lüyou bu zai jia.” Translated directly into English, it means, “This Sunday I go trip not at house.”
In contrast, anyone writing in English is expected to take responsibility for writing explicitly and so she needs to use explicit linking expressions, as well as to structure her writing so that the main point (thesis, or conclusion) comes out in the introduction, with the body supporting that main point, and the conclusion reiterating the main point with some recommendation. Rather than the ki-shou-ten-ketsu mentioned above, it is ketsu-shou-ketsu (結承結); teaching how this pattern works in practice, for example in presentations and business writing, is a key part of what we currently do at INTEC. Now, since we can get information from reading or listening, we can also think of some cultures as being “listener-responsible;” meanwhile, we can give information through writing or speaking, so languages such as English are “speaker-responsible.” And this is wonderful news for non-native speakers of English.
Imagine, if you will, being in a meeting or teleconference with someone who speaks English like a machine gun. If you don’t have much confidence in your own English ability, you may well feel intimated, particularly if you come from a listener-responsible culture. If you happened to be on the receiving end of a burst of verbal fire from that machine gun, you might freeze. However, the good news is that you (as the listener) do not bear the primary responsibility for understanding what is being said. Rather, the speaker bears the primary responsibility for speaking explicitly so that you can understand her. This means that if you don’t understand her, your only job is to tell her, and to do it within one second (“Pardon me?” or “Excuse me” of “Please say that again” or “Please speak more slowly” or “Please give me an example” or “Please write that down”). If you quickly show her when you don’t understand, she can try to explain it again until you do understand, and in that way, you can communicate. If you try to bluff your way through, or if you decide that you don’t want to appear selfish and interrupt her to ask for repetition, it is dangerous. She may think that you are following what she is saying. When she finds out that you don’t, she is very likely to be frustrated: “Why didn’t you just tell me earlier that you didn’t understand?”
This practical piece of advice is deceptively simple and very powerful. It helps to explain many instances of intercultural miscommunication. It is one clear example of the impact of Context on business communication. Another example is the use of contracts. While Low Context people like detailed contracts (as well as manuals), High Context people feel that they cannot put everything into words contained in one document. Their contracts, if they use them, tend to be brief, and their manuals may be vague or abstract. Low Context people often see the world in black and white terms, with 100% answers and absolute values (A is right, B is wrong). High Context people, by contrast, see the world in gradations of grey. Nothing is ever 100%, and values are relative. Whether something is right or wrong depends on the situation.
Finally for this article, please think about one last piece of advice. If you are a Low Context person dealing with a High Context person, when you think there is something that is being left unsaid [with words], then do what you usually do: check it. If you suspect that there may be a ‘face’ issue, then wait until later, or consider using a third party. Use your non-verbal skills to pay attention to ‘atmosphere,’ but don’t rely on your interpretation - check it. After several years of working with the same High Context people, you will develop sensitive antenna, but in the meantime, use the Low Context channel to avoid costly misunderstandings.
On the other hand, if you are High Context and you are working with other High Context people who are from different High Context cultures, then you need to be particularly careful. It is likely that neither person checks explicitly, and while these people may often understand one another quickly and efficiently, the problem is that they sometimes head in completely different directions because of subtle misunderstandings. That can cost you and your company a lot of time and money. Until you are sure that you have successfully built a common context and that you understand the other person’s ‘bottom-part-of-the-iceberg’ (see the article on “Culture”), it is much safer to be Low Context. Make sure that there are minutes for meetings, use contracts to confirm common understanding (while perhaps working to develop sufficient trust to be flexible when absolutely necessary), and follow up conversations with e-mails that summarise what was said in those conversations.
Next time, let’s look at how the ‘map’ of Context relates to explicit time schedules and project planning. For now, though, let me be Low Context and say, “This is the end of today.”