LinkedIn Twitter
Well-known expert on why IT projects fail, CEO of Asuret, a Brookline, MA consultancy that uses specialized tools to measure and detect potential vulnerabilities in projects, programs, and initiatives. Also a popular and prolific blogger, writing the IT Project Failures blog for ZDNet.

One response to “Five definitions toward the maturing of Enterprise 2.0”

  1. Steve Christensen

    Michael,

    Absolutely spot on. What you have so well defined is the current environment of an enterprise (commercial and public). Much of the E2.0 dialogue is around consumer applications attempting to bridge into the enterprise arena where the laws of nature are entirely different. At a minimum, the perspective of these vendors might be lacking.

    Enterprise 2.0 has three basic categories: Communication – Operations – Customer. Guiding any E2.0 application are two essential rules: 1) Do no harm – understand and protect the existing business and business systems 2) Increase revenue and/or margin or get out

    Your definition, which is a topology of E1.0 (ERP, BoB, etc.) and E 0.1 systems in my mind, taught us that overhauling any existing systems is disruptive, expensive and an innovation killer. Rule 1 avoids any impact on current systems. They run just fine and do well that which they are already doing. If the system isn’t doing it whatever you do don’t try to make it do it. Rule two requires that actual value be achieved and can best be accomplished by leaving that which is alone.

    So E2.0 will have to fill in the gaps and grow the entire asset value of the enterprise in rapid prototyping, adjustment and roll out. E1.0 and earlier versions of business systems will be blissfully unaware anything is going on nor that the lights have dimmed on their future upgrades and modification prospects while their chances of replacement have gone down.

    Great, instructive blog.