HBR's 10 Must Reads on Managing Across Cultures (with featured article "Cultural Intelligence" by P. Christopher Earley and Elaine Mosakowski). Harvard Business Review
Чтение книги онлайн.
Читать онлайн книгу HBR's 10 Must Reads on Managing Across Cultures (with featured article "Cultural Intelligence" by P. Christopher Earley and Elaine Mosakowski) - Harvard Business Review страница 7
Four Interventions
Your team’s unique circumstances can help you determine how to respond to multicultural conflicts. Consider these options:
Intervention type | When to use | Example |
---|---|---|
Adaptation: working with or around differences | Members are willing to acknowledge cultural differences and figure out how to live with them. | An American engineer working on a team that included Israelis was shocked by their in-your-face, argumentative style. Once he noticed they confronted each other and not just him—and still worked well together—he realized confrontations weren’t personal attacks and accepted their style. |
Structural intervention: reorganizing to reduce friction | The team has obvious subgroups, or members cling to negative stereotypes of one another. | An international research team’s leader realized that when he led meetings, members “shut down” because they felt intimidated by his executive status. After he hired a consultant to run future meetings, members participated more. |
Managerial intervention: making final decisions without team involvement | Rarely; for instance, a new team needs guidance in establishing productive norms. | A software development team’s lingua franca was English, but some members spoke with pronounced accents. The manager explained they’d been chosen for their task expertise, not fluency in English. And she directed them to tell customers: “I realize I have an accent. If you don’t understand what I’m saying, just stop me and ask questions.” |
Exit: voluntary or involuntary removal of a team member | Emotions are running high, and too much face has been lost on both sides to salvage the situation. | When two members of a multicultural consulting team couldn’t resolve their disagreement over how to approach problems, one member left the firm. |
The differences between direct and indirect communication can cause serious damage to relationships when team projects run into problems. When the American manager quoted above discovered that several flaws in the system would significantly disrupt company operations, she pointed this out in an e-mail to her American boss and the Japanese team members. Her boss appreciated the direct warnings; her Japanese colleagues were embarrassed, because she had violated their norms for uncovering and discussing problems. Their reaction was to provide her with less access to the people and information she needed to monitor progress. They would probably have responded better if she had pointed out the problems indirectly—for example, by asking them what would happen if a certain part of the system was not functioning properly, even though she knew full well that it was malfunctioning and also what the implications were.
As our research indicates is so often true, communication challenges create barriers to effective teamwork by reducing information sharing, creating interpersonal conflict, or both. In Japan, a typical response to direct confrontation is to isolate the norm violator. This American manager was isolated not just socially but also physically. She told us, “They literally put my office in a storage room, where I had desks stacked from floor to ceiling and I was the only person there. So they totally isolated me, which was a pretty loud signal to me that I was not a part of the inside circle and that they would communicate with me only as needed.”
Her direct approach had been intended to solve a problem, and in one sense, it did, because her project was launched problem-free. But her norm violations exacerbated the challenges of working with her Japanese colleagues and limited her ability to uncover any other problems that might have derailed the project later on.
Trouble with accents and fluency
Although the language of international business is English, misunderstandings or deep frustration may occur because of nonnative speakers’ accents, lack of fluency, or problems with translation or usage. These may also influence perceptions of status or competence.
For example, a Latin American member of a multicultural consulting team lamented, “Many times I felt that because of the language difference, I didn’t have the words to say some things that I was thinking. I noticed that when I went to these interviews with the U.S. guy, he would tend to lead the interviews, which was understandable but also disappointing, because we are at the same level. I had very good questions, but he would take the lead.”
When we interviewed an American member of a U.S.-Japanese team that was assessing the potential expansion of a U.S. retail chain into Japan, she described one American teammate this way: “He was not interested in the Japanese consultants’ feedback and felt that because they weren’t as fluent as he was, they weren’t intelligent enough and, therefore, could add no value.” The team member described was responsible for assessing one aspect of the feasibility of expansion into Japan. Without input from the Japanese experts, he risked overestimating opportunities and underestimating challenges.
Nonfluent team members may well be the most expert on the team, but their difficulty communicating knowledge makes it hard for the team to recognize and utilize their expertise. If teammates become frustrated or impatient with a lack of fluency, interpersonal conflicts can arise. Nonnative speakers may become less motivated to contribute, or anxious about their performance evaluations and future career prospects. The organization as a whole pays a greater price: Its investment in a multicultural team fails to pay off.
Some teams, we learned, use language differences to resolve (rather than create) tensions. A team of U.S. and Latin American buyers was negotiating with a team from a Korean supplier. The negotiations took place in Korea, but the discussions were conducted in English. Frequently the Koreans would caucus at the table by speaking Korean. The buyers, frustrated, would respond by appearing to caucus in Spanish—though they discussed only inconsequential current events and sports, in case any of the Koreans spoke Spanish. Members of the team who didn’t speak Spanish pretended to participate, to the great amusement of their teammates. This approach proved effective: It conveyed to the Koreans in an appropriately indirect way that their caucuses in Korean were frustrating and annoying to the other side. As a result, both teams cut back on sidebar conversations.
Differing attitudes toward hierarchy and authority
A challenge inherent in multicultural teamwork is that by design, teams have a rather flat structure. But team members from some cultures, in which people are treated differently according to their status in an organization, are uncomfortable on flat teams. If they defer to higher-status team members, their behavior will be seen as appropriate when most of the team comes from a hierarchical culture; but they may damage their stature and credibility—and even face humiliation—if most of the team comes from an egalitarian culture.
One manager of Mexican heritage, who was working on a credit and underwriting team for a bank, told us, “In Mexican culture, you’re always supposed to be humble. So whether you understand something or not, you’re supposed to put it in the form of a question. You have to keep it open-ended, out of respect. I think that actually worked against me, because the Americans thought I really didn’t know what I was talking about. So it made me feel like they thought I was wavering on my answer.”
When, as a result of differing cultural norms, team members believe they’ve been treated disrespectfully, the whole project can blow up. In another Korean-U.S. negotiation, the American members of a due diligence team were having difficulty getting information from their Korean counterparts, so they complained directly to higher-level Korean management, nearly wrecking the deal. The higher-level managers were offended because hierarchy is strictly adhered to in Korean organizations and culture. It should have been their own lower-level people, not the U.S. team members, who came to them with a problem. And the Korean team members were mortified that their bosses had been involved before they themselves could brief them. The crisis was resolved only when