Hello guys, it is good to see you guys again here! In this week’s post , I will be introducing the benefits and risks of Enterprise 2.0 implementation using case study AT&T . However, not every single benefit and risk are covered, I will just point out the really useful ones to help me explain the whole concept of how Enterprise2.0 can be both beneficial and harmful.
Initial response or demand was weak in that people didn’t really understand the need back in 2003. For over a year, the implementation struggled to get traction but when it did; demand sky rocketed. Collaborative spaces, meeting spaces, web conferencing and shared document spaces started movement. As with many implementations, it’s the small value add components that add up with volume. Sharepoint is considered the tool not really a product. Products are what you can do with the tool. Additional products and services were added as the implementation progressed. Services like search, PDF creation, and vanity URL are just a few add on services. The entire customer experience was reviewed from the initial knowledge that the tool existed to the killing of a decaying collaborative site. The goal was to create a single customer experience model that could be scaled as the user base grew from 100 to 60,000.
Today, a new set of tools are being added including blogs, wikis, professional profiles, and many others. While some are inside the Sharepoint offering, many will be provided through development and open source. As we progress, the key will be to bring all of these tools together into a single offering for many-to-many communications. Cost transformation and business speed are the two principle problems being addressed with the portfolio.
Enterprise 2.0 solution
The case study picks up after two years of implementation with little adoption by the business and technology communities. In 2004, another group with experience in deploying mass adoption software was brought in and asked to take this application to the scale defined by “mass adoption”. The main metric of progression will be the collaborative site count. Teams, group, and individuals can order a collaborative site which allows for group communication. At the time of only 100 collaborative sites had been built. This is similar to the five other implementations seen by the author. After implementing the core business model described below, the site count has increased to around 13,000 with around 3.5 Million page views per month. The number of document objects stored within the collaborative solution is over a million. Social Software is considered a subset of Collaborative Solutions and this group has now picked up the Social Software rollout deployed at the enterprise level.
The enterprise solution is actually a portfolio of solutions built on top of vendor products and open source. Microsoft’s Sharepoint and MOSS provide the core collaborative solution set. Confluence Wiki Software was also purchased for the Enterprise Wiki and various Open Source solutions provide the additional enterprise social software (Drupal, Roller, etc.)
- Over 37,000 Collaborative Sites growing at 124%
- Over 4 Million Documents Housed and Managed
- User Awareness of 98% of Total Population
- Average 8 Million Page View per Month
- Intranet Replacement
- Documented Reduction of Staff (Web Developers)
- Servers Retired (Cost Transformation)
- Speed of Business and Decision Making
However, there are still disadvantages of using Enterprise 2.0. Throughout my research I found out Enterprise 2.0 can do damage because of:
- Spread of rumours (Rapidly).
- False information .
- No long term plan or budget.
- Security Issues
Thank you all for attention! See you guys next week.