Corporate Web2.0 2009.04.26 Final Version
More and more organizations are getting on the Corporate Web 2.0 bandwagon and seeking ways to transform their Corporate 1.0 cultures with various social media tools to create collaboration inside their businesses. The web 2.0 tools outlined below -- blogs, wikis, social networks -- have been used successfully by many companies to facilitate communication, secure information sharing, interoperability, and collaboration. Lessons learned are illustrated through three case studies of our own corporations (although names are scrubbed). Companies are seeking to move away from their web 1.0 command-and-control ways -- where information flow is primarily one-way, concerned with top-down information control, and using websites built of static pages with 'read-only' material. Knowledge 1.0 is a problem because it lets employees create alone. It locks information in private silos. The 1.0 model forces knowledge into limited locations, workers into limited roles, inside a wall, stuck at a desk (and stuck using email and other standard tools) using rigid ways of organizing information. By unleashing the Knowledge 2.0 model with social media tools, companies put users in control of content so that critical knowledge can be quickly captured and archived, expertise shared faster, knowledge scaled quicker, information found more easily, and accuracy maintained through peer interaction.
Recommended
Recommended
More Related Content
More from Alan Belniak
More from Alan Belniak (11)
Recently uploaded
Recently uploaded (20)
Corporate Web2.0 2009.04.26 Final Version
- 1. corporate eb2.0 enterprise blogs Liz DiTucci enterprise wikis Katrina Gosek enterprise social networks Alan Belniak
- 2. using social media to create collaboration inside your business
- 5. html static websites mail messaging search + instant browse corporate content web ortals forums
- 6. knowledge 1.0
- 7. nowledge2.0
- 8. business2.0 goals capture + ARCHIVE critical info share expertise faster scalable knowledge base > obtain, negotiate + agree quickly > make info easier to find
- 9. to be true? oo good
- 10. advice
- 11. enterprise blogs Liz DiTucci enterprise wikis Katrina Gosek enterprise social networks Alan Belniak
- 13. Internal blogs • Easy to deploy and operate • Two way communication • Proprietary info • Learn, get feet wet • Ease into external blogging
- 19. enterprise wikis What are they? Collection of web pages, designed to enable anyone with access to modify content using simple html editors. How are they used? Collaboration and documentation.
- 20. groupmemory 1. simplified collaboration 2. aggregator of related info 3. accuracy through peer review 4. every page revision is saved 5. roll-back changes with a click
- 23. archiving knowledge “let’s hope <name> doesn’t get hit by a bus.”
- 24. We needed a better information transfer process and knowledge storage tool
- 26. 1. WYSIWYG Editor – no markup language 2. Named users and single Marketing Workspace signon 3. Ability to access outside office network 4. Full-test search, including attachments 5. Email, rss integration 6. Tagging for dynamic organization 7. Free – low stakes
- 27. essons 1. Seeing documentation benefits 2. Transforming culture, slowly 3. Tracking work done 4. Contributing regularly 5. Spreading word and motivation to other teams
- 28. enterprise social networks Alan Belniak
- 29. enterprise social networks What are they? community people shared interests Why are they used? group thought collaboration exposure to new issues crowd-sourcing knowledge sharing locating in-house experts
- 31. enterprise social network providers
- 32. case study enterprise social network
- 33. enterprise social network case study
- 34. essons 1. Understand the objectives 2. Determine evaluation criteria for potential solutions (spend lots of time here!) 3. Consider adoption rate carefully 4. Think big, start small, scale fast quotation credit: Mats Lederhausen, managing director of McDonald's Ventures; http://www.entrepreneur.com/tradejournals/article/152641350.html
- 36. what are FORCES 1. Low risk 2. Low cost working 3. General desire to connect among certain subset for you 4. Need to drive down costs, yet workload remains
- 37. there are FORCES 1. Lack of understanding how 2.0 tools work working 2. Lack of content for pre-seeding 3. Adoption anxiety and burden and inertia 4. Focus is on risks and you cultural incompatibilities
- 38. recipe for success 1. Make open and easy to use 2. Base design on corporate brand 3. Expose connections 4. Link to e-mail 5. Identify the right content 6. Focus on people 7. Provide initial structure 8. Lead by example – practice what you preach
- 39. corporate eb2.0 La Fin