ooh diagrams
sometime the void, always elegantly represented

this is Gino's profile

Gino Tocchetti




tumblr posts
(commenti ? usa friendfeed ;-))

I miei momenti di serendipita':

Triveneto visto da nord
Le mie conversazioni:

friendfeed

Twitter: metakappa

Le mie rielaborazioni:

The Knowledge Ecosystem: my blog


Questo blog non è una testata giornalistica, in quanto viene aggiornato senza nessun tipo di periodicità predefinita. Pertanto, non può essere considerato un prodotto editoriale, ai sensi della legge 62 del 7 marzo 2001. Le immagini inserite in questo blog sono tratte in massima parte da Internet; alcuni post sono effetto di reblogging; qualora la loro pubblicazione violasse eventuali diritti d'autore, vogliate comunicarlo all'autore.

Archive

Aug
23rd
Sun
permalink
pedroelrey:

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

pedroelrey:

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