The Two-Year Lag from Web 2.0 to Enterprise 2.0

The Enterprise 2.0 sector draws heavy inspiration from innovations in the Web 2.0 world. Indeed, the name itself, Enterprise “2.0” reflects this influence. From a product management perspective, Web 2.0, and its derivations social networking and social media are great proving grounds for features before coding them into your application.

A fruitful area to review is how long it takes for a feature to go from some level of decent adoption in the consumer realm to becoming part of the mainstream Enterprise 2.0 vendor landscape. The list of features that have made the jump – forums, wikis, blogs, tagging, social networking, activity streams, status updates – is impressive. Let’s look at three features that made the leap, with an eye toward how long it took.

Tool	Year of Web Adoption	Year of E2.0 Adoption
Wikis	2002	2004
Social networking	2006	2008
Microblogging	2007	2009

Here’s the back-up for those dates.

Wikis: Wikis got their start back in 1995. From there they grew, and the application became popular with computer programmers. But it hadn’t caught hold outside that culture. Wikipedia was launched in January 2001, and grew rapidly over its first two years. It wasn’t yet mainstream, but it clearly had caught a wave among early adopters. As recounted on the history of wikis page in Wikipedia, 2004 – 2006 saw an explosion of interest in wikis from companies.

Social networking: Defined as enabling social profiles, and connecting with others. Facebook started in 2004, and grew very popular among colleges. In 2006, it opened up its membership beyond college students, and turned down a $1 billion offer from Yahoo! Clearly, the company was on fire (even then).

In April 2008, Jive released Clearspace 2.0, which was touted as Facebook for the enterprise. Socialtext 3.0 was released in September 2008, and it included Socialtext People, its social networking feature. And I can tell you that at BEA Systems, there was a second quarter 2008 release of a Facebook for the enterprise in the Aqualogic product line.

Microblogging: Twitter. The source of it all. Twitter actually was conceived as an idea back in 2000, and company was started from a 2006 brainstorming session at Odeo. But it really hit big with the early adopter set at 2007’s South by Southwest.

Microblogging broke into the Enterprise 2.0 world when Yammer won best-of-show at the September 2008 TechCrunch 50. But that doesn’t count as mainstreaming into Enterprise 2.0. Yammer proceeded to grow strongly the next few months. And Socialtext introduced Signals in March 2009.

So there’s some documentation backing my 2-year cycle for Web 2.0 innovations to move from hitting the early adopter set to the Enterprise 2.0 sector. Note that this doesn’t apply to every Web 2.0 innovation. No one ever talked about “MySpace for the Enterprise” and there’s really not a Flickr in the Enterprise 2.0 umbrella.

Which raises a question about today’s hottest Web 2.0 trend…

Foursquare for the Enterprise?

Foursquare, and its up-n-coming competitor Gowalla, are all the rage these days. These location-based social networks are good for seeing what friends are doing. Foursquare also integrates features that reward participation (points), add a sense of competition (mayors) and provide recognition (badges).

Mark Fidelman recently wrote about Foursquare and Enterprise 2.0. And using our handy two-year lag calculation, somewhere in early 2012 the first mainstream Enterprise 2.0 will integrate Foursquare features. Actually, two of them.

Location check-ins

Employees will check in their locations from all around the globe. Sales meetings, customer on-site deployments, sourcing trips, conferences, etc. Sure, this info might be in the Outlook Calendar. But even if it is, Outlook Calendar entries aren’t social objects. These check-ins will allow you to know where colleagues are, including those you don’t know well. But wouldn’t it be nice to know if some other employee visited someplace you’re investigating?

These check-ins can be even more tactical. Folks who are part of a meeting in a conference room all check-in. Voila! Meeting attendance, which everyone can see. For an individual employee, these check-ins become a personal history of what you did over the past week.

Mayorships, Badges, Points

Foursquare makes it fun, and for many people, addicting, to check-in. You get points and *bonuses* when you check into the places you go. If you check in to the same place enough times, you get to be mayor of a venue and tweet it about it. You earn badges for accomplishing different things in the Foursquare system.

These features have had the effect of motivating legions of people to participate. It’s fun to see your stats. It’s fun to get a little competitive.  It’s great when you get that notification that you’ve earned a new badge.

Andrew McAfee wrote a series of posts exploring the question of whether knowledge workers should have Enterprise 2.0 ratings. This chart was from one of his posts:

Well, the Foursquare approach certainly takes us down this path, albeit in a fun way. I’d be remiss if I didn’t call out that Spigit already has these tools in place (ahead of its time?).

So what do you think? Personally, I’m looking forward to more Foursquare in the enterprise.

I’m @bhc3 on Twitter.