Here's a theme that's been causing a lot of debate amongst my peers of late — is a social intranet the same thing as a social workplace and the same as social collaboration? Can one product or set of features meet the needs of all of these requirements?
The issue here requires an understanding of the differences between communities and teams, affinities and goals.
Defining the Terms
One of the key challenges in this rapidly emerging space is that the vocabulary we have for discussing it is rather poor.
So, the first thing I want to do is define and clarify a few terms. I invite you to debate, discuss and add dimension to these terms. This is what I've laid out as a framework so far.
- Community: a group of people, usually a larger one, 25+ members with some affinity for each other.
- Organization: a company, government agency, enterprise or other formally recognized institution that has a defined purpose for its existence.
- Team: a group of people with a specific objective or purpose for their association.
Many Flavors of Collaboration
I will summarize my ideas on these three types of collaboration (you can also check out the in-depth post I wrote a while back).
- Creative collaboration is a purpose-driven effort toward a specific outcome. There is a specific group of people with a shared objective - in other words, a team. Process, Communication, Organization and Decision making are the critical activities here.
- Connective collaboration is the fine are of connecting the dots, where we (through a weaker set of ties) are able to discover related ideas, key information, spot trends and generally ensure that information and insight is discovered and connected in the right context, at the right time, by the right people. People also use terms like "expertise identification" and "serendipity" to describe this type of collaboration. I think that these are just examples of this type of collaboration, and I don't think that serendipity is a good business plan (we have ways of making serendipity happen - just wait).
- Compounding collaboration is where present meets and leverages past. Where the work of the past is added to, layered upon and compounded so that each of us may stand on the shoulders of those who've come before to accomplish more that we ever could if each had to start from scratch. Some people call this knowledge management. I think it goes well beyond that.
Editor's Note: Also read Hutch Carpenter's Three Types of Collaboration that Drive Innovation.
Connectiveness of Social Intranets
An intranet is (or should be) the digital embodiment of an organization’s purpose and resources. It should inform, empower and enable employees to understand the organization, its mission, and the resources and processes available to help them get their work done.
A good intranet is current, authoritative, relevant and inclusive. It keeps the organization as a whole informed, and gives employees both the map and the keys to the corporate assets. Social capabilities add the dimension of people to this, giving the organization the opportunity to know one another individually and as a team. It gives the leadership an opportunity to communicate more directly at scale with the organization. It becomes an arena to support and develop a corporate identity and culture - a sense of community.
The social intranet - sensitively built and wisely used - can be a crucial instrument of leadership as well as the center of gravity for the sense of belonging and community that is the organization. It can also be the foundation for "connective" collaboration within the organization.
The focus here is on communication of all kinds — structured and unstructured, formal, informal, ambient (e.g., microblogging), coupled with excellent search and discovery.
- Office 365 is a Disaster Waiting to Happen
- Don't Hold Your Breath: SharePoint Release Delayed
- Does the Apple Watch Signal a Post-Browser World?
- Who Leads in Multichannel Campaign Management?
- Hey Cloudera & MapR: Open Data Platform is the Real Deal
- 8 Tips to Spring Clean Your Digital Work Life
- 11 Ways to Ruin Your CMS Project Without Even Trying