Implementing Enterprise 2.0 technologies and approaches can be a key driver of competitiveness and profitability.
However since Enterprise 2.0 sits at the nexus of technology and organizational culture, there can be no one-size-fits-all approach.
Implementing Enterprise 2.0 Report provides detailed practical insights into how to create substantial business value with web technologies, supported by numerous case studies of successful implementation and lessons learned.
Enterprise2Blog partner Ross Dawson has written a comprehensive report on Implementing Enterprise 2.0 and published free chapters for your education.
Use this report to:
Gain a clear understanding of Enterprise 2.0 and Web 2.0 in organizations
Identify opportunities for value creation
Provide a structured view of benefits and risks
Establish governance initiatives
Create and communicate a clear Enterprise 2.0 strategy for your organization
GetSatisfaction is an interesting new approach to leveraging the power of the Web for fun (and maybe profit)? The idea is to create an open market place for customer support. Got a question about a particular company or product? Go to http://getsatisfaction.com/, enter your question, and hopefully within a few minutes you get a response via e-mail from someone in that company. There’s a pretty compelling business model there if you can leverage this sort of service to reduce calls to your contact centers. There’s also some interesting opportunities to meld this service with microblogging services such as Twitter.
One of the key ways that UC can benefit an organization is by reducing human latency. The idea is that if you can shorten the time it takes people to find the subject matter experts that they need to solve a particular problem, you can achieve demonstrable benefits such as increased sales, increased customer retention, or greater efficiency of contact center operations.
Most vendors here at VoiceCon San Francisco are spending a lot of time talking up UC as a way to reduce human latency, but few are saying “how” you classify and identify subject matter experts. Typically you hear discussions around grouping people by role, but what is missing is the merging of social computing and UC so that your employees (and perhaps even customers & partners) can self-identify experts based on concepts such as tagging or rating user profiles. It’s not hard to see how a company can integrate something like Lotus Connections or Microsoft SharePoint with Teligent Community server to let your users create the knowledge base that allows individuals to find the experts they need for a given problem.
As companies deploy (or simply allow) Web 2.0 tools in their organizations, they often forget the need for enterprise content management. But as employees use and contribute to wikis, blogs and social networking tools, they create a lot of content–and that content needs to be secured, compliant, and accessible to others within the organization. For more on this topic, check out this podcast, and post your comments below.
First, here are the links (the ones I could find; there may be others more than 1 degree away. A couple of them are repeated, since the authors seem to have posted the same reaction on more than one blog, but I am posting the repeats here in case they’ve developed different comment threads).
Steve’s comments below got me thinking about why we don’t just accept information overload, but actually ask for it.
There was plenty of chatter in the blogs this weekend over the decision by the Obama campaign to text its supporters news of the VP pick as soon as it happened (well, as soon as the campaign was ready to release it). Most of it seemed centered around (1) the timing of the text’s release (another 3am brouhaha), (2) the “next-gen Internet outreach” approach, and (3) the pick himself. Mainly lost in the discussion was whether anyone really needed to know the information in real time, on their cells and PDAs.
Googles Knol is now live. Knol is part wiki, part blog, and part social computing platform though it is most often being compared with Wikipedia. Essentially Knol is an information repository, but where it differs from Wikipedia is that knols, or pieces of knowledge, require a verified author. The idea being that a reader is likely to find an article on say "macro-economics in Macedonia more authorititive if it is written by a verifiable subject matter expert, than if it is anonymously compiled ala Wikipedia.
As blogging moves into the enterprise, one of the biggest questions managers face is whether to monitor the sites, and if so, how much. They can look to the consumer world for cues. Personal blogs (one person sharing his thoughts on his life, or perhaps a more specific topic) are monitored by the blogger directly; since the blogger isnt representing anyone else, let alone an organization, he isnt answerable to anyone but himself and can choose to allow or disallow comments as he see fit. The issue gets more interesting when we look at media sitesnewspapers, magazines and the likethat allow readers to post comments to articles and posts. Continue Reading »
Irecently learned of an interesting tool for schools and their students, called Web Lockers. According to the vendor, students “can use the lockers to upload homework assignments and projects, send and receive assignments, view graded work, and communicate with teachers and classmates outside of the classroom. For added collaboration, School Web Lockers also provides teacher blogs and message boards (for school-wide or even district-wide online discussions.)”
The Enterprise 2.0 Blog is affiliated with the Enterprise 2.0 Conference, an event focusing on social tools and technologies that help make companies more creative, agile and productive.