Wikis: Living Knoweldge Banks


Published on

This presentation provides a brief overview of wikis and their uses for knowledge management for any business organization. Originally presented at the SALT Summer Conference 2007.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Wiki-wiki means fast or quick in Hawaiian
  • 2 minutes Internet was/is often treated like a book Once upon a time books were strange and new Focus on showing how new ways enhance ‘traditional ones’ Until recently people have used the internet as a text dump. The difference is today… the internet is books on steroids Multiple people can contribute to developing content People all over the world can contribute and quickly People can share and contribute to the development of media other than print (videos, books, apps, etc.) Web 2.0 and new web use for storing content is probably just as foreign to some folks as books were to people who were used to a rich oral tradition. Younger… generations and people who have a greater experience and proclivity with web-tech may be open to doing things/seeing things differently. To get change-resistors on board you must make the process appear simple/easy and as good as the way they used to do it.
  • 1 minute
  • >30 seconds
  • 1 minute
  • 30 seconds Best example of an expansive wiki thousands of people contribute to it’s development.
  • 2 minutes Situation – Working with an extended group of SME’s on a set of large/complex processes in SAP - Problem – Members of the training team were in globally dispersed time zones. Meetings for design review occurred during off hours for some of the team members. Also e-mail trails with documents and complexity of Sharepoint sites were causing problems with document control and versioning. Players – Instructional design/development team (3), SME’s, Project Stakeholders Outcome – Users able to collaborate much more easily. Less confusion. Better documentation
  • 1 minute
  • >30 seconds
  • 3 minutes Leo and Leah are instructional designers who want to set up a podcast Sally works in HR but she knows that Jana has a great deal of information and contacts within the company she also has a background in copyright law after working for legal for 8 years Sam works in IT but has a background in audio engineering Justin is an web developer who has experience in both graphic design and animation but he’s interested in working with Pam and the IDs (Leo and Leah) to develop a few demos for IT Jana is a manager who has been with the company for many years and she has visibility and contacts with many others Pam is a technical writer who partners with the Instructional Designers in training development content The Boss (doesn’t have a clue)
  • >30 seconds
  • 2 minutes Quick collaboration – text and visual collaboration. People on a team can share and build on text. They can also find out who’s knowledgable in a topic or has skills in an area they’re weak at. People can continually contribute to topics or areas, problems that need solving and all people in the group can visibly see these contributions  Group knows more than just a group that sits in silos and shares e-mails with only some or a few members within the group. Content Development doesn’t depend on who has the latest version of the word document? Version Tracking – many wikis have features which allow people to track changes. You can revert if necessary if a mistake is made Expertise – I can look at someone’s profile and I know what’ they’re good at. I can share with others what areas of knowledge I have under my belt.
  • 3 minutes Collaboration and the idea that no one is always right are keys to the success of good wiki stewardship and participation Easy adoption might be a generational thing Individualistic Collaboration vs. Group Collaboration– E-mail chain collaboration is an example of individuals who collaborate in an individualist style Might be best to launch initial efforts to build a wiki with people who are open to the idea – no one likes to be forced into doing something they find alien with out an example of someone doing it.
  • >1 minute Getting creative means using what you have to fit your needs rather than relying on pre-built widgets and features. For example we created a navigation feature at in our wiki template page to include a back to previous page and home page for easier navigation. We also used simple tables to organize our content.
  • >1 minute
  • 3 minutes Combine all tips slides - Be Flexible : Let go of hard-line organization and categorization in the beginning Wiki content and organization grows organically Rigid structuring doesn’t work (though structuring the wiki portal so that people can find information is key). Also having a wiki that has a effective search feature helps. Train Your Group Build a sample site Let everyone know that they can take ownership in shaping the wiki Demo how to post and use Give lots of positive encouragement Have fun Every Gardner Prunes Don’t let the wiki be a text/content dump Assign people as architects or monitors Train people to think before they add Everyone should take ownership in figuring out which content should be archived
  • 2 minutes Similar to Intel Group wiki however, design/layout is arranged in a more visible format
  • 1 minute This is an example of a knowledge map similar to one we use in my current group. Designed in PBWiki Including your business process as part of your wiki is key. Helps orient/re-orient staff to group processes and flows. Suggest initially meeting with your group to brainstorm areas/topics they feel helpful to their job. You can use these topics as a basis for structuring your knowledge map categories
  • 1 minute Few more notes on structure
  • Wikis: Living Knoweldge Banks

    1. 1. Wikis Living Knowledge Banks
    2. 2. Internet use: Today’s End User :: Books :: to Audience used to Oral Tradition Before books oral history and communication were common sources of communication/info Yesterday… books, print, radio, media  ideas Today…internet  promotes live active collaboration Open it? If it’s that simple I wouldn’t have called the helpdesk, would I? The book
    3. 3. Wiki Definition <ul><li>A wiki is a web site that is fully editable from any web browser… by anyone with access. </li></ul>… but it’s much more than just that
    4. 4. Wikis open up a universe of knowledge and an infinite playground for learning and collaboration with others
    5. 5. Wiki – Levels of Application Large Scale Small Scale Encyclopedia Massive number of contributors to (near unlimited) great body of content SME/Designer Medium Scale Team or Organization Immediate team/organization can contribute. Can include satellite/ or ancillary contributors One/one collaboration. Text/visual content can be shared asynchronously Ex: Wikipedia Ex: Department Wiki
    6. 6. Large Scale - Wikipedia
    7. 7. Medium Scale –Organization/Team <ul><li>Note key elements: </li></ul><ul><li>Calendar </li></ul><ul><li>Team Info </li></ul><ul><li>Developer Notes Pages </li></ul><ul><li>Templates </li></ul>Visibility to/for everyone
    8. 8. Wiki Profile Page Example <ul><li>Note key elements : </li></ul><ul><li>Group information </li></ul><ul><li>History </li></ul><ul><li>Expertise </li></ul><ul><li>Informal information </li></ul>Visible to everyone
    9. 9. Why is visibility good? pam jana leo sam justin the boss leah sally
    10. 10. Why is visibility good? pam jana leo the boss sam justin leah sally
    11. 11. Without a knowledge network* you get… *developed in a wiki & fostered by work culture Center of Control the boss
    12. 12. Common Benefits and Features of Wikis Quick collaboration Collect Team Expertise and Tribal Knowledge Record Team Activities Reduces e-mail trails Version Tracking Content Development
    13. 13. Are you Wiki-ready? <ul><li>Wiki adopters need to: </li></ul><ul><ul><li>Be open to a way of life built around collaboration </li></ul></ul><ul><ul><li>Understand and appreciate dynamics and benefits of group-think </li></ul></ul><ul><ul><li>Rethink Individualistic Collaboration vs. Group Collaboration </li></ul></ul><ul><ul><li>Make the assumption that everyone’s an expert (or has expertise in some areas) </li></ul></ul><ul><ul><li>All or most members of the team must buy in to the wiki philosophy </li></ul></ul>Sometimes you have to give up all the fancy widgets and features
    14. 14. Question <ul><li>Ask yourself what you want to use the wiki for? </li></ul>Group collaboration Meeting records Documentation (Tribal Knowledge) Communication Knowledge Management There are tools which can accommodate all these things Sometimes you just have to get ‘creative’
    15. 15. Tips and Tricks – Selecting Wiki Tools <ul><li>What is your group’s tech comfort zone? </li></ul>Less Tech Savvy Tech Savvy PB Wiki or WetPaint Mediawiki or wikispaces Feel comfortable adjusting html, Mark up text, some coding WISYWYG Editing Ready-made editing tools
    16. 16. Additional tips and tricks… <ul><li>Be flexible </li></ul><ul><li>Train your group and partners </li></ul><ul><li>Every gardener prunes </li></ul>
    17. 17. Structuring your wiki Documentation Communication Meeting Records Group Collaboration
    18. 18. Structure continued… Knowledge management
    19. 19. Conclusions Don’t be stuck on your format/content Keep levels of information transparent and visible Prune and update when necessary Respect other’s work Adopt simple naming conventions Have fun Everyone playing must buy into collaboration culture
    20. 20. Resources <ul><li> </li></ul><ul><li>pbWiki: </li></ul><ul><li>Wikispaces: </li></ul><ul><li>Wikipedia: </li></ul><ul><li>Informal Learning Jay Cross on Why Wiki?: </li></ul>