Home | Biography | Contact | Speaking | Patents | Publications | Portfolio | My Blog

Barriers to Enterprise 2.0 Adoption

Here are a few barriers and issues related to Enterprise 2.0 adoption.

Awareness: Basic knowledge of the existence, availability, and reliability


  • Number of messages employees receive; information overload

  • Lack of knowledge and understanding of marketing

  • Mixed uses and multiple architecture products confuse everyone

  • Clear business value message and utility

  • Multiple products in the collaborative space

Education: Education and training on the product suite


  • Myth of easy to use and anyone can do it

  • Differences in business use versus personal use

  • Multiple methods of education; online, onsite, casting, and user guides

  • Need pattern libraries for multiple use case implementations

  • HR and legal issues must be addressed early

Political: Organizations choosing to reject based on group think


  • Major vendor prejudices like IBM, Microsoft and Open Source

  • Business or IT implementation control

  • Product architecture overlap; Document Management, Content Management, Intranet, Knowledge Management, Asynchronous Communications Tools

  • Policies and governance controls written for older technology

  • Organizational support like Executive Support

Cultural: Issues focusing around the organizations heritage


  • Hierarchy control of management; Command and Control

  • The level of employee empowerment

  • Influence of policies like RIM, Code of Conduct, etc.

  • Nature of the work where collaboration is essential

  • Sacred cows

Social: Issues that focus on the individual


  • Younger workforce emerging who expect these tools

  • Disparate employee base (Employee, Contractors, Consultant, Out-Sourced, Technical versus Non-Technical)

  • Contribution versus readership; higher percentages are required

  • Apathy and lethargy within the organization

  • Organizational trust

Technology: Technical issues or concerns


  • Tools and technology selection (Open Source, Suites, or Single Products)

  • Interoperability between tool selections (Search, Taxonomy, Data Exchange)

  • Reliability of the infrastructure

  • Extensibility of the environment; Can it Scale

  • Usability of the tools and the similarities between the tools

  • Serviceability of the physical environment

  • Data conversion or exchange to new tools

What others can you think of?


Comments (2)

Hi Todd. As usual, excellent work. Would you be interested in talking about these issues at the Office 2.0 conference in San Francisco? (Sept. 5-7)

Question-- are these based on your personal experience at AT&T, or have you included others' experiences here?


How profound� In 1985, these barriers obstructed information sharing across systems. I think the truth is this: what we're in is part of a larger complex dynamical system that�s universal to explaining effects on current events. 10-years from now, these same barriers will appear as the obstruction of something else � although slightly different, the list will re-appear.


Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Filed Under

Calendar

Fresh Ideas

Search


Subscribe to Feed
©2007 R. Todd Stephens, Ph.D. All rights reserved