A basic wiki primer. Examples are nonprofit but info applies to any organization. Covers: What are the attributes of a wiki? How do wikis differ from other commonly used communication and collaboration tools? What kind of problems can a wiki solve? What are its uses? What are examples of these use cases? (with screenshots) How can you build a successful wiki?

1. Wikis for Nonprofits: Could a Wiki Help Your Organization? Julie Spriggs

2. You are asked to do more with less. © Dave Belfer-Shevett (dbs@homeport.org)

3. Your mission is engaging, and exhausting.

4. The amount to do can be overwhelming. The amount to do can be overwhelming. http://flickr.com/photos/zen/1121085610/

5. But you want to do it to make a greater impact. Image courtesy: Kraus-Fitch Architects http://www.krausfitch.com/

6. A wiki can help. Nils Peterson

7. Wikis are easy to use, often free, and allow collaboration, knowledge retention, search, and real-time centralization of information. http:// en.wikipedia.org/wiki/Wiki

8. Here is how a wiki works. http://blip.tv/file/get/Leelefever-WikisInPlainEnglish801.wmv

9. A wiki is distinct from other commonly used communication and collaboration tools.

10. Collaboration on complex documents and finding the right version of a document can be difficult. Wikis can facilitate this. Courtesy "Intellipedians" US Intelligence Community

11. Ideas and plans are hidden in dispersed email inboxes. Wikis allow groups to coordinate and centralize. Copyright © 2008, Valdis Krebs http:// orgnet.com/email.html

12. Whiteboard ideas get lost. Wikis help you retain, organize, and then find all those great thoughts. flickr.com/photos/lisamac/293093751

13. Project management systems can be complex and costly. Wikis can be free, flexible, and easy to learn.

14. As well, wikis connect ideas, people, data and build community . http:// en.wikipedia.org/wiki/Community

15. You can use wikis for tasks critical to your organization.

16. example: COLLABORATIVE DOCUMENT CREATION – a report http:// scpsvisioning.wikispaces.com/Board+Presentation

17. example: COLLABORATIVE DOCUMENT CREATION – a report

18. example: COLLABORATIVE DOCUMENT CREATION – a report

19. example: COLLABORATIVE DOCUMENT CREATION – a report

20. example: COLLABORATIVE DOCUMENT CREATION – how to manual Other topics: Website development (21) ; Innovation stuff (6); Technology (5); Documentation (7); Misc (6).

21. example: PROJECT MANAGEMENT – planning a conference

22. example: PROJECT MANAGEMENT – planning a conference

23. example: PROJECT MANAGEMENT – planning a conference

24. example: PROJECT MANAGEMENT – planning a conference

25. example: PROJECT MANAGEMENT – planning a conference

26. example: PROJECT MANAGEMENT – planning a conference http://np2020.wikispaces.com/

27. example: PROJECT MANAGEMENT – planning a conference http://np2020.wikispaces.com/Conference+Notes http://np2020.wikispaces.com/Conference+Notes

28. example: PROJECT MANAGEMENT – an event Most current view of page History of page

29. example: PROJECT MANAGEMENT – an event

30. example: PROJECT MANAGEMENT – an event Most current view of page History of page

31. example: KNOWLEDGE BASE – organizational

32. example: KNOWLEDGE BASE – organizational

33. example: KNOWLEDGE BASE – organizational

34. example: KNOWLEDGE BASE – organizational

35. example: KNOWLEDGE BASE – intraorganizational for practitioners Thoughtfarmer

36. example: KNOWLEDGE BASE – glossary

37. example: INTRANET - department Home page

38. example: INTRANET - department Calendar

39. example: INTRANET - department Collaborative document creation More annual report

40. example: INTRANET - department Policies

41. example: INTRANET - department Department content- Presentations

42. example: INTRANET- department Content- Organization’s press releases

43. example: INTRANET - department Organization archived content- Blog

44. example: INTRANET - department Permissions

45. example: EXTRANET – organizing constituents

46. example: EXTRANET – organizing constituents

47. example: EXTRANET – disaster management End of examples

48. To ensure your wiki thrives, create a platform for success. Andreas Feininger

49. tip: Define the scope of the wiki and S tructure it Office of Disability Services Policies and Procedures Manual DAWN Source “Structure, Populate, Review, Invite, Garden”: Michael Idinopulos in his blog: Transparent Office

50. tip: Scope: In-the-flow wikis may be adopted more readily. In-the-flow wiki Source: Michael Idinopulos in his blog: Transparent Office http://michaeli.typepad.com/my_weblog/page/2/ =Used during the daily flow of work to get work done For example: for project management, collaborative document creation, collaborative workspace =Out of the daily flow of work= Capturing knowledge and insights that people collect in the course of their work. Above-the-flow wiki

51. tip: Sometimes in addition to creating a s tructure of pages and links, you also need templates for pages.

52. tip: Seed it ( P opulate it) with content, R eview it and discuss your adoption strategy Source “Structure, Populate, Review, Invite, Garden”: Michael Idinopulos in his blog: Transparent Office

53. tip: Seed it ( P opulate it) with content, R eview it and discuss your adoption strategy 1. 2. Source “Structure, Populate, Review, Invite, Garden”: Michael Idinopulos in his blog: Transparent Office

54. tip: I nvite others to read and start participating. Source “Structure, Populate, Review, Invite, Garden”: Michael Idinopulos in his blog: Transparent Office

55. tip: G arden it…and find people for key roles Champions Gardeners Wiki master Page stewards

56. Notifications allow a community to monitor the wiki

57. You are asked to do more with less.

58. A wiki can help.

59. Source: SPRIG: “Structure, Populate, Review, Invite, Garden”: Michael Idinopulos in his blog: Transparent Office