The document discusses harnessing the power of a team wiki for an organization. It describes implementing a wiki in mid-2005 and some early progress capturing information like procedures and passwords, as well as struggles getting some teams onboard. It also lists current needs for the wiki like rich email, notifications, and workspaces and lessons learned like the importance of etiquette, governance, and promotion to drive participation.

1. Harnessing the power of a team wiki An SME case ... 14 th August 2008 Andrew Mitchell [email_address]

2. Fairytale

7. Urbis work 1

8. Urbis work 2

9. Urbis work 3

11. Urbis work 4

17. Team culture Tomorrow better than yesterday

19. Mid-2005

21. Some early progress (GIS)

22. Mid-2006

23. Some slower than others (early Library)

24. CLIENT NAME

25. Agendas & Actions

26. Idea Capture

27. Procedures

29. Passwords

30. Multiple Authors

31. People Finder

33. Project Finder

36. Intranet 4.0

38. Search Engine

40. SOME RE-ORGANISATION

41. Before

42. After

43. Before

44. After

45. CURRENT NEEDS

46. Rich Email

47. Rich RSS

48. Notification

49. Comparison

50. Single Sign On

51. WYSIWYG

52. Workspaces

53. Access Control

54. Approved Content

55. LEARNING

56. Little Content

57. Lots of Content

58. Etiquette Talk about Etiquette

59. Gardening More Gardening

60. Promotion Tell People

61. Promotion Permit People

62. Some mess is OK

63. No, too much!

64. Freeform is OK

65. It’s OK to be out of date… sometimes

66. Lasting Truth

67. Past Truth

68. Collaborative Truth

69. My thanks to: Stuart French Ignatius Winarto Gill Patterson Danny Matulic & the whole team Let’s talk…