Six Steps To Enterprise Wiki Success


Published on

Originally presented at Content Convergence & Integration 2008.

Wikis, with their free-flowing unstructured approach to knowledge management are catching on like wildfire within organizations. However, there are pitfalls to avoid before rolling them out within your company. This presentation outlines the six key factors to consider before launching one of these applications. Using examples based on real-life success stories using <a href="">ThoughtFarmer</a>, Darren will provide recommendations that will help you achieve success regardless of the wiki platform you choose.

Published in: Technology, Sports
1 Comment
  • could you please send your presentation? it would help me a lot for my thesis. -->
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Six Steps To Enterprise Wiki Success

  1. 1. Launching an Enterprise Wiki 6 Steps to Success Darren Gibbons ThoughtFarmer [email_address]
  2. 5. Why use an Enterprise wiki?
  3. 8. What’s the problem? <ul><ul><li>Intranet team can’t keep up </li></ul></ul><ul><ul><li>If it’s not up-to-date, usage drops </li></ul></ul><ul><ul><li>Updating process alienates </li></ul></ul><ul><ul><li>Ownership is skewed </li></ul></ul>
  4. 9. Turn users into authors
  5. 13. The Green Place Green is no longer the domain of a few crusaders on the fringes of society; it has matured into an established reality. We feel that it is the responsibility of each human and every organization to advance the cause of sustainability, playing a key role through behaviours and decision making. In light of this, we are formally declaring our support for and commitment to initiatives that have as their goal to reduce the impact Kermit.jpg
  6. 15. In the beginning was the document.
  7. 16. They’ve been around for a while
  8. 17. The Good <ul><ul><li>Good for formal communication </li></ul></ul><ul><ul><li>Universal Format (according to Microsoft) </li></ul></ul><ul><ul><li>Print really well </li></ul></ul>
  9. 18. The Bad <ul><ul><li>Documents are formal </li></ul></ul><ul><ul><li>Not great for multiple-author collaboration </li></ul></ul><ul><ul><li>Finding information in documents is not easy </li></ul></ul>
  10. 19. And then there was email
  11. 20. Email Pros <ul><ul><li>Easy. Minimal formatting required </li></ul></ul><ul><ul><li>Fast. Have a thought, bang it out, off it goes </li></ul></ul><ul><ul><li>Universal. Everyone has an email address </li></ul></ul>
  12. 21. Email Cons <ul><ul><li>Too much of a good thing </li></ul></ul><ul><ul><li>Poor for documenting decisions </li></ul></ul><ul><ul><li>Knowledge gets locked inside inboxes </li></ul></ul>
  13. 22. Wiki is Best of Both Worlds <ul><ul><li>Low barrier to content creation </li></ul></ul><ul><ul><li>Shared knowledge archive </li></ul></ul><ul><ul><li>Easily findable </li></ul></ul>
  14. 25. <ul><ul><li>Strengthen workplace community </li></ul></ul>
  15. 26. The six steps to Enterprise Wiki Success
  16. 27. Step 1: Pilot with the right group
  17. 28. Don’t make The pilot group too BIG
  18. 29. Don’t make The pilot group too BIG But don’t make it too small either
  19. 30. Attitude Choose keeners that aren’t afraid to try new things
  20. 31. Seniority Get at least one – preferably more senior member in the pilot group
  21. 32. Step 2: Designate a Wiki Gardener
  22. 33. Wiki Gardener Performs small edits, increase overall value of everyone’s content
  23. 34. Tips for Gardeners <ul><ul><li>Cosmetic editing of content </li></ul></ul><ul><ul><li>Fixing links, organizing </li></ul></ul><ul><ul><li>Tagging </li></ul></ul><ul><ul><li>Set an example for others </li></ul></ul>
  24. 35. Step 3: Start with a basic structure
  25. 36. Blank slate is bad Start with a skeleton It’s easier to edit than create /
  26. 37. Sample structure <ul><li>Tools and Links </li></ul><ul><li>People </li></ul><ul><li>How-To </li></ul><ul><li>News </li></ul><ul><li>Projects </li></ul><ul><li>Offices </li></ul><ul><li>Departments </li></ul><ul><ul><li>Corporate </li></ul></ul><ul><ul><li>Engineering </li></ul></ul><ul><ul><li>Finance </li></ul></ul><ul><ul><li>Human Resources </li></ul></ul><ul><ul><li>IT </li></ul></ul><ul><ul><li>Legal </li></ul></ul><ul><ul><li>Marketing </li></ul></ul><ul><ul><li>Sales </li></ul></ul>
  27. 38. Step 4: Migrate existing content
  28. 39. Barn raising Get 4 or 5 people to migrate content from existing systems
  29. 40. Employee Directory Get employee information into the system
  30. 41. Keep it fresh Aim for new content every day
  31. 42. Step 5: Training and Support
  32. 43. <ul><li>Learning by doing </li></ul><ul><li>Give users a set of tasks to perform </li></ul>
  33. 44. <ul><li>Narrated Walkthroughs </li></ul><ul><li>Screencast software: </li></ul><ul><li>- Adobe Captivate </li></ul><ul><li>- Camtasia </li></ul>
  34. 45. <ul><li>Don’t forget print documentation! </li></ul>
  35. 46. Step 6: Promote and Launch!
  36. 47. Promote: Generate interest
  37. 48. Launch: Make it an event Bring donuts
  38. 49. Six steps to Wiki success <ul><li>Pilot with the right group </li></ul><ul><li>Designate a Wiki Gardener </li></ul><ul><li>Start with a basic structure </li></ul><ul><li>Migrate existing content </li></ul><ul><li>Training and support </li></ul><ul><li>Promote and launch </li></ul>
  39. 50. Thank You! <ul><li>Darren Gibbons </li></ul><ul><li>[email_address] </li></ul><ul><li> </li></ul>