Skip to main content

Diigo Home

Potential Pitfalls in Enterprise 2.0 - The Diigo Meta page

www.bluethots.com/...tial-pitfalls-in-enterprise-20 - Cached - Annotated View

Bertrand Duperrin's personal annotations on this page

bertrandduperrin
Bertrandduperrin bookmarked on 2009-02-21 enterprise2.0 socialnetworking privatelife problems sharing collaboration risk trust

First of all, let me recap some of the key fundamentals of Enterprise 2.0 - social networking with friends, colleagues and business partners, collaboration on job specific tasks (possibly on the same platform), sharing and trusting people in the network. So what are the potential problems people might face?

  • The problem of work life balance comes into play. Without control, for example, someone might be responding to emails on their honeymoon because a server crash and he saw a SOS on the wiki. We can’t be working all the time. We need to know when to stop.
  • However, some teams can never decide on the proper cause of action or agree on certain things.
  • Sharing - free rider problem will always be a problem. “Free riders” are those who consume more than their fair share of a resource, or shoulder less than a fair share of the costs of its production.
  • Trust - when one join a social community and put trust in their network, its like opening the front door of your house to the people in the neighbourhood.

This link has been bookmarked by 1 people . It was first bookmarked on 21 Feb 2009, by Bertrand Duperrin.

  • 21 Feb 09
    bertrandduperrin
    Bertrand Duperrin

    First of all, let me recap some of the key fundamentals of Enterprise 2.0 - social networking with friends, colleagues and business partners, collaboration on job specific tasks (possibly on the same platform), sharing and trusting people in the network. So what are the potential problems people might face?

    enterprise2.0 socialnetworking privatelife problems sharing collaboration risk trust

    • The problem of work life balance comes into play. Without control, for example, someone might be responding to emails on their honeymoon because a server crash and he saw a SOS on the wiki. We can’t be working all the time. We need to know when to stop.
    • However, some teams can never decide on the proper cause of action or agree on certain things.
    • 2 more annotations...