NCF05 Implementing Wikis
NCF05 Implementing Wikis
wikis
Implementing wikis in a corporate setting
Constantin Basturea
www.thenewpr.com
Wiki buzz
• Business Week: They're Web sites
anyone can edit - and they could
transform Corporate America
• Wall Street Journal: Wiki May Alter
How Employees Work Together
• PR Week: PR firms adopting wikis to
buoy internal, external comms
• Forbes: Extreme Blogging - Best of the
Web 2004
• Infoworld: 2004 - The Year of the
Enterprise Wiki
Wikipedia: http://en.wikipedia.org/wiki/Main_Page
Your wiki is not Wikipedia
No problems with:
• Public access
• Anonymity
• vandals, spammers, monitoring
pages integrity
• NPOV = Neutral Point of View
• Copyright (in Wikipedia all content must
be in the public domain)
A wiki should be beautiful
• Wikis: minimalism & simplicity, so “look doesn’t
matter” (that was back in ‘95)
• 2005: It’s not for geeks only anymore
• Interface design can impact positively the adoption
of a new technology
• User-friendly interface design, like any other
professional software – brings trust
• Recommended: customize the skin of your wiki
Common complaints about wikis
• They're ugly (design)
• Vandals will destroy my work (content integrity)
• There's no accountability (responsibility)
• There's no structure (organization)
Wanted: wiki gardeners
(* Meatball Wiki)
Implementing a wiki:
Have realistic expectations
• A wiki will not force people to collaborate
• People should take responsibility for
collaboration
• The wiki offer: very simple, intuitive, flexible,
non-technical, easy way of facilitating
collaboration and sharing
What a wiki brings:
old vs. new
Passive reader Active writer
Dependence on webmaster’s Update pages on the fly
updates
Information consumption Information creation & sharing
No ownership Stakeholders
Formal Informal, human voice
E-mail as information graveyard Information in context + flow
Fixed navigation, changing Flexibility in organizing
content is difficult navigation and refactoring
content
What a wiki brings: extra
• Train users
• Respond to users' concerns
• Build momentum
• Allow organic growth of the community
• Leverage existing habits
• e.g.: integrate RSS in Outlook with Newsgator
• Promote the wiki
Technical factors to consider when
picking a wiki solution
• Hosting: external vs. internal
• Security and access control
• Data portability; wiki markup 'translators'
• Ease and breadth of customization
• Features set
• Ready-to-use applications
• RSS notifications
• Setup, support and training services
Wiki software producers