Why Enterprise 2.0 projects fail
Dion Hinchcliffe’s excellent list of reasons for why Enterprise 2.0 projects fail has been extended by James Dellow’s reference to four key rules of thumb for avoiding Enterprise 2.0 project failure.
James raises the valid point that unlike social software implementations of the past, knowledge workers today are more familiar with social networking technologies. This factor alone should contribute to the likelihood of E2.0 adoption.
So extending upon this, James has raised these four key rules of thumb for avoiding Enterprise 2.0 project failure:
* Use real social computing platforms
* Take an abundance approach to the technology
* Put the ‘users’ in the driving seat
* Tap into your pool of early adopters
Combine Dion’s considered list and the above key drivers and Enterprise 2.0 project success will be one step closer!