Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Venkatesh Rao

A Crowdsourced Definition of Collaboration

Socially speaking, are you most comfortable working in teams, tribes, or co-groups? Each has its strengths and weaknesses.

I realized recently that my understanding of the term "collaboration," in the flavor-of-the-decade sense, was extremely poor, so I decided to do some digging. As this Google Trends view shows, popular interest in the term peaked in 2004. Media interest began in late 2007 and plateaued by 2009.

chart: Google Trends

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The flavor-of-the-decade sense of the term isn't the same as the dictionary definition, prescriptive definitions offered by major commentators, or technical definitions. So I decided to try to articulate, with hindsight, the zeitgeist definition in all of its sloppy glory. Because that's the definition that matters. There's also a sort of aesthetic logic to this approach: Shouldn't a definition of collaboration be collaboratively created?

To construct my definition, I assembled a sort of tag-cloud of terms associated with collaboration, filtered out those that seemed to reflect the madness rather than wisdom of crowds, and strung together a strawman paragraph. Then I added some of my own theoretical ideas to make the strawman more coherent. Here's what I came up with:

Collaboration: Generating value within a nominally large, leaderless, temporary, partly voluntary, loosely defined, and partially open group that comes together and figures out what do with itself at the same time. The group relies more on exit than on dissent to resolve conflict, is animated by a shared narrative rather than a shared identity, and is driven by a culture of consensus. The group possesses both mechanical and organic solidarity, and is indifferent to its institutional environment unless a conflict with that environment emerges. The group does not engage in direct conflict with alternative group models that compete with it, but instead lets some sort of broader market mechanism determine its fate.

You can work out for yourself why each of the qualifiers and characterizations is in the definition.

In crafting this definition, I realized that we need a word for the kind of group structure that does the collaboration, so I picked "co-group." This word makes the comparison with other forms of group work easier. Co-groups that acquire a layer of formal management can be considered communities, but most co-groups never acquire that level of structure.

It's particularly useful to compare co-groups to two other group types.

1. Teams do teamwork. They work toward objectives defined before the team is. In contrast, co-groups come together before purposes are defined.

2. Tribes fight battles. They're temporary groups that form and disband as appropriate, within a "segmentary" society under situational leadership, to respond to external threats to a shared social identity.

The team was the main group model studied by business thinkers until about 1997. It's still the dominant form within organizations. The tribe is a modern overload of a traditional construct championed by some writers, notably Seth Godin and Dave Logan.

Let's contrast the co-group from the team and tribe.

Collaboration Vs. Teamwork

I put the transition date between teamwork, done by teams, and collaboration, done by co-groups, at around 1997, with the dissemination of Eric S. Raymond's The Cathedral and the Bazaar.

The big jump in connotations was that teamwork referred to work by a small and closed group situated within a given organizational context and specifically chartered by some sort of legitimate authority (such as a CEO). In contrast, from the beginning collaboration has implicitly been based on the idea of a fuzzy, open group that spans organizational boundaries and isn't chartered by any recognizable authority to do anything in particular.

 1 | 2  | Next Page »


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.