Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How we wiki

2,008 views

Published on

A presentation called 'How we wiki' for the Gov2.0 conference on 19 October 2009 in Canberra.

Published in: Technology
  • What a great presentation! It's great to see all the value you're getting out of Confluence.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

How we wiki

  1. 1. How we wiki<br />Bobby Graham: Director Web Publishing (Acting)<br />National Library of Australia<br />Gov 2.0 Conference: 19 October 2009<br />
  2. 2. Vital statistics<br />The Library has 450 employees.<br />We implemented our first wiki in 2006.<br />We have 100+ wiki spaces.<br />We use Confluence.<br />Now we have two wikis: internal and external.<br />
  3. 3. Why wiki?<br />We support transparency of information.<br />We engage with other libraries – nationally and internationally.<br />We have a professional interest in information management.<br />
  4. 4. Why Confluence?<br />It was compatible with our systems infrastructure.<br />It is widely used by corporate organisations.<br />We had an existing relationship and experience with the company.<br />It has an active open source community, building macros and plug-ins.<br />
  5. 5. What wiki features?<br />WYSIWYG editor<br />Pages, news items and comments<br />Access control<br />One installation; multiple wikis<br />Export to PDF and MS Word<br />
  6. 6. What wiki stuff we like<br />Browser based editing<br />Versioning<br />Recently updated listing<br />Search<br />Pages print well<br />
  7. 7. Wiki flexibility<br />It happens now<br />Easy to restructure<br />History<br />Easy to roll back<br />But . . . flexibility, freedom, trust = uncertainty<br />
  8. 8. Wiki engagement<br />Anyone can participate in the wiki.<br />All staff can access, read and edit any wiki space.<br />All staff can freely con-tribute new content using any web browser.<br />We all collaborate.<br />
  9. 9. Wiki governance<br />Admin is by community.<br />Any wiki user can fix spelling, formatting, grammar or structure.<br />Author is recorded.<br />We can roll back to a previous version.<br />Space administrators<br />
  10. 10. Wiki transparency<br />We share information.<br />All staff can collaborate on any project or topic.<br />All staff can share infor-mation across all APS levels.<br />
  11. 11. Work in teams<br />We could work in a group or in a project team.<br />We work across teams and projects.<br />We collaborate internally and externally.<br />Each community space is like a mini wiki in its own right.<br />
  12. 12. What kind of projects?<br />We manage the Library’s collections.<br />We look after the Library’s readers and users.<br />We plan to implement new services.<br />We work in divisional, branch and group projects.<br />
  13. 13. How we wiki<br />Pages are the building blocks of the wiki.<br />A statement of purpose is a good way to start.<br />We add content like text, images and tables.<br />We attach files.<br />We can find stuff: any location is good.<br />We (sometimes) archive stuff.<br />
  14. 14. What we wiki<br />We plan, draft and write documents.<br />We prepare project plans.<br />We manage activity schedules.<br />We maintain rosters and planning docs.<br />Sometimes we improve business processes.<br />
  15. 15. Wiki woes<br />Wiki users expect Word.<br />They miss structure and presentation.<br />Some resist a new system.<br />Users may not commit or own spaces or pages.<br />It’s easy to publish and forget, or not archive.<br />Wiki is yet another place to publish (not).<br />
  16. 16. Case study: How to improve a business process<br />400+ procedures documents . . . In various Excel spreadsheets<br />How to share information in all of these docs?<br />How to update the documents?<br />Where to publish them?<br />Who is responsible?!<br />
  17. 17.
  18. 18.
  19. 19. What was the outcome?<br /><ul><li>Reduced no. of documents
  20. 20. Source files updated and maintained.
  21. 21. Archived in TRIM.
  22. 22. Content published on intranet and linked to TRIM.
  23. 23. Updated content always available to users.
  24. 24. Four staff members maintain the wiki page.</li></li></ul><li>What wikis?<br />Internalwiki space: all staff can view and edit.<br />Closed wiki space: a group of external and internal users can view and edit.<br />Public wiki space: all staff can view and edit, public can view only.<br />External wiki space: ex-ternal users and all staff can edit and view.<br />
  25. 25. What have we learnt?<br />People may make mistakes, but they will take responsibility for:<br />their own learning<br />organising things<br />tidying up<br />Given the opportunity:<br />they have good ideas<br />learn from each other<br />
  26. 26. What works well?<br />Documenting services<br />Documenting processes<br />Working and writing collaboratively<br />Collaborating with external partners<br />
  27. 27. What doesn’t work well?<br />The wiki could be used for what it was never intended:<br />archiving<br />publishing workflows<br />publishing secure documents<br />Blog style writing<br />
  28. 28. Is wiki successful?<br />How should we measure success?<br />100+ wikis implemented in three years<br />10 public wiki spaces<br />12 closed wiki groups<br />Continued use of service<br />
  29. 29. Wiki future<br />We plan to improve the interface: add themes.<br />We’d like to make browsing more pleasant.<br />We plan to improve wiki help and guidance.<br />We’d like to assist with training.<br />
  30. 30. With thanks to Michele Huston for her direction and leadershipAll images courtesy of the National Library of Australiabgraham@nla.gov.auTel: 02 6262 1542http://libertylittlebasil.blogspot.com/@LibertyBasil<br />

×