All in Enterprise 2.0

One question I have is how long "social networking" can be a viable business given its steady march into the mainstream. As more and more of our personal and online communications become potentially definable, acquirable, and -- what's really important -- sharable in social networking terms, social-networking-enabled communications will become the norm. When that happens, social networking "features" become commodities and, following basic economics, prices are driven down.
One of the more interesting blog comment series I've read recently is the ongoing discussion about Lotus Notes over at Rod Boothby's Innovation Creators blog. A couple of weeks ago Rod posted Lotus Notes - The Asbestos of Enterprise IT. In it he lambasted Lotus Notes' usability, among other things. This has led to some back and forth - and mudslinging - that when read in the right light tells us a lot about the advantages entrenched platforms have in large corporations when they compete with up-and-coming Web 2.0 "newcomers."
Luis Suarez recently blogged and podcasted about social bookmarking services. He highly recommends BLINKLIST, a service that I have not used. I have been using RAWSUGAR, COGENZ, and CONNECTBEAM, so I also have been forming some personal opinions about social bookmarking.
I learned basic data analysis techniques by studying the relationship between demographics and political opinion poll responses. As an undergraduate in a graduate Political Science course at Ohio State University I used 80 column punch cards (send me an email if you don't know what that means) to instruct an IBM mainframe computer to crosstabulate age, sex, income, and race data with voting behavior and political opinions. Now you can do the same stuff online with little more than an Internet connection and a browser.

Introducing Collaboration Technologies to the Enterprise is a Challenge

One of the interesting topics that came up several times at last week’s The New New Internet conference here in Northern Virginia was the challenge of how to introduce collaborative tools into an organization. This is a topic that is well reviewed in a recent post by Shawn Callahan in the Anecdote web site titled Why People Don’t Use Collaborative Tools.
Given the difficulty of doing Return on Investment (ROI) analysis for IT projects, how do you justify an Enterprise Web 2.0 project? In a comment he left on my How Much Will Your Enterprise Web 2.0 Project Cost? post, Vinnie Mirchandani suggested that one place to start would be to look at the criteria used in the past for evaluating large IT investments.
One blog I read is the Microsoft Knowledge Network Team Blog (registration required). It describes development and features of the "Knowledge Network" product that will accompany Microsoft's upcoming Microsoft Office SharePoint Server 2007 which is also in Beta status.
When considering the potential system integration costs of an enterprise web 2.0 project, one of the first things to do is to identify potential system-related “ripple effects” (if any) of introducing an enterprise web 2.0 system into the organization. We also need to consider the cost implications of addressing and managing these ripple effects over time.
Professor Andrew McAfee has an excellent series of posts related to the application of “return on investment” (ROI) calculations to enterprise IT. His posts deserve a close reading. He gets some flack for seeming to argue against measurement, but as he explains in his second post, that’s not his point; he’s basically saying that too many business cases that rely on a haphazard or incomplete calculation of IT benefits are flawed, incorrect, incomplete, or self serving.