Organisational Wiki Adoption

Slide 1: Organisational Wiki Adoption Mike Cannon-Brookes - mike@atlassian.com

Slide 2: 8200 customers. 95 countries. Atlassian Software 125 people. 5 years. 3 offices. $26 million. 2 crazy kids.

Slide 3: Crew Wanted Html + Css + Javascript Pirates

Slide 4: Atlassian Confluence Largest enterprise wiki.

Slide 5: Why a wiki?

Slide 6: Knowledge 1.0 Create alone. Layer slowly.

Slide 7: Knowledge 2.0 Work together. Layer faster.

Slide 8: Generation Yspace Online collaboration is natural.

Slide 9: Simple, contextual content

Slide 10: Simple, contextual content More archival than email Less process than Word

Slide 11: Epit

Slide 12: Edit

Slide 13: Edpit

Slide 14: Enterprise Wikis Are Like Wikipedia?

Slide 15: No.

Slide 16: Enterprise Wiki versus Wikipedia 1. Open versus secure 2. Collaboration not publishing 3. Vandalism not present 4. Small team rather than planet 5. A tool not an encyclopaedia

Slide 17: Atlassian Wikipedia Wikis 65 + 165 Pages 10,400 Comments 2,300 10m Blog Posts 3,000 Comments 5,700 106,600 167m Revisions (1:10) (1:16) Authors 176 5.5m* Statistics * registered users, not authors

Slide 18: “The love you get is equal The Beatles to the love you give”

Slide 19: Wikis In Enterprise

Slide 20: Corporate Web 2.0

Slide 21: “...financial services has a risk-averse nature.” Harvey Koeppel CIO & Senior VP

Slide 22: “...financial services has a risk-averse nature.” “Internally we have started using wikis in large projects where there is lots of terminology or processes...” Harvey Koeppel CIO & Senior VP

Slide 24: “We don’t have a Production meeting without the wiki.”

Slide 25: “At Pixar...wiki technology is being used to help coordinate new computerized animation tools for the studio's planned 2008 release of a film called ‘WALL-E.’” 18 June 2007

Slide 26: How do you get a wiki adopted?

Slide 27: People and Process Not Tools

Slide 28: What is the competition?

Slide 29: Top 4 Wiki Enemies

Slide 30: #4 - Intranets Fight uneditability!

Slide 31: #3 - Knowledge Management Folksonomy not taxonomy.

Slide 32: #2 - Email Communication not information.

Slide 33: End forest-of-folders hell. #1 - Share Drives Most docs don’t need Word.

Slide 34: How do we use them?

Slide 35: Induction 1. Create personal space 2. Write about yourself Start editing the wiki on day one with a personal introduction.

Slide 36: Internal Blog 1. Blog posts 2. Page edits 3. Discussion Keep everyone on the same page. Reduce email.

Slide 37: Staff List Create reasons to visit the wiki. Useful, necessary content

Slide 38: Personal Spaces De-scarify the system. Give people their own area to own

Slide 39: Agenda Minutes Tasks Projects Meetings Creates editing cycles. Move familiar items to the wiki.

Slide 40: Social organisation Encourage non-work use

Slide 41: Do you ban facebook? Trust your employees

Slide 42: Be As Open As You Can Don’t kill the wiki!

Slide 43: Wikis Collaborate Too

Slide 44: Widgets!

Slide 45: Calendar Share calendaring simply and Mashup schedule data contextually

Slide 46: Task List Contextual content! Extremely popular widget in teams

Slide 47: Charts Real time from Excel, DB etc... Agile Business Intelligence

Slide 48: Maps Classic Google maps mashup Show contextual location data inside a document.

Slide 49: Code Snippets Embed code within documents from SCM Documents are alive and always update to date with examples and APIs

Slide 50: Patterns patterns

Slide 51: wikipatterns.com

Slide 52: Wiki Champion The go-to guy for your wiki

Slide 53: Barn Raising Jump start your wiki with a party

Slide 54: Magnet Attract with exclusive content

Slide 55: Scaffold Outlines that guide people

Slide 56: WikiGnome Small, continuous gardening

Slide 57: anti-patterns

Slide 58: Laffy4k @ Flickr Empty Pages Editing is easier than creating

Slide 59: Beware over-engineering Too Much Structure Organic is better, man

Slide 60: Do It All Trust others. Teach them to edit.

Slide 61: Lessons

Slide 62: Have A Purpose

Slide 63: Have A Purpose “To Make Them Collaborate” Is Not A Purpose

Slide 64: Wiki Adoption Recipe 1. Grassroots is Best 2. Your Wiki Isn’t Wikipedia 3. The First Edit 4. Build Group Collaboration 5. Spread Adoption 6. Support Emergent Behaviour 7. Watch Out For Obstacles

Slide 65: Q&A Mike Cannon-Brookes mike@atlassian.com http://blogs.atlassian.com/rebelutionary Don’t forget, we’re hiring Web Pirates http://www.atlassian.com/about/jobs