* Create your FREE website now *

More actions

7 effective wiki uses and the companies that benefit from them

Tags:  

7 effective wiki uses and the companies that benefit from them

from:grow your wiki

In CIO magazine, Thomas Wailgum writes, “CIOs really need to listen to their business users and peers, especially when it comes to knowledge-worker productivity issues… they shouldn’t just try to force a generic solution (”Here’s your BlackBerry,” or “Take this laptop”) out to business users before sitting down and listening to them. In many cases, a user won’t know what the solution is, but by being able to explain the problem to IT, a joint, appropriate solution can be discovered. That thinking will ultimately enable more productivity for the user and offer a greater chance of ROI for the technology.”

I meet with a lot of organizations to help guide their wiki adoption, and one common trend I see is this:

When they decide to centrally support an enterprise wiki deployment, it’s because they’ve found that they already have wikis scattered throughout groups, teams, and departments. Wikis were brought into organizations under the radar by people that saw the value and couldn’t wait for the usual bureaucratic process for bringing in new tools.

Does your organization use a wiki?Wikis have gone from those initial small scale pilots and scattered uses - with perhaps a dozen users here or there - to broader communities of hundreds or thousands of users. In the software development world, some of the most common uses include:

  • Developer networks
  • Managing software development
  • Technical documentation
  • Knowledge bases
  • Intranets & extranets

How about some examples?

IBM, SAP, and Sony Ericsson all use wikis as part of their developer networks. Others, like Pixar, Carbon Five, and Red Ant use wikis for collaboration with clients and managing production on major projects.

SAP
SAP Developer Network Wiki On the SAP Developer Network Wikithe, “main criteria for choosing to put content in the wiki is its volatility and dynamics, extendability and/or collaborative character. Ask yourself the question, if you want others to be able to change, extend, regroup, add, etc. your contribution.” That’s an excellent question to ask, especially for content that’s going on a public wiki.

Pixar
Pixar, the iconic producer of animated films that have won seven Academy Awards, uses a wiki internally to manage film production. A recent Wall Street Journal article says the company is using a wiki, “to help coordinate new computerized animation tools for the studio’s planned 2008 release of a film called “WALL-E.”

Sun Microsystems
Sun Wikis I recently talked with Linda Skrocki, Sr. Engineering Program Manager: Blogs, Forums, Planets, Wikis at Sun Microsystems, about how people at Sun use the recently launched wikis.sun.com: “Collaboratively created documentation is a primary use for the wiki, with many spaces for specific initiatives dedicated to building and maintaining community created content. Not all spaces are entirely Sun-centric, and that’s as it should be. For the wiki to be successful, information should be on topics of interest to all participants.”

Red Ant
Red Ant, a Sydney, Australia based web design and development firm, uses a wiki as the main collaboration hub for employees and customers. I asked Ben Still, managing director, how they use wikis: “Say, for instance, we’ve created a design and need to show it to our client. First, a designer makes a page, attaches an image, and they’re done with their part. But then I might look at it and realize that it needs a bit more explanation, or a link to a wireframe diagram to give context. One of our developers might have also mocked up how a menu works, and so they stick in a link to that. Our client might email the link around, and then add some comments on the page. This kind of collaborative workflow is one of our strengths, and it is really important for us to be able to add these various types of content easily.”

Read more on wiki use at Sun and RedAnt in my new book: Wikipatterns. The book contains 8 case studies on wiki use in a range of organizations, and how-to guide for growing a successful wiki in your organization.

Sony Ericsson
Sony Ericsson Developer World WikiThe Sony Ericsson Developer World Wiki is a place for people developing applications using the Java ME application platform and Symbian/UIQ3 pen based interface to get information on how these technologies are used in Sony Ericsson phones and share ideas & information. The home page includes five “house rules” that are excellent guidelines for community members:

  1. Respect the views of others - reminds people to be constructive, cite sources, keep calm if editing gets heated, and offer contributions that benefit the whole community and take into account the contributions of others.
  2. Take responsibility - this guideline lets users know that it’s okay to create new articles, move content when necessary, and make changes that improve the wiki. For example, if a discussion moves away from the initial topic on a page, it’s best to create a new page for the new topic, so that multiple topics can be easily distinguished.
  3. Stay on-topic - this guideline reminds users not to use slanderous, racist, offensive, or unsolicited commercial content on the wiki, as it will be removed.
  4. Use common sense- reminds people that the wiki is a work in progress, and information in it should not be taken as an official Sony Ericsson policy or stance on any issue.
  5. Use English - Sony Ericsson uses English as the official language for the wiki, and uses this guideline to remind contributors.

Carbon Five
Carbon Fiveis a small San Francisco and Los Angeles based company that develops enterprise web applications for clients. They rely heavily on a wiki as well, for both internal use and as an extranet for collaboration with customers. According to Don Thompson, “Each client gets their own “space,” an area that they can collaborate on projects with the team at Carbon Five.”

IBM
IBM DeveloperWorks WikisIBM DeveloperWorks Wikis cover topics like:

  • Lotus Quickr Best Practices,
  • J2EE Systems Management,
  • WebSphere Instructor Wiki,

and a series of Web 2.0 Goes to Work conferences held in Raleigh, North Carolina and Austin, Texas. The space for those conferences has links to video posted on YouTube, a conference podcast, and a resources page for anything demoed at the conferences.

Looking to grow your own wiki use?

