Fusion ECM

Dude, the difference is:

You're driving decisions from the CIO, top-down into the enterprise.

I say, let the people speak, i.e. let them drive adoption from the edge-in before you make any grandiose edicts.

So, sure this could be 2 sides of the same coin, if you accept that heads and tails are diametrically opposed.

Jake

Let the people drive adoption from the edge-in.... with what???
If there is no web2.0 technology in the enterprise (because the C's are mandating against it) then what are they driving with? There's no there there without web2.0 tech getting incorporated into the products.

And what grandiose edicts? You and I *both* want cool and useful technology to be adopted by people - whether it's my brother in law in his dorm room or my colleague 3 cubes down from me. My point is that the college student is motivated by different things than the business user (not just the cio).

But to not bother trying to get the CIO on board as early as the business users is silly. That is the crux of my original post: for Web 2.0 to make it in the enterprise, BOTH the users have to drive demand for adoption WHILE the C levels have to approve and incorporate the technology/apps into their budget/infrastructure/business practices.

Props for the engagement!

With what? How about delicious or Reader or any number of social networks? Consumer properties that have value to do work.

Motivation aside, people want to get stuff done. 2.0 tools facilitate this, regardless of where they are used.

I didn't say to leave the CIO out; I said the CIO should listen to the users, not drive policy top-down. I don't see that in any of your posts. What I see is a top-down methodology, cost-benefit, ROI, blah, blah, blah. FYI, the consumery tools are free (as in beer).

Not that it matters. I disagree with top-down; you agree with it. I'm noting the difference between us.

See that's the problem. I don't agree with top-down. I agree that it is necessary to get top down buy-in (they sign the POs, they go to jail for non-compliance). But the DNA behind the keyboards drive the requests while C-levels filter and decide what to buy. It's interesting to note that, coming from Stellent, we sold *much more* to the DNA while obtaining IT buy in on infrastructure compliance etc. The reason our blogs and wikis ECM add-ons were so popular is not because it was new technology (corporations could always use blogger or pbwiki or whatever). It was because it was desired technology with a management capability and infrastructure readiness that IT required before it was brought in.

ECM (the perspective from which I write) straddles the fence between pure IT back end and pure application front end. Take a look at the sales / positioning history of the Stellent product suite and that becomes evident.

Cheers Bro!