How To Use Wikis For Business - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

02:57 PM

How To Use Wikis For Business

Content management systems will always have their place in the publishing world, but they've never been the best tools for business collaboration. A simple open-source app called the wiki may soon rule the knowledge management roost.

Why Wiki?

Thanks to the Web, and networks in general, the cost of publishing and sharing information has diminished substantially — which makes wikis the killer app for corporations. Prior to wikis, an expensive enterprise application would have been required for sophisticated information management. But because most wikis are based on open-source code, they're free for companies who opt for an open-source distribution, or relatively cheap for companies willing to pay for their implementation and support.

Wikis are designed to facilitate the exchange of information within and between teams. Content in a wiki can be updated without any real lag, without any real administrative effort, and without the need for distribution — users/contributors (with wikis, they're one and the same) simply visit and update a common Web site.

Wikis can centralize all types of corporate data, such as spreadsheets, Word documents, PowerPoint slides, PDFs — anything that can be displayed in a browser. They can also embed standard communications media such as e-mail and IM. Heavy-duty PHP-based wikis can directly interface with company databases to bring in audio and picture files. A wiki's functionality is limited only by the programming skills of the person who implements it.

A traditional project management tool simply
cannot reproduce the environment of collaboration and involvement that wikis create.

It's important to note that placing a document in a wiki does not necessarily make it editable by everyone with access to the wiki. For example, the marketing department can make a PowerPoint slide available to the sales team or the company at large without letting them change or overwrite it.

What's more, wikis have built-in version control even for those who have edit privileges. No changes can be made without creating a record of who made those changes, and reversion to an earlier version is a matter of a few clicks.

Consider implementing a wiki if:
  • You want to establish a company intranet quickly and cheaply without sacrificing functionality, security, or durability.
  • You want to publish a range of corporate documents in one universally accessible location and let employees manage those documents with a minimum of effort, lag, and risk of redundancy.
  • You want to manage and organize meeting notes, team agendas, and company calendars.
  • You need a project management tool that is cheap (if not free), extensible, and accessible through any Web browser.
  • You need a central location where shared documents can be viewed and revised by a large and/or dispersed team.
A wiki might not be right for your organization if:
  • You need to use complex file formats. Some wiki platforms can support only text or HTML files. Consider using a PHP/SQL-based wiki platform that can handle robust file types. Avoid wikis based on PERL.
  • You don't have a staff member who can take responsibility for its use. A wiki is only as good as its ontology (or the search engine it uses). You will need somebody who can establish conventions for naming pages and maintaining links.
  • The collaborative format isn't appropriate for your group or workplace. Peer review is not always the best solution for content management.
  • You're looking for an exchange of views. Wikis are not the best tool for airing opinions or carrying on conversations. If that's your primary goal, use a blog instead.

Wikis Vs. Traditional Content Management Software

There is a plethora of project management and collaboration software available, so why use a wiki instead?

Wikis are cheap, extensible, and easy to implement, and they don't require a massive software rollout. They also interface well with existing network infrastructures. Wiki software maker Socialtext, for instance, has concentrated on making its platform work with existing global ID and registration systems behind corporate firewalls.

Furthermore, wikis are Web-based and thus present little or no learning curve in the adoption cycle, and they allow the user to determine the relevancy of content rather than being dependent upon a central distribution center or a linear distribution chain. After the initial setup, users, not administrators, control a wiki, to the benefit of both.

A major benefit of many wikis is their ability to organize themselves organically. In other words, users can create their own site structure, or ontology, rather than have it imposed on them by the developers of content management software. That said, wikis need to be used by people with a shared cultural language so that the ontology and navigation make sense to everybody. Wikis are well-suited to the workplace because a common corporate language is already in place.

Finally, it is the inherently collaborative nature of wikis, as opposed to the workflow structure of content management software, that distinguishes wikis and gives them the upper hand. A traditional project management tool simply cannot reproduce the environment of collaboration and involvement that wikis create.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
2 of 3
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
2/25/2014 | 10:34:31 AM
Re: Author
Hey!  That would be me, Ezra Goodnoe.  Glad you find the article useful.
User Rank: Apprentice
2/15/2014 | 4:45:08 PM
This a really good article for a report I'm writing on the use of wiki's, blogs and podcasts in business. Is it possible to get the Authors name so that I can cite this website. Thanks!
State of the Cloud
State of the Cloud
Cloud has drastically changed how IT organizations consume and deploy services in the digital age. This research report will delve into public, private and hybrid cloud adoption trends, with a special focus on infrastructure as a service and its role in the enterprise. Find out the challenges organizations are experiencing, and the technologies and strategies they are using to manage and mitigate those challenges today.
What Digital Transformation Is (And Isn't)
Cynthia Harvey, Freelance Journalist, InformationWeek,  12/4/2019
Watch Out for New Barriers to Faster Software Development
Lisa Morgan, Freelance Writer,  12/3/2019
If DevOps Is So Awesome, Why Is Your Initiative Failing?
Guest Commentary, Guest Commentary,  12/2/2019
Register for InformationWeek Newsletters
Current Issue
Getting Started With Emerging Technologies
Looking to help your enterprise IT team ease the stress of putting new/emerging technologies such as AI, machine learning and IoT to work for their organizations? There are a few ways to get off on the right foot. In this report we share some expert advice on how to approach some of these seemingly daunting tech challenges.
White Papers
Twitter Feed
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.
Sponsored Video
Flash Poll