Five ways to avoid Enterprise 2.0 failure
Of course there's risk in negation and not-moving-at-all (bear some 21 Risks in not adopting Enterprise 2.0, yes) - but there's some business transformation execution risks as well that come with Enterprise 2.0. Sameer of Pretzel Logic (what's up with 'em Enterprise 2.0 consultants and their funny names, frogpond, pretzel logic, what next? Jolts and Pistachios? Right ...) writes up some of them, but ends on a motivational tone anyway:
If you’re planning social business design, you have it easier than your predecessors who had had to justify and drive large-scale, traditional enterprise software deployments. Today’s Enterprise 2.0 products are faster and easier to implement than ever before.
49 comments
Would be more than happy to see 10 reasons why not get on a E20 journey... Or top 10 reasons why we should not move.
Turn around perspectives? What do you think?
OK, I am joking and turning around the perspectives might be a fun exercise.
Let's invent #1 - we shouldn't move into Enterprise 2.0 because none of our competitors has
Thanks for the riff. Far more fun a topic than the one I chose :)
