On TV.com: PSYCH Is Canceled ? Sike!
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 2 of 18:
Next »
« Previous
Shift of emphasis
Projects of every type fail due to issues that arise when people collaborate. Agendas, information silos, politics and so on are part of every sphere of collaboration.

From that standpoint, there's nothing new under the sun here. At the same time, the specific mechanisms in how these problems manifest does change.

I think Dion did an admirable job, and has set the bar high, in identifying how those issues get expressed in the E20 context.

Cheers,
Michael
Posted by: mkrigsman@...   Posted on: 08/21/09 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Really?  Rotkapchen | 08/21/09
Shift of emphasis  mkrigsman@... ZDNet Moderator | 08/21/09
Some of these are certainly E2.0 specific failures  dionhinchcliffe ZDNet Moderator | 08/21/09
Really? Part Deux  Rotkapchen | 08/21/09
RE: 14 Reasons Why Enterprise 2.0 Projects Fail  fidelman | 08/23/09
RE: 14 Reasons Why Enterprise 2.0 Projects Fail  lee@... | 08/23/09
RE: 14 Reasons Why Enterprise 2.0 Projects Fail  schmediachick | 08/23/09
RE: 14 Reasons Why Enterprise 2.0 Projects Fail  schmediachick | 08/23/09
15. Inventing problems.  CobraA1 | 08/23/09
Top reasons ....  wackoae | 08/23/09
RE: 14 Reasons Why Enterprise 2.0 Projects Fail  Russ_h | 08/24/09
Why we rouge developers exist.  urlonz | 08/24/09
Why you have rouge developers!  urlonz | 08/24/09
Perhaps Enterprise 2.0 Is Not An App  ourfounder | 08/24/09
RE: 14 Reasons Why Enterprise 2.0 Projects Fail  matthewgreeley | 08/24/09
8 Tips for a Successful Enterprise 2.0 Pilot  thoughtfarmer | 08/26/09
Where to start?  Palmetto | 09/21/09
RE: 14 Reasons Why Enterprise 2.0 Projects Fail  ananiasacts | 10/01/09

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

SmartPlanet

Click Here