The Surprising Downside of Collaboration in Problem-Solving
You are a natural-born problem solver. From the moment you were born, you’ve solved problems. Hungry? Start crying. Learning to walk? Stand up, take a step, fall over, repeat. Want to grow your business? Fall in love with a problem, then solve it more delightfully than anyone else.
Did you notice the slight shift in how you solve problems?
Initially, you solved problems on your own. As communication became easier, you started working with others. Now, you instinctively collaborate to solve complex problems, assembling teams to tackle challenges together.
But research indicates your instincts are wrong. In fact, while collaboration can be beneficial for gathering information, it hinders the process of developing innovative solutions. This counterintuitive finding has significant implications for how teams approach problem-solving.
What a Terrorism Study Reveals About Your Team
In a 2015 study, researchers used a simulation developed by the U.S. Department of Defense to examine how collaboration impacts the problem-solving process. 417 undergrads were randomly assigned to 16-person teams with varying levels of “interconnectedness” (clarity in their team structure and information-sharing permissions) and asked to solve aspects of an imaginary terrorist attack scenario, such as identifying the perpetrators and target. Teams had 25 minutes to tackle the problem, with monetary incentives for solving it quickly.
Highly interconnected teams “gathered 5 percent more information than the least-clustered groups because clustering prevented network members from unknowingly conducting duplicative searches. ‘By being in a cluster, individuals tended to contribute more to the collective exploration through information space—not from more search but rather by being more coordinated in their search,’”
The Least Interconnected teams developed 17.5% more theories and solutions and were more likely to develop the correct solution because they were less likely to “copy an incorrect theory from a neighbor.”
How You Can Help Your Team Create More Successful Solutions
You and your team rarely face problems as dire as terrorist attacks, but you can use these results to adapt your problem-solving practices and improve results.
- Work together to gather and share information. This goes beyond emailing around research reports, interview summaries, and meeting notes. “Working together” requires your team to take action, like conducting interviews or writing surveys, with one another in real-time (not asynchronously through email, text, or “collaboration” platforms).
- Start solving the problem alone. For example, at the start of every ideation session, I ask people to spend 5 minutes privately jotting down their ideas before group brainstorming. This prevents copying others’ theories and ensures all voices are heard. (not just the loudest or most senior)
- Invite the “Unusual Suspects” into the process. Most executives know that diversity amplifies creativity, so they invite a mix of genders, ages, races, ethnicities, tenures, and industry experiences to brainstorming sessions. While that’s great, it also results in the same people being invited to every brainstorm and, ultimately, creating a highly interconnected group. So, mix it up even more. Invite people never before invited to brainstorming into the process. Instead of spending a day brainstorming, break it up into one-hour bursts at different times of the day.
Are You Willing to Take the Risk?
For most of your working life, collaboration has been the default approach to problem-solving. However, this research suggests that rethinking when and how to leverage collaboration can lead to greater success.
Making such a change isn’t easy – it invites skepticism and judgment as it deviates from the proven “status quo” process.
Are you willing to take that risk, separating information gathering from solution development, for the potential of achieving better, more innovative outcomes? Or will you remain content with “good enough” solutions from conventional methods?
