Feed Sign in with OpenID OpenID

Simon Willison’s Weblog

Ward talks Wiki

Artima have published the first installment of Bill Venners’ Conversation with Ward Cunningham, which focuses on the Wiki. When asked how readers can get a bigger picture of what is going on in a Wiki, Ward responds with this:

The first thing you have to understand is that because we made wiki easier for authors, we actually made it harder for readers. There is an organization there, and the organization can be improved, but it isn’t highly organized. So the feeling for a reader is one of foraging in a wilderness for tidbits of information. You stumble across some great ones and you say, “This is fantastic, why doesn’t somebody just make a list of all the great pieces so I don’t have to look at the rest.” In other words, “Why doesn’t somebody organize this so I can get answers to my questions quickly?” Sooner or later they realize, “Gee, I could do that.” They put in a month or two of finding what they care about, and then they make a page, which is their take on what the organization of wiki is.

I think this goes a long way to explaining why a lot of people dislike the Wiki format.

This is Ward talks Wiki by Simon Willison, posted on 22nd October 2003.

View blog reactions

Next: Knoppix

Previous: A List Apart Again

4 comments

  1. Because they prefer to have a readily consumable source of info? Such a thing is certainly useful as a reference, but not so useful for retention, or for collaboration.

    If you read a wiki while wishing for an article, you'll be disappointed. By the same token, if you read an article while wishing for a discussion, you'll be disappointed.

    Many times I have read something, and felt very near to understanding it, but the author is not available to me for comment (or their is no single author that could answer the question). Here, the wiki excels.

    Very often, people create a document when what's needed is understanding. Moreover, this understanding can most easily be achieved through dialog not available when receiving a broadcast.

    I haven't read Ward's interview yet, but I can say that a wiki can often capture what would otherwise not have been available in a single, if messy, source.

    This mess yields a market for a well-written book covering what's been learned. This serves those that need something for consumption.

    I buy books, and read other such refined materials.

    But I also contribute when and where I can. Progress is not tidy.

    Jeremy Dunck - 22nd October 2003 20:24 - #

  2. I find that the software behind wikipedia and metaweb is much easier on the reader than any other. To a reader that has no intention of ever writing/editing, it feels very much like a normal site. It's amazing how much of a difference it makes to remove CamelCasedLinks.

    Patrick Lioi - 22nd October 2003 20:51 - #

  3. Maybe a wiki could use something like Amazon - let users "rate" pages, and also track which users go to which pages. Then you could give feedback to visitors like: "people who rated this page high also liked these pages..." and "people who visited this page also visited these pages most frequently...".
    You could alternatively just indicate similar information with icons, see this paper.

    Another option might be to encourage wiki authors/designers to improve the style of the site: use navigation sidebars, CSS, and a "recent highlights" column (like a blog) on the wiki's first page.

    Lastly, often the edit page link is often hidden away at the bottom of the page where few notice. That could be made more prominent, and you could embed "edit" or "comment" buttons in the page. People are more likely to hit a "comment" button (like in Zwiki) than an "edit" button anyway.

    wiki - 22nd October 2003 20:51 - #

  4. I find Wikis are good as a central site for sharing information.

    For example, on our project at work, we use it as a central repository of information including:

    • Convenient links (e.g. bugzilla, cvsweb, etc.)
    • Documentation such as the non-automated steps in our code push and testing processes.
    • HOWTOs

    Joe Grossberg - 23rd October 2003 17:48 - #

Comments are closed.

Previously hosted at http://simon.incutio.com/archive/2003/10/22/wardTalksWiki

A django site