Yesterday I was fortunate to be the host of a really enlightening conversation on adoption issues related to enterprise 2.0 projects with Andrew McAfee, Euan Semple, Jenny Ambrozek, Jerry Bowles, and Jim McGee (you can listen to a replay of the event here). We had another session on Monday – but since we had some technical difficulties during that session the audio needs editing. I will write about that one when the audio is available.
One of the questions that crossed my mind is whether enterprise 2.0 tools (web 2.0 tools deployed within an enterprise environment) have the same barriers to adoption as traditional collaboration tools. One of the main barriers to adoption with collaboration tools is to not be able to get everyone who is working on a project to use the tools. This can happen for a variety of reasons – i.e., “the blank screen” syndrome, which happens when people do not quite know how to use the tools or organize their work within those tools, and revert back to email, face-to-face and phone instead of working within the specialized collaborative environment, or for cultural/political reasons, when people do not like the way the project is organized and boycott the use of the collaborative tools. In all those instances the value of the collaboration environment goes down to zero for all the other team members who want to use it. If some part of the work or the project lives outside of the project collaboration environment, then that environment has no more value than a person’s inbox – it is not complete.
Enterprise 2.0 tools on the other hand are less project-centric and a little more individual-people-centric, meaning that even if I am the only one who is using tagging or blogging on a project, that still has value to me. I am not sure that holds true for wikis, which are true collaborative environments.
Note that we also set up a Ning social networking group for Enterprise 2.0 Ravers – feel free to join and engage in that conversation as well.