This is part two of opening workshop by Dion Hinchcliffe on Implementing Enterprise 2.0 at the Boston Enterprise 2.0 conference. Dion brought up a guest speaker David Stephenson who he said is the “world’s leader in democratizing data.” This was the tile of his discussion, the concept of democratizing data: the data-centric organization. This makes it automatically available to those who need it based on roles and responsibilities while maximizing security. He said that data democratization can actually increase security. I agree here.
Having data at the heart of all actions is an attitudinal shift. You need to provide metadata so you can make sense of it and RSS feeds to reach user. You need to think of every worker as a knowledge worker. Giving more authority to people who fill potholes by providing them with all the data on their daily assignments increases morale and productivity as they will know the best way to complete the tasks. David said that the Netherlands government saves over 25% of reporting costs by standardizing and making data more transparent.
Dion can back and picked up on this theme. Government is picking up on the data democratization theme with the new administration. For example, wikis are being used for dealing with crisis issues for more transparency than email.
Dion reviewed enterprise 2.0 platforms; wikis, blogs, microblogging, mashups, online communities, social bookmarking, social networking and them went over the vendor space with examples of each category. There is currently no one stop shop for all tool categories but there are suites. Online communities include: Joomla, Drupal, Zikula, PHP/Nuke SharePoint, Lithium, Telligent, DotNetNuke, KickApps, Jive. Dion said these are the top ones based on usage. SharePoint is already available in many organizations that want to start enterprise 2.0. It has many necessary capabilities. It can also be adapted to implement many of the social emergent tools but usually requires some work.
Dion put up an enterprise 2.0 ecosystem chart. You have traditional enterprise systems and enterprise 2.0 systems. These can be connected through mashups and data can be found through federated search. He went on to cover some other platforms being used: Igloo, Facebook private groups (it is open source). Serena software uses Facebook (see my post - Serena has Adopted Facebook as their Intranet).
Mashups are being used and Serena, Jackbe, IBM (Lotus Mashups), Microsoft (Popfly) have tools. One creative example, Chicago did a mashup of crime data with Google Maps that is updated real time and can be sorted by time of day.
Crowdsourcing is another application. One gold company put their survey data out and invited anyone to tell them where the gold was. They had great success and paid a large sum in bounties. This can be done internally or externally. (see Innovating Through Market Games with Spigit.)
Dion then switched to best practices. Successful adoption strategies include: gain and enlist top down support, overcome turf issues in advance, align applications to key business processes, align enterprise 2.0 strategy to business strategy, develop a clear simple business case, provide strong leadership, design measure aligned to business processes. I could not agree more. These were also all the key adoption strategies for knowledge management in the early 90s. This does not take away from them. I think it just reinforces them. Dion said these factors came from actual case studies.
He added more adoption strategies: listen to users, simply the access and production of knowledge, develop a clear communication plan to promote the effort, involve all key stakeholers (but go slow on this), integrate all forms of communication, develop a clear motivation plan. Again these are all best practices from knowledge management in the early 90 but I see this as a further validation. I found that legal often got overlooked and this can come back to bite you so do not leave them out.
Dion went on to discuss the need to aggregate social data and not have silos. This is critical. Enterprise 2.0 suites are adding this. Also, social analytics is being implemented to take advantage of the transparency and make sense of it. He gave an example of Facebooks’ FriendWheel as a consumer version. In line with this you need to cultivate weak ties, as well as strong ties, and enterprise 2.0 enables this. These weak ties are often the source of new insights vs. the people you talk to all the time.
Reputation systems are another way to make use of the social data and rather input. Sezwho is one tool that works across platforms. Expertise location is an overlapping capability.
Dion offered a breakdown of effort: tools, 15%, integration, 25%, community management 25%, IT support, 15% change management 20%. These make intuitive sense. Do not short change the people issues. The quality of the community management team is a critical success factor. Community Manager is one of the roles in the enterprise.
You need to allow time for people to learn the tools and methods. Social tools are the new productivity tools like word processing and spreadsheets before so everyone needs to learn how to use them. As Dion said earlier, the more people use the tools the greater the value. There are three levels of community in the enterprise and you need to deal with each one: team level, community level, and entire network.
I found this workshop to be a useful overview of enterprise 2.0 adoption.
Thanks for the comment
Posted by: dizi izle | November 21, 2009 at 10:56 AM