This post follows from the previous, which discussed strategic and ad-hoc adoption of E2. It will map vendors on to that discussion, in a couple of ways.
First, I want to map four specific vendors on the continuum of E2 adoption, anchored at one end by a purely strategic, top-down approach and at the other by a purely ad-hoc, bottom-up approach. I found myself writing down beside that continuum the following four vendors. I’ll list them in descending order of fit with the strategic approach, and hence in ascending order to fit with the ad-hoc approach.
- IBM. I still think of IBM as the enterprise IT vendor that gets in well with top management. That thought may of course be a sign of my age, or of IBM’s.
- Acquia. Drupal is ready to go… built-in functionality, combined with… add-on modules, will enable features such as content management, blogs, wiki collaborative authoring, tagging, picture galleries… Already, “Drupal powers sites including the homepages of Warner Brothers Records, The New York Observer, Fast Company, Popular Science, and Amnesty International and project sites by SonyBMG, Forbes, Harvard University…”
- Six Apart. 6A provides the best illustration of something that’s true for all vendors: a vendor isn’t a single point in the continuum. Movable Type is further toward the strategic end then TypePad.
- Automattic. WordPress requires three easy steps below to start blogging in minutes. Automattic’s projects emphasize the same ease of use and speed.
In case it’s not already obvious, I should point out that the above is a simplification and a starting point. Since first jotting it down, I’ve had conversations (with myself and others) about how to capture the richness of what various vendors offer without obscuring the basic continuum too much. But, having shared the starting point with you, I have another way to look from the strategic/ad-hoc perspective toward vendors.
The starting point for this second half of the post is the claim that some large organizations are in an ad-hoc E2 stage, and are embarking on strategic E2. Such organizations may well decide that their strategy should be based on the lessons and successes of existing ad-hoc E2 efforts. Yes, I am implying that grand strategy is not necessarily better than ad-hocery and tactics, and may often have much to learn from them.
An important challenge, then, is that of managing the diversity of E2 approaches and heterogeneity of tools already present in the organization. One aspect of this is realizing that the organization already has web-based social networks, and deriving from them the social graph.
Did someone say social graph? Brad Fitzpatrick and David Recordon did, and their
Thoughts on the Social Graph aroused much discussion. Their thoughts are couched more in consumer than in enterprise terms.
However, social graph for the enterprise looks like a fascinating arena. The most obvious contender is this arena is, duh, Google, which already has a Social Graph API, on which Brad is currently working.
UK-based Trampoline Systems may also turn out to be a contender. If I were doing E2 strategy for a corporation, and realized that there was a lot of E2 already in that corporation, I’d definitely want to take a look at SONAR Flightdeck, at the server that powers it, and at the API for said server.
I’ve mentioned only half a dozen of the many E2 vendors. That’s fine, by me at least. This post is meant to sketch out ideas, and illustrate them with vendors, rather than to provide detailed comparisons of many vendors. It’s also meant to start discussion…
