Enterprise2.0 er et konsept som ble etablert av Harvardprofessor Andrew McAfee. Han beskriver enterprise2.0 som virksomheter som bruker sosiale nettgjenester som plattform for å kommunisere internt og mellom selskaper, deres partnere og kunder.
På sett og vis er derfor enterprise2.0 prototypen på organisasjoner i det digitale nettsamfunnet. Disse organisasjonene utnytter at det er mulig å slippe og installere en rekke applikasjoner på egne servere for å understøtte organisasjonens arbeid, men heller gjør bruk av ulike plattformtjenester.
Nå har konseptet modnet, etter som det er blitt mer vanlig å bruke wiki og blogger, og sosiale nettverkstjenester som Facebook er så stuerent at mer enn 1,5 millioner nordmenn er i fjesbokhylla.
Her er 6 råd for deg som vil implementere enterprise2.0 i egen organisasjon (langt utdrag av artikkelen).
1. The transformation to a bottom-up culture needs help from the top. Web 2.0 projects often are seen as grassroots experiments, and leaders sometimes believe the technologies will be adopted without management intervention—a “build it and they will come” philosophy. These business leaders are correct in thinking that participatory technologies are founded upon bottom-up involvement from frontline staffers and that this pattern is fundamentally different from the rollout of ERP systems, for example, where compliance with rules is mandatory. Successful participation, however, requires not only grassroots activity but also a different leadership approach: senior executives often become role models and lead through informal channels.
At Lockheed Martin, for instance, a direct report to the CIO championed the use of blogs and wikis when they were introduced. The executive evangelized the benefits of Web 2.0 technologies to other senior leaders and acted as a role model by establishing his own blog. He set goals for adoption across the organization, as well as for the volume of contributions. The result was widespread acceptance and collaboration across the company’s divisions.
2. The best uses come from users—but they require help to scale. In earlier IT campaigns, identifying and prioritizing the applications that would generate the greatest business value was relatively easy. These applications focused primarily on improving the effectiveness and efficiency of known business processes within functional silos (for example, supply-chain-management software to improve coordination across the network). By contrast, our research shows the applications that drive the most value through participatory technologies often aren’t those that management expects.
Efforts go awry when organizations try to dictate their preferred uses of the technologies—a strategy that fits applications designed specifically to improve the performance of known processes—rather than observing what works and then scaling it up. When management chooses the wrong uses, organizations often don’t regroup by switching to applications that might be successful. One global technology player, for example, introduced a collection of participatory tools that management judged would help the company’s new hires quickly get up to speed in their jobs. The intended use never caught on, but people in the company’s recruiting staff began using the tools to share recruiting tips and pass along information about specific candidates and their qualifications. The company, however, has yet to scale up this successful, albeit unintended, use.
At AT&T, it was frontline staffers who found the best use for a participatory technology—in this case, using Web 2.0 for collaborative project management. Rather than dictating the use, management broadened participation by supporting an awareness campaign to seed further experimentation. Over a 12-month period, the use of the technology rose to 95 percent of employees, from 65 percent.
3. What’s in the workflow is what gets used. Perhaps because of the novelty of Web 2.0 initiatives, they’re often considered separate from mainstream work. Earlier generations of technologies, by contrast, often explicitly replaced the tools employees used to accomplish tasks. Thus, using Web 2.0 and participating in online work communities often becomes just another “to do” on an already crowded list of tasks.
Participatory technologies have the highest chance of success when incorporated into a user’s daily workflow. The importance of this principle is sometimes masked by short-term success when technologies are unveiled with great fanfare; with the excitement of the launch, contributions seem to flourish. As normal daily workloads pile up, however, the energy and attention surrounding the rollout decline, as does participation. One professional-services firm introduced a wiki-based knowledge-management system, to which employees were expected to contribute, in addition to their daily tasks. Immediately following the launch, a group of enthusiasts used the wikis vigorously, but as time passed they gave the effort less personal time—outside their daily workflow—and participation levels fell.
Google is an instructive case to the contrary. It has modified the way work is typically done and has made Web tools relevant to how employees actually do their jobs. The company’s engineers use blogs and wikis as core tools for reporting on the progress of their work. Managers stay abreast of their progress and provide direction by using tools that make it easy to mine data on workflows. Engineers are better able to coordinate work with one another and can request or provide backup help when needed. The easily accessible project data allows senior managers to allocate resources to the most important and time-sensitive projects.
Pixar moved in a similar direction when it upgraded a Web 2.0 tool that didn’t quite mesh with the way animators did their jobs. The company started with basic text-based wikis to share information about films in production and to document meeting notes. That was unsatisfactory, since collaborative problem solving at the studio works best when animators, software engineers, managers, and directors analyze and discuss real clips and frames from a movie.4 Once Pixar built video into the wikis, their quality improved as critiques became more relevant. The efficiency of the project groups increased as well.
4. Appeal to the participants’ egos and needs—not just their wallets. Traditional management incentives aren’t particularly useful for encouraging participation.5 Earlier technology adoptions could be guided readily with techniques such as management by objectives, as well as standardized bonus pay or individual feedback. The failure of employees to use a mandated application would affect their performance metrics and reviews. These methods tend to fall short when applied to unlocking participation. In one failed attempt, a leading Web company set performance evaluation criteria that included the frequency of postings on the company’s newly launched wiki. While individuals were posting enough entries to meet the benchmarks, the contributions were generally of low quality. Similarly, a professional-services firm tried to use steady management pressure to get individuals to post on wikis. Participation increased when managers doled out frequent feedback but never reached self-sustaining levels.
A more effective approach plays to the Web’s ethos and the participants’ desire for recognition: bolstering the reputation of participants in relevant communities, rewarding enthusiasm, or acknowledging the quality and usefulness of contributions. ArcelorMittal, for instance, found that when prizes for contributions were handed out at prominent company meetings, employees submitted many more ideas for business improvements than they did when the awards were given in less-public forums.
5. The right solution comes from the right participants. Targeting users who can create a critical mass for participation as well as add value is another key to success. With an ERP rollout, the process is straightforward: a company simply identifies the number of installations (or “seats”) it needs to buy for functions such as purchasing or finance and accounting. With participatory technologies, it’s far from obvious which individuals will be the best participants. Without the right base, efforts are often ineffective. A pharmaceutical company tried to generate new product ideas by tapping suggestions from visitors to its corporate Web site. It soon discovered that most of them had neither the skills nor the knowledge to make meaningful contributions, so the quality of the ideas was very low.
To select users who will help drive a self-sustaining effort (often enthusiastic early technology adopters who have rich personal networks and will thus share knowledge and exchange ideas), a thoughtful approach is required. When P&G introduced wikis and blogs to foster collaboration among its workgroups, the company targeted technology-savvy and respected opinion leaders within the organization. Some of these people ranked high in the corporate hierarchy, while others were influential scientists or employees to whom other colleagues would turn for advice or other assistance.
When Best Buy experimented with internal information markets, the goal was to ensure that participation helped to create value. In these markets, employees place bets on business outcomes, such as sales forecasts.6 To improve the chances of success, Best Buy cast its net widely, going beyond in-house forecasting experts; it also sought out participants with a more diverse base of operational knowledge who could apply independent judgment to the prediction markets. The resulting forecasts were more accurate than those produced by the company’s experts.
6. Balance the top-down and self-management of risk. A common reason for failed participation is discomfort with it, or even fear. In some cases, the lack of management control over the self-organizing nature and power of dissent is the issue. In others, it’s the potential repercussions of content—through blogs, social networks, and other venues—that is detrimental to the company. Numerous executives we interviewed said that participatory initiatives had been stalled by legal and HR concerns. These risks differ markedly from those of previous technology adoptions, where the chief downside was high costs and poor execution.
Companies often have difficulty maintaining the right balance of freedom and control. Some organizations, trying to accommodate new Web standards, have adopted total laissez-faire policies, eschewing even basic controls that screen out inappropriate postings. In some cases, these organizations have been burned.
En annen interessant side ved artikkelen er at forfatterne ønsker å skape diskusjon om innholdet, ikke i neste utgave av magasinet, men på Twitter. Les nederst i artikkelen og delta i diskusjonen.