14 Reasons Why Enterprise 2.0 Projects Fail: - It starts strong in a single department and then never makes it out - Selecting the tools first - Selecting the wrong tools and sticking with them - There are no resources allocated to adoption and training - It’s purely an IT initiative - The effort excludes IT - Engaging with HR, legal, branding, compliance, etc. too soon - Pushing Enterprise 2.0 as a generic toolbox instead of the solution to specific problems - Lack of effective executive champions - Lack of effective participants: Empty blogs, wikis, or silent social networks - No long term plan or budget for governance, community management, upgrades, or maintenance - Failure to draw in key influencers as adoption broadens - Building it all as a self-contained, top-down effort - Not waiting long enough to let critical mass build

14 Reasons Why Enterprise 2.0 Projects Fail: - It starts strong in a single department and then never makes it out - Selecting the tools first - Selecting the wrong tools and sticking with them - There are no resources allocated to adoption and training - It’s purely an IT initiative - The effort excludes IT - Engaging with HR, legal, branding, compliance, etc. too soon - Pushing Enterprise 2.0 as a generic toolbox instead of the solution to specific problems - Lack of effective executive champions - Lack of effective participants: Empty blogs, wikis, or silent social networks - No long term plan or budget for governance, community management, upgrades, or maintenance - Failure to draw in key influencers as adoption broadens - Building it all as a self-contained, top-down effort - Not waiting long enough to let critical mass build

1 nota
Notes
  1. oohdiagrams ha rebloggato questo post da pedroelrey
  2. postato da pedroelrey

other news is designed by manasto jones, powered by tumblr and best viewed with safari.