The Boston version of the Enterprise 2.0 conference was over 5 weeks ago however there is still a lot of great Social Computing and Professional Collaboration information that is being shared on a weekly basis. I came across a number of first person interviews from the Enterprise 2.0 Conference that I thought was worth sharing. Level 3 produced 15 different interviews from both Enterprise 2.0 participants and speakers that are worth listening to. The Level 3 site is called The Red Couch and includes interviews from many conferences. All of the Enterprise 2.0 interviews were great but I really enjoyed these four:
- Steve Wylie from Tech-Web and Enterprise 2.0 Conference
- Dion Hinchcliffe from ZDNet and Dion Hinchcliffe and Company
- Mike Gotta from the Burton Group
- Oliver Marks from Oliver Marks and Company
In the weeks after the Enterprise 2.0 conference, a nice little community has formed to discuss 3686954681_b17c8aff6a_oEnterprise 2.0, Social Computing and 2.0 Adoption issues. The group, started and managed by the ITSinsider – Susan Scrupski is called The 2.0 Adoption Council and has participants on Linkedin, Facebook, Socialcast and Jive. The Linkedin group has moved to Socialcast and Jive however if you are interested in participating in this discussion, join the Linkedin or Facebook 2.0 Adoption Council groups and let us know that you are interested, or you can message me on twitter at @kmullins.
In the middle of this 2.0 adoption discussion, Dion Hinchcliffe wrote an insightful post today about the Top Ten Issues in Adopting Enterprise Social Computing where he identified a list of 10 issues that impact the adoption of Social Computing in the Enterprise.
Here is the list:
- Lack of social media literacy amongst workers.
- A perception that social tools won’t work well in a particular industry.
- Social software is still perceived as too risky to use for core business activities.
- Can’t get enough senior executives engaged with social tools.
- There is vapor lock between IT and the social computing initiative.
- Need to prove ROI before there will be support for social software.
- Security concerns are holding up pilot projects/adoption plans.
- The needs around community management have come as a surprise.
- Difficulties sustaining external engagement.
- Struggling to survive due to unexpected success.
and you can read Dion’s complete post and analysis on ZDNet’s Enterprise Web 2.0 blog.