When Should We CollaborateDecember 4, 2012 Leave a comment
I like to describe IISC as a collaboration shop. We look at collaboration through three lenses. When looking through the lens of networks we are acknowledging a shift from “complicated to complex” (see image). We often rely on the Cynefin framework to encourage an attitude of exploration, a more open attitude than the quest for technical answers that obsesses so much of our work for social change.
I had not seen the overlay of complexity and collaboration that Shawn Callahan articulates so well. I love the work of our friends at Anecdote, and this blog post is a must read:
Is it collaboration when you’re sent the yearly performance review spreadsheet and instructed to assess your staff’s performance? Absolutely not; it’s an act of co-ordination. Everyone is working separately to achieve the overall goal of conducting the performance reviews. Only a modicum of trust is required (trust in the system) to get the job done.
So, is it collaboration when you meet with your team to work out the performance review process? Not quite. Here we are co-operating with our colleagues to deliver a task that we all know needs to be done. When we co-operate there is often a medium level of trust involved (trust in each other’s competencies and character), the value of the activity tends not to accrue directly to the participants co-operating and, in most cases, someone else is driving you to do it. 
So what is collaboration then? It’s when a group of people come together, driven by mutual self–interest, to constructively explore new possibilities and create something that they couldn’t do on their own. Imagine you’re absolutely passionate about the role that performance reviews play in company effectiveness. You team up with two colleagues to re-conceptualize how performance reviews should be done for maximum impact. You trust each other implicitly and share all your good ideas in the effort to create an outstanding result. You and your colleagues share the recognition and praise equally for the innovative work.
The important factor is mutual self-interest. When people create things they really want to create, and it is also good for the company, it energizes and engages people like nothing else. Just ask Google, who have institutionalized collaboration by giving every engineer 20 per cent of their work week to spend on any project that takes their fancy.
Today most commentators conflate co-ordination, co-operation and collaboration under the single banner of ‘collaboration’. All three types of working together are important, but creating environments where collaboration (as we have defined it) happens creates a spark that will truly transform an organization. The important skill is knowing when to collaborate, co-operate and co-ordinate.
When is the best time to collaborate?
When thinking about good times to collaborate, it’s useful to start with a simple model that helps us understand the nature of the types of issues we might encounter in an enterprise. Here I’ve illustrated the Cynefin (pronounced cun-ev-in) framework, which categorizes organizational activity into four domains.
Simple: this is when there is a clear relationship between cause and effect. When you do X you always get Y, and no matter how many times you do X you get the same Y result. Organizing the performance reviews is a good example. You can predict with confidence the end result of the activity. In these cases co-ordination can be used to great effect.
Complicated: this is when there is still a relationship between cause and effect but you have to put effort in working out that relationship and there is often a range of possible answers. This is the realm of experts who put in the effort working out these cause-and-effect relationships. Co-operation is effective in this domain because there is often a clear end goal in mind but you need the combined forces of a range of people to achieve it.
Complex: this domain is characterized by causes and effects that are so intertwined and intricate that things only make sense in hindsight. You hear people saying: “Ah, the reason that happened was because …”, but if you rewind the tape of what just happened and play it again, you get a different outcome; rewind and play again, and yet another outcome. This phenomenon occurs because in complex situations everything is so interconnected that a small change in one part of the system can have inordinate impact somewhere else, and vice versa. The system is unpredictable in detail, yet we can discern patterns. Designing and implementing a new performance management approach is complex because, regardless of how much analysis we do before putting it into practice, we won’t know how it’s going to work in detail. It is in these complex situations that collaboration comes to the fore.
Collaboration works well for complex situations because the style of working collaboratively matches the nature of the issues that complex situations pose. Complexity is unpredictable, and collaborating is adaptable; complexity is messy – it’s difficult to work out the question, let alone the answer – and collaborating involves bringing together a diversity of people and talents to improvise and test possible approaches, all learning as you go. Complexity offers unique and novel conundrums, and collaboration draws on a deep foundation of trust to that fosters creativity and delivers innovations.
The last domain of the Cynefin framework is chaos. This is where it’s impossible to discern a relationship between cause and effect. The best approach in this domain is simply to take action. Paradoxically it really doesn’t matter which group style is used here, as any way of working will either create opportunities in the complex space where collaboration can take effect, or push the situation into the simple domain where a co-ordination approach is effective.
With the Cynefin framework as a guide, we can better align the type of group work with the nature of the issue at hand. Collaboration is not the best approach in every situation and let’s not fall into the trap of thinking of it as a panacea. Sometimes it’s simply more effective to issue a direction to get the job done when the job is simple or complicated. It’s when things are truly complex that collaboration is most effective, and the reality is that the world is becoming more connected, faster moving and therefore more complex by the minute. Collaboration will have a growing role to play in every organization.
Interesting overlay and I agree that collaboration may is not the best way to behave in every situation. But I’m not completely sold on the way the author distinguishes between cooperation and collaboration.
He describes collaboration as “It’s when a group of people come together, driven by mutual self–interest, to constructively explore new possibilities and create something that they couldn’t do on their own.”
Seems like a lot hangs on the question of motivation. But I don’t think all cooperation is extrinsically motivated while all collaboration is intrinsically motivated. And, he says that the benefits of cooperation don’t generally accrue to the people involved, while the benefits of collaboration do. I’m not sure I see that either. There are times when those coming together to address a complex situation don’t all have the same level of self-interest (except in the sense that they want a social good to be created or a problem to be solved) or expect the same level of benefit from the collaborative solution. And, I think what he describes as cooperation can also arise from mutual interest, and can also be relevant in a situation where the individual players can’t achieve something alone. It would be appealing to think that collaboration is only relevant in the complex space (which occupies a lot of our attention, as it happens), but I think it’s more complicated than that!