Todos hemos escuchado hablar sobre Social Networks, Wiki, Blogs, etc; en fin cualquier expresión del Web 2.0 y los beneficios que se pueden obtener de estas.

Pero más allá del benéfico que puedan obtener los usuarios individuales hay una tendencia de querer aplicar algo de Web 2.0 en las empresas y obtener estos mismos beneficios; claro esto no es nuevo y ya muchas empresas lo han venido haciendo durante algún tiempo obteniendo muy buenos resultados y logros lo ha motivado que otras quieran implementarlo; lo que nos trae a la mesa el concepto de Enterprise 2.0

El concepto como tal ha llamado mucho la atención y a pesar de que muchas empresas no saben como iniciar o que tipo de experiencia web 2.0 podrían implementar. El día de hoy me encontré 7 recomendaciones para los que inician con esto o quieren hacerlo.

  1. Don’t be afraid to experiment. At its foundation, innovation is driven by a spirit of experimentation. I’ve long argued that the ‘traditional’ approaches to intranets (and other enterprise platforms) hasn’t been working, so we have everything to gain by trying some different ideas.
  2. Take a ‘safe-fail’ approach. Enterprise projects are very conservative, moving much more slowly than the wider world. To increase the pace of change, we need to take a ‘safe-fail’ approach, allowing a range of ideas to be tried with the expectation that some (perhaps most) will fail. The key is to have these failures to strengthen the strategy, not weaken it.
  3. Have a clear purpose. Enterprise 2.0 is just a means to an end. We need to have clear business goals and end-user benefits driving our projects, beyond fuzzy ideas of ‘knowledge sharing’ or ‘creating a collaborative culture’.
  4. Take it seriously. Don’t just ‘roll out’ a solution and hope for the best. We need to make every effort to have these new approaches succeed, including creating usable tools, and establishing good communications, marketing, training and support.
  5. Make it work now. There is a remarkable consensus on what future directions should be, and how things might look in the longer term. Our projects, however, cannot just plan for the future. If staff don’t use our solutions in the short-term, there won’t be a long term (for us or our projects).
  6. Match the culture. Technology can, to some degree, change the culture of an organisation. More realistically however, our projects should match the current culture to give the best chances of success. We shouldn’t be trying to deploy solutions that staff or the organisation as a whole aren’t ready for.
  7. Build on the experiences of others. The early adopters have blazed at least some of the trails ahead, and we should build on their experiences. This allows us to avoid ‘reinventing the wheel’, or deploying solutions that are founded solely on idealism.” Source

No es la panacea por supuesto ni tampoco ofrece una metodología concreta, pero es un muy buen inicio.


Ferglo clip_image002 clip_image004 clip_image006 clip_image008