21 Risks in not adopting Enterprise 2.0

Dion Hinchcliffe identified some reasons why Enterprise 2.0 projects can fail.  As with any IT project, failure is statistically an option even without bringing Web 2.0 into the equation.  The second common cause of failure was the bottom up failure of adoption .  I think a bigger risk is that companies fail to understand changes that are happening in the work place and society, and don’t react in a proactive way.   There is significant risk in failing to acknowledge Web 2.0 as a major tool in business administration.  Hopefully I will find some companies who have failed to identify this risk and can add their details at a later date

• Graduates and young employees perceive the company as old fashioned and competitors attract talented, younger staff
• Costs increase as a company is restrictively aligned with Microsoft or Apple products
• Inefficient practices of emailing pdf or word documents continues
• Time in checking emails results in reduced productivity
• Reduced moral due to old work practices and the company not keeping up the pace of change
• The water cooler news is not transformed to an online experience
• Restrictions in communication and collaboration due to a global workforce and community, and inefficient practices
• Inability to find relevant company information due to old file systems
• Reputation amongst customers and suppliers
• Inability to engage in two way dialogue with customers, and possibly build goodwill
• Restricted ability to communicate and market to customers
• Inability to conduct relevant competitor analysis
• Inability to rapidly respond to aggrieved customers
• Restricted ability to operate remotely or in a mobile environment
• Unexpected outcomes associated with adopting new technology may not occur
• Potential customers may not be aware of the company – Customers may develop a positive attitude without actually purchasing products, or interacting with staff
• The static web site does not adequately portray the company, staff and its vision
• The company may be getting an ineffective return on marketing dollars spent in print or other media
• Delayed communication to customers due to old practices
• Many customers will form an online opinion, whether you are there or not – it is better to positively guide this experience
• Many Web 2.0 tools are open source, and cheaper to maintain and initiate

Hinchcliffe summed up the challenges in implementing Enterprise 2.0 with “Creating and nurturing a community and keeping it thriving is not something that a project plan alone can achieve or that the traditional stakeholders in software projects are often skilled at. It takes diligence, patience, engagement, emotional intelligence, and understanding of the needs and motivations of participants to be successful for the long term.”  I think there are greater risks with no adoption.