organisational wiki adoption
Post on 21-Oct-2014
207.105 views
DESCRIPTION
A look at best practices for wiki adoption within enterprises.TRANSCRIPT
Mike Cannon-Brookes - [email protected]
Organisational Wiki Adoption
Atlassian Software8200 customers. 95 countries.125 people. 5 years. 3 offices. $26 million. 2 crazy kids.
Crew Wanted
Html + Css + Javascript Pirates
Atlassian Confluence Largest enterprise wiki.
Why a wiki?
Knowledge 1.0 Create alone. Layer slowly.
Knowledge 2.0 Work together. Layer faster.
Generation Yspace Online collaboration is natural.
Simple, contextual content
Simple, contextual content
More archival than emailLess process than Word
Epit
Edit
Edpit
Enterprise Wikis Are Like Wikipedia?
No.
1. Open versus secure
2. Collaboration not publishing
3. Vandalism not present
4. Small team rather than planet
5. A tool not an encyclopaedia
Enterprise Wiki versus Wikipedia
Statistics * registered users, not authors
Atlassian WikipediaWikis
PagesComments
Blog PostsComments
Revisions
Authors
65 + 165
10,4002,300
10m3,0005,700
106,600(1:10)
167m(1:16)
176 5.5m*
The Beatles“The love you get is equal
to the love you give”
Wikis In Enterprise
Corporate Web 2.0
“...financial services has a risk-averse nature.”
Harvey KoeppelCIO & Senior VP
“Internally we have started using wikis in large projects where there is lots of terminology or
processes...”
Harvey KoeppelCIO & Senior VP
“...financial services has a risk-averse nature.”
“We don’t have a Production meeting without the wiki.”
18 June 2007
“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.’”
How do you get a wiki adopted?
People and ProcessNot Tools
What is the competition?
Top 4 Wiki Enemies
#4 - Intranets Fight uneditability!
#3 - Knowledge Management Folksonomy not taxonomy.
#2 - Email Communication not information.
#1 - Share Drives End forest-of-folders hell.Most docs don’t need Word.
How do we use them?
Induction1. Create personal space2. Write about yourself
Start editing the wiki on day one with a personal introduction.
Internal Blog1. Blog posts2. Page edits3. Discussion
Keep everyone on the same page. Reduce email.
Staff ListUseful, necessary content Create reasons to visit the wiki.
Personal SpacesGive people their own area to own De-scarify the system.
MeetingsMove familiar items to the wiki. Creates editing cycles.
MinutesAgenda
ProjectsTasks
Social organisation Encourage non-work use
Do you ban facebook? Trust your employees
Be As Open As You Can Don’t kill the wiki!
Wikis Collaborate Too
Widgets!
Share calendaring simply and contextually
CalendarMashup schedule data
Task ListContextual content!
Extremely popular widget in teams
Charts Agile Business Intelligence
Real time from Excel, DB etc...
MapsClassic Google maps mashup
Show contextual location data inside a document.
Code SnippetsEmbed code within documents from SCM
Documents are alive and always update to date with examples and APIs
Patternspatterns
wikipatterns.com
Wiki Champion The go-to guy for your wiki
Barn Raising Jump start your wiki with a party
Magnet Attract with exclusive content
Outlines that guide peopleScaffold
Small, continuous gardeningWikiGnome
anti-patterns
Empty Pages Editing is easier than creating
Laffy4k @ Flickr
Beware over-engineering Organic is better, manToo Much Structure
Trust others. Teach them to edit.Do It All
Lessons
Have A Purpose
Have A Purpose“To Make Them Collaborate”
Is Not A Purpose
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
Wiki AdoptionRecipe
Q & A
Mike Cannon-Brookes [email protected]
http://blogs.atlassian.com/rebelutionary
Don’t forget, we’re hiring Web Pirates http://www.atlassian.com/about/jobs