(Things to think about) Before you pick a wiki
Download as PPTX, PDF0 likes1,096 views
The document discusses considerations for implementing wikis in organizations, highlighting their potential uses such as knowledge capture and project management. It presents questions organizations should ask before adopting wikis, including issues related to content ownership, user roles, and editorial workflows. Additionally, it emphasizes the importance of legal considerations regarding user-generated content and licensing.
(Things to think about) Before you pick a wiki
- 1. This slide intentionally left blank
- 2. Policy and Process Considerations for Collaborative Authoring EnvironmentsJanet SwisherMozillaSession hashtag: #boring
- 3. (Things to Think About)Before You Pick a WikiJanet Swisher, @jmswisherMozillaSession hashtag: #b4wiki
- 4. Baseline assumptionsA wiki is a website that allows the creation and editing of any number of interlinked web pages via a web browser using a simplified markup language or a WYSIWYG text editor. —Wikipedia
- 5. Most wikis are not like WikipediaWhy use a wiki?InternalWorkgroup coordination
- 9. Product documentationOur scenarioYour organization is considering or has decided to move some customer-facing information (documentation or knowledgebase) to a wiki.
- 11. Photo by Nate Steiner
- 12. Photo by Jim Linwood
- 13. A wiki is just a (kind of) CMSAuthoring environment
- 15. Delivery platformAnn Rockley, Managing Enterprise Content, p. 312
- 16. 10 Questions to ask before startingfrom WIKI: Grow your own for fun and profit, Alan PorterWhat business issue will the wiki resolve?
- 17. How will you measure success?
- 18. What is the expected return on investment?
- 19. Where will the content come from?
- 20. Who will use the wiki initially?
- 21. Who will use the wiki in the future?
- 22. Who will own the wiki?
- 23. Where will the wiki be hosted?
- 24. Which wiki should I use?
- 25. What controls will I need?Who will contribute?90%: “lurk” but never contribute
- 26. 9%: do a little
- 27. 1%: do a lotJakob Nielsen, Participation Inequality: Encouraging More Users to Contribute
- 28. Who will do what?RolesWritersEditorsSMEsManagersPartnersCustomersTasksWritingEditingReviewingUpdatingMaintaining
- 29. Define the editorial workflowPre-publication review (may be necessary for external wikis)Post-publication review (via RSS feeds)Ad hoc review
- 30. Define the publication workflowDefault: What happens in the wiki stays in the wikiPhoto by Thierry
- 31. Define the publication workflowWiki as an output format only: DITA2wiki
- 32. Define the publication workflowPrint output from a wiki Confluence PDF exportMediaWikiPdf Export extension (see wiki.service-now.com for an example)
- 33. Who stands behind it?IANAL: Consult your attorney for legal advice.Warrantied content (read-only)Unwarrantiedcontent (user-contributed)
- 34. What can we do with users’ content?IANAL: Consult your attorney for legal advice.Grant a license vs. assign copyrightExplicitly stated in terms-of-useShould be irrevocable
- 35. What can users do with our content?IANAL: Consult your attorney for legal advice.Default: All Rights ReservedCreative CommonsOther terms
- 36. Thanks!Resources I mentioned: http://www.janetswisher.com/?itemid=283Email me: JMSwisher@gmail.comFollow me: @jmswisherShare your feedback: http://www.surveymonkey.com/stcsummit
Editor's Notes
- #11: Everything you know about content management applies to wikis, too.A wiki is a CMS with specific choices for the core elements.
- #13: Tech writer jobs are not at risk, because users are unlikely to take over content production.Don’t consider a wiki to be a failure if the participation level is low.
- #14: Connect the two columns in the way that makes sense for your business.
- #15: If you have more than one level of review, you don’t really have a wiki. You have a CMS with a web-based editor.
- #20: Users have to give you the right to use what they right.