True collaboration embraces conflict

No readers like this yet.
A community building a barn

Opensource.com

Effective collaboration is essential for creating value. Indeed, it's one of the reasons we create corporations, because organizations are more effective than individuals at allocating resources. But knowing and doing are two different things. As organizations grow, collaboration can suffer—particularly across silos, as people learn to work for the benefit of their own group rather than the whole. This lost potential in collaboration is a huge, untapped source of competitive advantage, one that executives appear to be aware of.

In a 2005 McKinsey survey only 25 percent of senior executives would describe their organizations as effective at sharing knowledge across boundaries, even though nearly 80 percent acknowledged such coordination was crucial to growth.1

This article was originally posted on the Management Innovation eXchange (MIX), an open innovation project aimed at reinventing management for the 21st century.

One of the most difficult and interesting aspects of collaboration is conflict. True collaboration can’t exist without personal commitment, and commitment brings with it the possibility of engaging in healthy conflict and debate. If I go to a meeting but don’t have the chance to test my views against contrary opinions, I may leave the room saying “yes” to initiatives without feeling any personal commitment to them. Before you can have healthy debate, you need to establish a baseline of trust that makes it safe to voice dissenting views. You may also need to develop people’s skills in areas such as how to de-personalize ideas, how to ensure that everyone’s views get heard, and how to make it clear that once the debate is done, the decision is binding on everyone taking part, even if their view wasn’t adopted.

Since employees watch their managers’ behavior for cues on the organization’s values, managers can signal the acceptability of conflict by engaging in debate with their seniors. If employees see managers acquiesce to their senior managers without open debate, they’re likely to follow suit. If on the other hand, there is an open commitment to debate and an explicit understanding that debate moves the organization to better decisions, then employees are more likely to bring their ideas into the arena.

Role modeling is only one of several ways that management can signal to employees that conflict is a natural part of collaboration, one that can be managed successfully in the organization. Companies can overtly state that conflict is okay; at McKinsey, for example, the obligation to dissent is a core value because we believe it gets us to better answers when solving complex issues for clients. This obligation is reinforced at every level of training and in company discussions of firm values. Skills in encouraging and managing healthy conflict successfully can be part of ongoing training programs. And of course, managers can reinforce these principles by ensuring that employees don’t suffer negative consequences solely for disagreeing or introducing constructive conflict into a conversation.

We’ve seen many interesting examples of ways to manage conflict effectively and openly in organizations.

Some groups use a visual symbol – a yellow card, for example – in meetings as a way for individuals to signal that they have an objection or that they feel their view (or someone else’s) is being overlooked. Bob Sutton and other management researchers have noted the tendency for senior people to dominate conversation within meetings. Raising the yellow card signals that the objector is acting within the group-defined agreement of behavior and serves as a cue to remind the others that the group has agreed on the necessity and value of conflicting opinions and debate.

In a real-time production environment, quick and informal meetings can resolve issues and fix small problems before they become big ones. Following a series of late deliveries (complete with subsequent recriminations) at one aerospace company, the global head of operations began a policy where if a conflict arose or a mistake was discovered along the production line, all work in that section stopped immediately. The managers of that section, along with those of the sections immediately upstream and downstream, gathered quickly in a team room for a fast meeting to resolve the issue. These meetings rarely took more than 20 minutes, sometimes less than 10, and occurred only a few times a week. But they were effective in quickly resolving problems that might otherwise simmer or create larger issues. Stopping the production line may look expensive, but it was less costly than the mistakes that would otherwise have occurred.

Both of these examples show how managers implemented simple but effective ways for employees to air their conflicts, to openly debate their opinions in a safe environment.

Of course, managing conflict is only one aspect of creating healthy collaboration. In this series, we’ll also explore the roles of people in the collaboration network (brokers and bottlenecks), focusing on collaboration as a means to the organization’s goals, and the need for accountability. We’ll also detail the steps that companies must take to make their collaboration deliver effective impact, in terms of business success and employee morale. Finally, we’ll also look at other opinions on the role and importance of collaboration, including the views of INSEAD’s Morten Hansen who argues in a recent book that a focus on collaboration for its own sake can distract managers from the goals that effective collaboration is intended to achieve and that collaboration should be targeted to the places it adds value.2

How do you encourage healthy conflict resolution in your organization? What is the business value of healthy conflict in your organization?


This is the first in a series of posts from McKinsey about healthy collaboration and how managers make it work successfully.3 In coming months, McKinsey authors will discuss different types of collaboration and the places where it happens, such as knowledge sharing, informal and social networks, talent mobility, and formal communities of collaborative practice. We'll also explore the hypothesis that the proper type of collaboration depends on the type of organization and can take various forms across geographic and vertically integrated groups.

Footnotes

1.   “The McKinsey Global Survey of Business Executives, July 2005,” The McKinsey Quarterly, web exclusive, at http://www.mckinseyquarterly.com/links/22581.

2. Collaboration: How Leaders Avoid the Traps, Create Unity, and Reap Big Results, Morten T. Hansen, Harvard Business Press, May 2009

3. The ideas in these posts are explained in greater detail in our paper, “How do I drive effective collaboration to deliver real business impact?” by Carolyn Aiken, Scott Keller, Johanne Lavoie, and Leigh M. Weiss, September 2009, McKinsey & Co.

Tags
User profile image.
Leigh Weiss is a Senior Expert in McKinsey & Company’s Boston office. She serves clients on organization design and change management. She is a global expert inside and outside McKinsey on knowledge sharing, collaboration and social networks. A leader in the Organization Practice, she serves a range of clients across industries.

2 Comments

Definitely agree with the importance of collaboration and how difficult it can be..we've been using Teambox which works great and it's easy to manage and organize..it's saved a lot of stress and time :) I recommend it to everyone.

www.teambox.com

That sounds promising : ) But indeed, conflict is something we all have to deal with. Now that collaboration takes place across different boundaries (cross-functional, cross-organizational, etc), we indeed need to find ways how to manage this more effectively.

One way of doing this is by creating a healthy form of transparency so that conflict is not only resolved but others can learn from the dialogue.

Bests,

Bart Schrooten
www.lumoresearch.com

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.