Thursday, August 27, 2009

5 Basic Reaons Why Enterprise 2.0 Projects Fail

Michael Krigsman recently posted on ZDNet that organizations can follow a simple guideline in order to avoid enterprise 2.0 failure. Here's a quick recap of his 5 points.

1.What’s in it for me’. Not just ‘What’s in it for us’ - Most failures occur at the initial planning phase where the typical business focus is on organization benefits and personal incentives. An example of this is how a sales rep would act in an online community as opposed to an engineer who would want to collaborate, learn, and share information.

2.Social software plays an important but limited role towards Enterprise 2.0 design - Another big stepping stone is premature technology selection. It's best to think of the performance objectives you're trying to affect and then deciding whether a best of breed solution is best of if you can stick with a general purpose platform.

3.Fix the True Break points in Your Organization - You must carefully think through inputs and outputs of enterprise 2.0 design before deploying anything.

4.Figure out the Optimal Ownership Structure - It can be quite confusing to figure out for this broad functional set in the enterprise. Do this instead, identify which benefits most closely support your performance objectives. This should help you figure out the right home for it in the enterprise.

5.There’s Metrics and then there’s Performance Goals - Explain to superiors that metrics for new media is different. You should measure your business based on conversations, engagement, affinity, frequency of sharing, and other such points.

Do you have any more reasons to add to this list?

No comments: