| Why Wikis are a waste of time |
May 23, 2006
People keep telling me how wonderful wikis are, how they let people work together in new and creative ways, and how they can harness the wisdom of groups. What a bunch of horse manure!
Wikis are just another in a long, long line of tools designed to help people produce useful work that end up not being all that useful to most people. Deal with it.
Yes, I know all about Wikipedia. I also have serious doubts about its accuracy -- Nicholas Carr does a better job than I do, of explaining why it's untrustworthy.
But, let's get to the meat of the matter. The Wikipedia hasn't been a real "wiki," where anyone can write and edit, for quite a while now. Wikipedia's management decided that to prevent article vandalism they had to "semi-protect" some stories from new, would-be writers.
Thus, when you read Wikipedia today, you'll find some stories, like Dick Cheney's biography, marked with the message, "editing of this article or project page by new or unregistered users is currently disabled."
Jimmy Wales, Wikipedia's founder, however, proposed on May 21 that "that we eliminate the requirement that semi-protected articles have to announce themselves as such to the general public."
And, the difference between Wikipedia and a conventionally edited publication is what exactly?
Here's the point: wikis are just another form of groupware. That's all.
What makes wiki's different, anyway? I think most people would agree that it's a program that enables people to "have connectivity with, not just everyone in your company, but with vendors and customers. By working with teams that are blind to organizational boundaries and technology differences, work proceeds in a more continuous way."
Right?
Wrong.
That's a 1991 quote from an interview I did with Eric Sall, then Lotus Notes director of product management, for a PC Week (today's eWEEK) groupware story.
Ward Cunningham, creator of the wiki and the Eclipse Foundation's director of committer community development, thinks wikis are wonderful. In a recent eWEEK interview with Daryl Taft, he said, "Eclipse is a shining example of the accomplishments of this methodology."
For Ward and company, I'm sure it is great. In my experience, though, people just don't want to bother with changing their work or workflow habits. Unless the workers involved are highly motivated (like the people in the Eclipse Foundation), they simply aren't going to use wikis.
It's not the software's fault. eWEEK's labs people say, for example, that "CustomerVision's BizWiki provides users with a polished set of tools for creating and managing content collaboratively," and I believe them. MediaWiki, the software behind Wikipedia, is widely praised, and I'm sure it deserves it.
The real problem with wikis is the same one that groupware has -- it's a wonderful idea that most people never use.
For example, I really like Notes. No, I really do, and there was a time when I was a decent Notes programmer. Notes enables a team scattered around the country to do otherwise impossible tasks quickly and efficiently. Then there's the great majority of the time, when Notes users move like a slug running uphill.
Collaborative work, no matter what the software is behind it, simply doesn't come easily to most people.
Another problem is the one that Wales and company are running into. It's that, at the end of the day, someone does have to manage and edit the information, the workflow, the stories, etc. At this point, wikis become just another workflow tool.
Sooner or later the people who do that managing, or who pay their salaries, ask, "Why am I going to so much trouble to track work, when I could be doing work." And, that's that.
What finally ends up happening, in all the cases I've personally seen, is that the collaboration tools end up gathering dust.
It's not that people won't work with each other, or that they won't change their methods. They do, and they have. For example, in my own field of technology journalism, email and IM are now how most of us "talk" and work together on stories and publications. It's also how open-source software is created.
The greatest example of collaborative work I know of is the Linux operating system. How do the developers work together? With that oldest and cheapest online community collaboration tool -- the Linux kernel mailing list.
I think Linus and company may be on to something.
So it is that wikis and groupware programs like Notes continue to sound like great ideas to improve accuracy, workflow, and all that other good stuff. But, darn it, they really, really don't work all that well.
You really want to get work done with a group of people scattered from hither to yon? I recommend a mailing list running off the open-source Mailman MLM (mailing list manager).
-- Steven J. Vaughan-Nichols
Do you have comments on this story?
Talkback here
NOTE: Please post your comments regarding our articles using the above link. Be sure to use this article's title as the "Subject" in your posts. Before you create a new thread, please check to see if a discussion thread is already running on the article you plan to comment on. Thanks!
(Click here for further information)
|
|
|
7 Advantages of D2D Backup
For decades, tape has been the backup medium of choice. But, now, disk-to-disk (D2D) backup is gaining in favor. Learn why you should make the move in this whitepaper.
4 Legal Reasons to Control Internet Access
The Internet is obviously a valuable resource for many organizations. However, many are exposed to legal liability concerns because they fail to control Internet access. Learn if you're safe in this white paper.
Rapidly Resolve J2EE Application Problems
Whether you are in the process of building J2EE applications or have J2EE applications already running in production, you must ensure that they deliver the expected ROI. Learn how in this white paper.
Load Testing 2.0 for Web 2.0
There are many unknowns in stress testing Web 2.0 applications. Find out how to test the performance of Web 2.0 in this white paper.
Build Better Games Online
For the game infrastructure providers, life is complex. Making money from games has become more complicated. Why? Find out in this white paper.
Building a Virtual Infrastructure from Servers to Storage
This white paper discusses the virtual storage solutions that reduce cost, increase storage utilization, and address the challenges of backing up and restoring Server environments.
Gaining Faster Wireless Connections with WiMAX
Welcome to what is quickly becoming the hyperconnected world where anything that would benefit from being connected to the network will be connected. Learn more in this white paper.
Is Your Desktop a Security Threat?
The new wave of sophisticated crimeware not only targets specific companies, but also targets desktops and laptops as backdoor entryways into those business’ operations and resources. Learn how to stay safe in this white paper.
Increasing SAN Reliability by 100 Percent
Storage area networks (SAN) are a strong part of storage plans. Learn how to increase your reliability and uptime by 100 percent in this case study.
|
|
|
|
|
news feed