Web 2.0 applications are generally from the perspective of Web 2.0-enabling test based on two factors individualization and interactivity to their "participatory potential." In the organizational Context, the two concepts as self-determination and self-tuning are described. It can be seen from the graph that can meet because of various design features, not all applications both criteria equally. Individualization and self-determination lead to autonomy and sovereignty and is on personal blogs or asynchronous communication, as part of the Instant Messaging or the micro-blogging is the case, much higher than for example in corporate blogs. Interactivity and self-tuning on the other hand promotes use of "collective intelligence" of the problem-solving and decision making. Examples are team wikis or social software platforms which can limit the content and timing trade-offs as a result of the collaborative creation of content with autonomy.
Enterprise 2.0 (or Web 2.0) applications are diverse, often associated with novel functionality. It is therefore not surprising that the company first experimented with, or an isolated solution is created. According to the study Enterprise 2.0 2010 by Centrestage are wikis and blogs, followed by electronic communities that are primarily used Web 2.0 applications for the realization of Enterprise 2.0. It can, however, from case studies do not explicitly recognize, that wikis and blogs are also largely responsible for the process of introducing Enterprise 2.0. Just because they are now in almost every company in the main are interested or already occurring, this is not evidence that an implementation process to be initiated with wikis or blogs necessarily need. Micro blogging and social tools to share and evaluate information (eg Social bookmarking services) are among the new favorites, and Enterprise 2.0 in the mean time a distribution such as podcasts and video solutions achieved.
particularly advanced in the use of wikis is Sun Microsystems . There are Wikis as a tool for knowledge and software development processes used either in the form of several smaller internal wikis or in the central enterprise under the name of enterprise wiki Confluence. Meanwhile, first experiments show semantic wikis, a system that automatically produces relations between systems. The PSI uses the open source MediaWiki software as a technical basis of the Group-wide intranet for easy networking and ease of use of content and the elegant (full text) search for articles and topics. In DB Training is the Wiki system as the basis for linking various objects of knowledge based on the principle the self-assembly used to enable faster development of topics, documents, proposals and studies. Nokia wiki uses one for projects, for example, to pool information and input from stakeholders. On the other hand there is the Nokia Infopedia, with various information about products, solutions, organizational change initiatives, pricing, strategies, marketing initiatives, etc. Also, the mobile aspect is again taken into account by the possibility of a Wiki-use exists on mobile phones.
A comprehensive blog system offers Core Media in the form of a conversation platform where managers, employees, customers and partners can have their say and to actively contribute to the enrichment of knowledge in the company. Siemens uses an open source multi-blog, which is seen as bottom-up tool for knowledge management by contributions and comments on topics such as productivity gains and innovations are written. But also provides for simple events, events or personal stories, as well as for example in the corporate blog of Daimler , blogs can be used. A special form of the use of wikis and blogs Cablecom that both applications to a have merged so-called "Bliki". This "Bliki" with the name is eTouch the new IntraWeb 2.0 Cablecom is, are the employees connected disciplines, regardless of location and level of hierarchy with each other. The example of HP with his water cooler concept shows the increasing spread of parallel use social software applications.
Overall we can say that the field of Web 2.0 applications has become very dynamic and regularly get several tools and technologies used in parallel. In the relative frequency of use of wikis and blogs shows that they are already widely discussed in the company to discuss deployment scenarios, useful at which point the use of these two applications or is worthwhile. The problem is that constantly meet new innovative technologies and applications emerge and, thus, different generations of Web 2.0. The companies are often not able to take account of this fast pace, although at least the wikis and blogs from the crowd gradually understood quite well and used. As can be seen also from the examples, are wikis and blogs as good as in any business now a daily occurrence and are usually the oldest used applications dar.
recommendation: one, the intensive education of the employees on the workings of an Enterprise 2.0 tool to a successful launch. If the Enterprise 2.0 tool helps to solve an existing problem, the employees learn to use it naturally. It is important to note that the use of Enterprise 2.0 tools is generation dependent. Customized on-and offline training programs are necessary so that the Enterprise 2.0 tools can be used in wider form. The various Enterprise 2.0 tools are often compete with each other. Therefore, one must be clear which tools you want to use for any purpose and the objectives to be achieved with them in an Enterprise 2.0 initiative. The selected Enterprise 2.0 tools must be clarified. In the medium can also regulations on the Avoid redundancies and duplication of information and functions are necessary ("Single Source of Information"). At the beginning of an Enterprise 2.0 implementation of redundancy and duplication are more of a luxury problem. The focus of this issue should be to make the tools and their use simple and understandable. Duplication of tools due to non-unique mapping functions would be counterproductive.
