I was interviewed yesterday by a Forrester Research staff member about how CIO’s (Chief information Officers) should approach the implementation of collaboration tools (click here for a list of blog posts related to “collaboration”). We talked about the usual adoption issues related to “web 2.0” applications within the enterprise.
All in Cost Analysis
Years of managing, studying, developing, consulting on, and using information technology have taught me about the realities of using technology for business advantage. Here are ten of these realities:
In Should You Make or Buy Your Social Network? I wrote about some of the technology-related decisions that are needed when an organization adopts online social networking.
I’m a member of an exclusive and high quality group on Facebook called “Association of Associations.” It’s composed of professional association executives and managers, members, vendors, and consultants (like me).
The OECD has published the Executive Summary of a major report on international trade involving counterfeited and pirated products. The report, The Economic Impact of Counterfeiting and Piracy, estimates that international trade in 2005 involving counterfeit or pirated works totalled $200 billion US.
Followup to "Is DRM a 'Tax' on the Intellectual Property Supply Chain?"
On May 2, 2007 I published Is DRM a “Tax” on the Intellectual Property Supply Chain? where I compared DRM (Digital Rights Management) to a “tax.”
I’ve received several comments and emails with different perspectives and I wanted to follow up.
Mike Stopforth called me from South Africa last week to chat about Web 2.0 in the enterprise. We talked about a lot of things. One topic that piqued my interest was how different technologies are adopted at different rates in different cultures.
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.
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.