So over at Talking IC, Lee Smith links (via Jim Berkowitz) to Jake Swearingen of CNet, who pours cold water on Kris Dunn's idea of experimenting with a social network for his company.
Jake isn't overly polite, so my first instinct is to note how interesting it is that some "technology experts" are very keen to draw distinctions within "Web 2.0" between wikis, blogs, social networks, etc. and yet at the same time think of social networks as this "stuff like Facebook" blob, rather than realising that Facebook et al. are bundles of technologies, which don't all have to come together and could be bundled up with other parts of "Web 2.0" (or even Web 1.0!) and that might well turn out to be the future.
However, I have to echo Lee, (and Kevin Keohane) when he makes the point that it'd be really nice to see some of the people who are always promoting "social networking in the business" actually involved in implementing some, rather than just talking about it.
And yet, that's another reason I find the reaction towards Kris Dunn a bit excessive. At least he's trying to do some empirical work. Maybe it will turn out just as Jake predicts, but at the same time where did we get so sniffy about people trying to "walk the talk"? I at least want to applaud Kris Dunn for trying to make his ideas real.
And as much as I share the general fatigue of Lee and Kevin about the fact that there are more people making money out of talking about social networking in IC than actually doing it, I think there are a number of barriers to current adoption:
Shel Holtz recently posted about JotSpot and in there discusses one of the barriers:
A typical IT response to the notion of introducing social media tools to the intranet focuses on the time and expense involved in testing new applications to ensure compatibility with existing software. If you suggest that the social media tools can be hosted offsite, the odds are pretty good that you’ll be told the information those sites would contain is too sensitive to risk maintaining it outside the firewall.
(This excuse is pretty lame, given that every single one of the US-based companies that has raised this concern in my experience also maintains its employee 401(k) data on a hosted server.)
Now, Shel points up with this last remark that the IT dept's fear of "hosted social networking" might not be wholly rational, but that doesn't mean to say it isn't real. Also, there's a world of difference between putting company data on a pension transaction company's hosted server and putting it on Facebook or even on Ning. There's nothing in the Facebook/Ning terms of service which give the IT Director any kind of job security in the event of a security breach.
So, Lee links to Ning, but fun as it is to experiment there (as Kris Dunn is doing) it's not really an enabler for experimentation in larger corporations. The "where is the data, is it safe?" remains a significant barrier.
To overcome this, you need a internally hosted solution. I don't know how many people have one of these for sale/use. Maybe I'm wrong, but I haven't seen one in an operational state. Without that, we're not going to see much happen. If anyone knows of a good one, let me know.
Other barriers include that fact that everyone thinks "Facebook" when someone says "social network" so there is a lack of other models for what it might look like in circulation. Hence people can't see some of the possibilities. I'll try to repair that in a post later this week, as this is already getting too long.
Reacting to the 3 specific problems Jake mentions:
1) Email is more efficient:
Well, it is now, but it didn't use to be, before Notes, Exchange, Outlook, etc. I remember a day when I did business over email but sent all the docs using a fax machine. Email didn't look that useful then, but it's day has since arrived.
It's easy to see that the messaging systems on social network sites can be improved a lot. Part of why they haven't yet is because social networks have been, up to now, universes-to-themselves for their teenage/college student main customers. Developing the user interface for multi-media communications (blog, email, IM, twitter, SMS) is the hardest part perhaps here. But it will happen.
2) Social networks lose engagement over time.
Complex one this. Studies I've seen suggest that youth communities who establish around social networking stick with it, but being youth communities, the communities lose engagement over time. The older people who rushed into things like Facebook rarely integrated it into their community and so naturally their interest waned. The tool cannot create links that are not really there. If you're married with kids, you have commitments to social networks that are stronger than your Facebook friends list, unless they happen to include the same people. But that's not a common condition.
Corporate social networks do need to be integrated with the rest of the intranet functions, in particular the corporate directory and communication technologies. If it's set up as just another optional site, it won't get much interest. If it's actually a proper part of people's work eco-system, it will, like email, get a lot more use. Especially once you integrate the internal VOIP system (and potentially videoconferencing too.)
3) Social networks are, well, social.
Jake claims that the workplace is not about selective connection. Interesting working life he must have led, connecting with everyone in his organisation equally, every day.
It's true that part of the power of social networks is to cement existing relations, but they also serve to create links, particularly about factual matters (here's where the workplace can really benefit) between people who would normally find it too much effort to stay in touch.
No corporation really wants people to spend all day socialising on the internal network. The value is in creating loose connections between people who would otherwise not have a way to find each other. Yes, everyone can blog about their projects, but how will you find interesting blogs, especially when people have less time to comment and trackbacks still don't work properly? RSS still requires you to know about the blog in question...
Social networking has the potential to answer that. It creates visible topologies which can be followed and human reasons to do so. (And yes, that adds a bunch of human, emotional pitfalls too, but that's always the case in human organisations.)
This of course raises the point that social networks only make sense inside larger communities. If your office is small enough that the "global listserv" email list isn't totally clogged all the time, you probably don't need social networking to help navigate the infospace of your organisation. This is another barrier to adoption.
The laugh is, I type all this and I'm not really a social networking zealot. I just see that blogs, wikis, podcasts etc. are mostly just extra content channels and to me, it's the various kinds of "social" technology that can help us navigate all this content and make it useful, in the end.
Finally, this isn't my area of business, so as interested as I am in it, I'm unlikely to make it happen any time soon. I guess another question for the readers, who do you know who is really working on this? After all, they are the ones I should be inflicting this discourse on...