If you’re looking to grow your own wiki use, Wikipatterns.comis a toolbox of patterns & anti-patterns, and a guide to the stages of wiki adoption that’s intended to give anyone, anywhere, using any wiki software, a collection of strategies for successfully growing wiki use. It’s also a wiki, which means you can help build the information based on your experiences!Since its launch in January 2007, Wikipatterns.com has grown from 29 to 78 patterns, and most of those have been contributed by the 900 registered users that make up the community as of today.check out the new Wikipatterns book! Check out the newly published Wikipatterns book- a how-to guide for growing wiki use in organizations with practical advice from a wiki expert. (That’s me!)

Here’s what people are saying about the book:

  • “Create an idea-sharing environment where incomplete can be linked together and from this, solutions emerge.” - From the book’s Foreword, by Ward Cunningham
  • “I’m going to recommend this without even reading it! Should be an e2.0 must-read top-shelfer…” - Susan Scrupski
  • “Just pre-ordered this from Amazon. Looks to be a good read and an essential tool in any E2.0 evangelist’s tool kit.” - Scott Gavin
  • “I love it when this happens, a blog I’ve read for ages (devoured some would say) gets published in book format. Needless to say my copy is already ordered.” - Gordon McLean

Have you started a wiki recently? Thinking of starting one? What are your plans for it?

ShareThis Subscribe to Grow Your Wiki

Related Posts:

3 Comments, Comment or Ping

  1. Craig Tobias

    Considerations in Deploying an Enterprise vs. an Internet Wiki

    There is a difference between an enterprise or internally facing wiki (inside a firewall) and that of an Internet based or external wiki (outside a firewall). While the platform can remain the same and the basic purpose of collaboration is the same, it is their application purpose and the types of data collected and maintained on these systems which is different. Enterprise wikis contain team and project type information. This information usually consists of information such as team member, colanders, project statuses, inventories, and processes. Enterprise wiki contain large portions of information for a limited or closed set of people. An Internet based wiki is a wiki which provides information about an organizations good or services to a much larger user base. Internet wikis serve much more in an information sharing, education, and marketing capacity and less in a project management and process documentation capacity than that of an Internet wiki.

    Because there are some differences in these two types of wikis, there are also a number of other items that must be considered when building an Internet wiki versus that of an enterprise wiki. The main factors you will want to address in an Internet based wiki will be:

    • Ease of use
    • Speed (User Response)
    • Scalability
    • Security
    • Content Moderation
    • Skins (Look and Feel)
    • Navigation
    • Metadata

    It is not that these items are not important in an enterprise wiki, they are extremely important but there are a number of items which take priority in an enterprise system such as:

    • Flexibility
    • Plug-ins/Extensions/Adaptors
    • Integration (mashups)
    • Email integration
    • RSS feeds
    • Content change notification
    • Training
    • Job function application
    • APIs

    Again the reason for the differences here is because most people will use the Internet based wiki as a repository for viewing and collecting information on products, technologies/systems and services. The user base will most likely have about a 1-2% user contribution rate, where as in an enterprise wiki it would not be unreasonable to have an 80-90% contribution rate meaning that 80-90% of the users have contributed at least once. So with an Internet wiki the more users you have the higher qualify information you will have. This isn’t necessarily the case with an enterprise wiki where the quality of information will largely be a result of a concept understanding peer review, benefits of adoption, and mainly education.

    With an Internet based wiki you will want to focus on the skins to make sure they adhere to your organizations branding standards. Internet wikis also have the potential for explosive growth as well as vandalism items which are much less of a concern in an enterprise wiki. If an enterprise wiki has scalability or navigation issues you can tell the user base to hold-on changes are on their way. On an Internet based wiki system your users simply don’t come back if they find the site aesthetically unappealing, unreliable, or no responsive enough. Therefore with an Internet wiki system you will want your site to have a very professional and appealing look and feel so that no matter what is contributed it is well presented. This will make visitors less hesitant to contribute to your company’s public collaboration space. You will also want to have a process for moderating content. Removing liable and unseemly content will be important in maintaining an environment that appeals to the greatest number of contributors and promotes participation.

    Enterprise wikis are slightly different in that factors that contribute to the greatest adoptions and collaboration are benefit to a person’s role, education, and a clear contribution strategy. What is meant by this is that people are often willing to contribute but they will say they don’t know where to put something. Having clear information architecture, a method for easily navigating it and educating the users on the basics of the information architecture will greatly drive adoption.

    An enterprise wiki will also need to be much more flexible because it will be used in a much wider capacity than that of an Internet based wiki. For any one organization the wiki might be used to keep track of customers, part number, manufactures, suppliers, shipping, operations, training, and other function required by and organization. So one will want to look at watch features a particular wiki has and in addition how that wiki can be expanded in capabilities this is usually done through plug-ins. Different wikis call them different things such extensions, modules or adaptors. Whatever they are call their purpose is to expand the capabilities of the wiki.

    Since on an Internet wiki some of the main concerns are speed, reliability, and security you will not want to just start adding plug-ins without carefully considering each and everyone. Each plug-in generally expands the command options or feature set therefore that code much be processed before a page can be displayed. The more plug-ins you add the more code that must be processed per-page therefore adding vast amounts of unnecessary will not only slow down the response to the user with each line of new code you must consider the security implications.

    I have deployed several internal wikis at Cisco and have most recently been responsible for the deployment of Cisco’s external wiki.

    http://supportwiki.cisco.com

    Craig Tobias
    Senior Solutions Architect
    Cisco Systems


0 Comments
Post a comment



 RSS of this page

Written by:   Written by:   Version:   Last Edited By:   Modified

This is a wiki for sharing information and collaboration,if u have a feeling of adding something new here,just feel free to make some contribution.i am douyue,u can contact me by sending a Email to:douyuester(at)gmail.com or QQ me:402526772.