Sharing the Bad

December 20, 2007

Meredith Farkas’s blog post a few days ago (Sharing the Bad Stuff, Learning from Failures) was a lot to take in. She was absolutely right: we need to share failures in the workplace. The library community needs to hear what doesn’t work in addition to what does. We need to learn from each other, good or bad.

Expressing the bad isn’t always easy, though. She wrote that “failure isn’t sexy. Disclosing problems isn’t good for your brand.” How true! Transparent libraries are still rare. If you speak on behalf of an organization, you have to watch your tongue. Even if you speak independently, you often feel obligated to err on the side of caution.

As a blogger, I share what interests me. It’s an added benefit if I happen to excite other people about things I’ve found or imagined. I usually write positive stuff because that’s what I want to think about. I’d rather discuss what’s possible than dwell on the negative or complain about office politics. But it is a bit misleading, to be sure. Life is never 100% good and 0% bad. Not everything is wonderful.

I’ve recently had difficulty in my workplace, for instance. A lot of difficulty. Should I share everything? Maybe for the good of the library community, I should. It would let others learn from the problems I’ve encountered. But at what price? I’m one of those “bottom-up upstarts who revolutionized the way things were done at their libraries” that Sarah Houghton-Jan mentioned this week (although I’m not so delusional to think she was referring to me). I championed a tremendous amount of positive change in recent years. In the last few months, however, I hit a wall. Oh, who am I kidding? The wall fell on me. Three times. Sharing the specifics on the Internet might only make things worse locally, but I’d be remiss not to admit there are problems, conflicts, and frustrations.

I still want to produce positive change within my organization. Recent events make that much more difficult, but I’m still hopeful. I like Alan Kirk Gray’s suggestion* of a Library Failures Wiki. It could be a valuable tool allowing us to share common problems. More people might contribute and more experiences might be exchanged if anonymity was part of the forum. Our objective wouldn’t be to embarrass our libraries, after all, but to help improve them. Getting publicly specific about failure isn’t always the best course when the culture in which you work is not yet transparent.

___
* which I first saw in Meredith’s post

Advertisements

Learn More: Wikis

December 17, 2007

[This is one in a series of self-paced discovery exercises for library staff venturing into the social web.]

If you gather a committee, write a draft document, and solicit feedback, you might receive scores of revisions in email and on paper. Compiling all those changes back into a single coherent document could be a long and tedious task. On the other hand, you could create a wiki. That would enable everyone to work on the same collaborative document and compile changes on the fly. A wiki is basically a read/write website open to anyone with permissions.

Wiki is a Hawaiian word meaning “quick”. Ward Cunningham, who developed the wiki concept in the mid-1990s, named his WikiWikiWeb program after the “wiki wiki” shuttle bus he encountered at the Honolulu Airport. It seemed the perfect name for a web platform intended to give users quick access to editing tools.

The largest and most famous wiki, of course, is Jimmy Wales’ Wikipedia, where thousands of contributors have complied a global encyclopedia with more than 2 million English language articles (and even more than that number in other languages). Most other encyclopedias publish articles written and vetted by experts; Wikipedia entries are created and edited by anyone volunteering the time and effort. Accounts aren’t even required! Readers add information, correct typographical and grammatical errors, and contribute to a worldwide public-review process that is much faster than traditional peer-reviewed documents.

Meaning for libraries

Here are three ideas for libraries to consider.

  • Accuracy. Information in a wiki is mostly accurate, but who knows? How’s that for a ringing endorsement? Wikipedia, the largest of all wikis, has been studied* and found to be reasonably accurate. It might not be peer-reviewed by recognized authorities, but it is read and continually re-edited by thousands of people. There is vandalism, to be sure, but most people don’t make changes unless they are confident of their facts and they are more likely to contribute good information than bad.
    My opinion: A site like Wikipedia is a reasonable place to begin a search. You can pick up a few facts and grasp an understanding of a subject. However, it probably isn’t the best place to end a search. Don’t prohibit its use as a resource, but encourage people to supplement it with other sources.
  • Collaboration. Libraries increasingly use wikis within the profession.
    • Wikis created by the international library community provide ample room for collaboration toward common goals.
    • Library conferences have begun providing wikis. Planners, speakers, and attendees compile information and experiences without the need or delay of editors.
    • Intranet-based wikis may be helpful within an organization. University libraries have been active in this regard. I recently began a manual-writing project on an internal wiki open to supervisors at my public library. Such wikis can foster the participation of many people without the usual drag of long committee meetings.
  • Patrons. Wikis can be created for library patrons. Bookclubs and teen programs might help construct and/or benefit from them. A “Community Places” section seems custom-made for residents who know their area better than anyone. A wiki can give them a venue for sharing their knowledge with others.

Learn more by participating

Nothing demonstrates the concept of a wiki better than just diving in. Here are a few explorations I’d encourage you to try this week.

  • Go to Wikipedia and search a few topics that are near & dear to you. Topics might include a town or a hobby you know well.
  • Read over each article. Look at the organization and note the writing style. This article was probably not written by a single person. Several people likely compiled it over months or years.
  • Click the “History” tab to see past activity on the page.
  • Click the “Edit this page” tab to open the page’s editing functions.
  • Browse the source code to familiarize yourself with the text and format code of this particular wiki. Wikipedia was built on MediaWiki software. Other wiki platforms may use a different mark-up language.
  • If you honestly have something to contribute, edit or add to the page and save it. That’s how wikis evolve: one reader/writer at a time.

  • Bonus: If you or your library are interested in creating your own wiki, there are many software types available. Shop around for the best fit. Some services charge, others are free; some are open to public view, others are private; some host pages for you, others allow software downloads to your server. Here are three examples: MediaWiki, PBWiki , WetPaint.

Collaboration. Participation. It’s all part of the social web.


* most famously by Nature magazine, Dec. 15, 2005.