WWW/Internet - Portal do Software Público Brasileiro

ISBN: 978-972-8939-25-0 © 2010 IADISdefinition, McAfee wants to identify a real philosophy that uses the concepts of the Web2.0 in order to renewthe enterprise standards not forcing the application of a hierarchical organization and of a strictly proceduralprocess. Today, the introduction in an organization of the E2.0 model is seen as the adoption of a newtechnology (through the use of a tool such as wiki, blog,.. ) [Chwelos, 2000] [Premkumar, 1995] and theproblems connected with the managing of the information or with the organization are not considered.Recovering this gap, this paper aims to define the adoption process of the Enterprise 2.0 model that couldbe used as guidelines by the company in order to minimize the risk of a complete change of enterprise workprocedure [ The Economist, 2007]. After this paragraph that introduces the context in the second paragraphwe explain the open issue and the problem to adopt the Enterprise 2.0 model into an organization. The thirdparagraph describes the process: first in general and then describing each phase. The conclusion describes theresearch result and the future works.2. THE ENTERPRISE 2.0 CHALLENGEAs stated before, the adoption inside an organization of the E2.0 paradigm is not a simple task because manytechnical and social issues must be solved. First of all, it’s necessary to consider that the employees have anatural aversion to any changes in their working manner. Thus, the possibility of the employees to work in acollaborative perspective through the publication of their know-how in a blog or a wiki could be dramatic.Not only the low level of collaboration and/or communication between the employees could be an obstaclebut also its higher level could cause several problems. Indeed, we have to consider that the opportunityoffered to the employees to insert their information [Newman, 2009] and to express their opinions involvesserious problems of governance related with the loss of know-how (information that is not correct andinaccurate) and with the loss of sensible data (reserved information broadcasted).From the technological point of view, even if the introduction of the Web2.0 tools in the enterprisesoftware architecture does not involve particular problems, these new collaborative features must beintegrated in the traditional information system. The traditional information systems are born and aredeveloped assuming the business process, including the operative processes, the management processes andthe collaborative processes in order to have a wide, integrated and pervasive control of the all enterpriseparameters . Clearly, the introduction of E2.0 that in a complete adoption must affect these processes in orderto promote the collaboration, must be related with the legacy system modernization . Furthermore, we haveto consider that the current information systems are strongly focused and strictly dependent from data andtheir structure. These systems must be adjusted to manage the de-structured information obtained, forexample, from a forum and blog; in fact, the goal of the Web2.0 tools is to prompt each employee to elicit (ina blog, wiki, forum) his/her know-how that must be indexed and make widely accessible. If the internalinformation system does not have a flexible infrastructure able to manage the not structured data, all thisknowledge will be lost and all benefits of E2.0 for the organization will be really poor.In the following, we report in general the main factors that affect the adoption of a complete E2.0paradigm [Massey, 2007] [Riche, 2007] [Lin, 2005] inside an organization:• Infrastructure factor [Frappaolo, 2008] [Duncan, 2009]. This factor is directly connected with theability and the will of the enterprise to renew own legacy system: the management has to take a firm decisionin the modernization process and must be allocated a good part of the innovation budget. In some case,hybrid architectural solution in which the legacy system manages the operative data and the Web2.0 systemmanages the not-structured knowledge, could be efficiently adopted.• Cultural factor [Holt, 2007]. This factor is related with the enterprise culture and with its inclinationto evolve its internal organizational structures to follow the E2.0 philosophy. A flexible organization will bemore able to use a flat structure and to use in an informal way the new available tools.• Environment factor [Premkumar, 2005]. The enterprise is a part of complex environment that is themarket with its rules and pressure. If the enterprise works in a market that is much competitive in whichcontinuous changes are required and the company is often forced to follow these changes, clearly the entireenterprise is directed towards a radical change such as the adoption of E2.0.Technological factor [Edison, 2000]. Unlike the infrastructure factor, this aspect underlines the capacityof the organization to innovate itself [Parasuraman, 2000]. If the employees are not accustomed to use ICTtools during their works, the introduction of E2.0 will be more difficult.314