ALA TechSource Logo

ala-online-v1.jpg

 
curve Home spacer Publications spacer Subscribe spacer Blog spacer About  
    

Building a Better Beta

Submitted by Michelle Boule on September 8, 2006 - 8:28pm

Every day companies are coming out with new tools to reach their users on the Web. Many companies have learned that rolling out products before they are completely formed—in beta or even in alpha mode—can save them development time and money. By giving their customers an early look at a product, companies are empowering customers to use the tool in new ways and are providing them with an opportunity to ask the company for functionality that product developers may never have considered.

Companies in Beta
Meebo, a robust, widely used instant-messaging (IM) service is still in an alpha phase. Meebo allows users to sign into more than one IM account with more than one IM provider at the same time, so all of a user's accounts appear together on the same screen. For people in restrictive IT environments, there are no downloads when using Meebo.

Google, the hero and bane of many, has been extremely successful using beta products. Some of its beta products are Gmail, Google Video, Froogle, and Google Catalogs. Almost everything Google develops comes out in a beta version before the "real" version appears.

LibraryThing enables users to access their catalogs from their mobile phones.LibraryThing is a service near and dear to the hearts of many librarians who have long wanted a catalog of their very own. LibraryThing, a beta product that celebrated its one-year anniversary on August 29th, holds more than 4 million cataloged books and has 70,000-plus users.

Flickr is in gamma mode, and with all of its functionality, one has to wonder if it is ever going to be "fully" launched. Flickr began as a photo-sharing site, but it has become a community.

Defining Beta
All of these companies and their software have something in common. They are successful. They have followers. Their customers are loyal. Customers are given the chance to test products and make suggestions. They are let in, sometimes from the ground up, and that gives people a sense of empowerment and ownership. Going beta has become less of what you roll out and more of just what you do—a mind set. You could even call it a belief system.



How can libraries build beta products and services and develop their own followings?



Libraries Building in Beta
The MIT Libraries have released a whole set of beta products for their users. LibX–MIT Edition is the MIT take on the library Firefox extension. It allows users to search Google Scholar, MIT's Barton Catalog, the online holding via SFX, and more. They also have a similar product that uses an MIT-specific Greasemonkey script to look up things on Amazon in the libraries' catalog.

MIT Libraries' Dewey Research Advisor for Business and Economics

As a non-business librarian, I am especially impressed with their Dewey Research Advisor for Business and Economics; it's something I would like to have at my library. Using it, in an "Ask Jeeves" style, the user, for instance, can query: "Where can I find company reports?" The widget then returns starting points for research.

Those working on these beta projects at MIT Libraries also list new beta products they are planning to launch later this year. This is a wonderful example of being transparent with your users.

Casey Bisson has been building a WordPress-based OPAC for Plymouth State University's Lamson Library. Casey's WPopac looks like a blog with item entries, but it has some added features that make it more innovative and accessible than traditional catalogs. It is simple in design, aesthetically pleasing, easy to understand, and retrieves items relevant to the search.Lamson Library's (Plymouth State University) WPopacThe WPopac also has all the added extras from WordPress, like RSS feeds, comments, and spam filters.



Building beta in your library does not have to revolve around new technologies. The endeavor can also take the form of new programs or initiatives. Many libraries have created Dance Dance Revolution (DDR) nights for teens. These nights usually include a dance off, food, and a way for the students to talk about how much they liked the experience. Building loyalty with your users requires a way for them to provide feedback about your beta service.

Staff members at The Public Library of Charlotte and Mecklenburg County (PLCMC) have created a teen space—the Library Loft—a place for teen users to engage in teen-oriented offerings, like gaming nights, and/or to participate in a program that provides students with the opportunity to learn how to create claymation movies in a blue-screen studio.

The amount and variety of programs offered through this fun and user-centered approach is amazing. These are the kinds of programs that any library could plan with the right "beta attitude." You must be willing to try, fail, and try again. PLCMC did not suddenly have this level of innovative service for teens overnight.

Like the successful companies, PLCMC offers many ways for the teens that use the library's space to give feedback. PLCMC has an advisory council (made up of teens) and multiple MySpace accounts.

PLCMC's teen space, the Library Loft.

The focus of the Library Loft is not necessarily the library, but it is about putting things teens want and use in one space. PLCMC has built a place, virtually and physically, in which teens can be empowered, feel ownership, and believe in its worth.

Building a Better Beta
I am not advocating for libraries to conduct half-formed programs with little thought or planning. Building beta is more about flexibility and allowing the participants—not the creators—to redefine the meaning of the service. Planning beta is about allowing for failure, success, and change.



Providing services in beta also means that we must trust our users as they trust us. Transparency must go both ways. We must be honest and transparent, so that users can provide constructive and useful feedback.

How would our libraries look if we treated everything as a beta product? Would we be more willing to try new things if we knew that bugs could be fixed in the next installment? Will our transparency inspire trust in our users and make them believe in us?Technorati tags: beta, Google beta, librarians, libraries, library catalog, LibraryThing, library 2.0, Library2, library2.0, Meebo, OPAC, web 2.0


Comments (5)

I think adopting a "beta

I think adopting a "beta mindset" is a great approach for libraries. Many libraries already have a well developed process for pilot projects. Having a beta mindset goes beyond the pilot project approach and moves towards an attitude of continuous improvement, listening to customers, and adapting and changing. It's important to remember that while there are lots of people are comfortable with "beta", there are also lots of people who not happy with beta versions. Some people are much happier with stable interfaces and don't want to encounter "under construction" and bugs and beta versions. How you successfully role out beta services can be very different depending on your audience and their expectations.

Eric is right. If we start

Eric is right. If we start listening to our users, they are going to expect us to actually do something! I think this is a good thing. I think some older institutions have trouble with transparency. Going beta means giving up some level of what an institution might consider "privacy," but does it really matter if our patrons know a few of our inner workings? I think it does not. The payoff is too high. Tim - I think the backlash against beta is very prevalent in academia. Beta means getting away from the tried and true research model we are used to having in Higher Ed.

I think this is dead right:

I think this is dead right: "Going beta has become less of what you roll out and more of just what you do—a mind set. You could even call it a belief system." So here's my belief. I see a certain backlash against beta—against the trendiness of the term. "Doesn't beta just mean you're not done? Be done already." I see it quite differently. Beta is my license to play, experiment, screw up and create. We all know sites change--Paul Graham's argument against "beta" is that it's redundant. I'm saying more than that. Yahoo changes; I'm saying that LibraryThing may change *drastically*. It may even be broken now and then, on the way to being better. It's a notice to users—we're changing the floors underneath you all the time, watch your step and let us know what you think. You speak of fixing bugs in installments. Even though LibraryThing now has the money for a real development server, we don't have one. We work on the live server always. It's like juggling knives. Keeps you alert. Here I'm supposed to say "I'm not suggesting libraries do this." I am. Now, LibraryThing can afford to alienate the 10% of users that attitude disturbs. Libraries need to be a little more careful. But not much, I think. I'd love to walk into my library and see "under construction—always." PS: We're up to 5.5 million books now--a rate of more than 1 million/mo. Beta works.

This is what the developers

This is what the developers of open source software have been doing forever. Release early release often. Let the people who use the software test for bugs.

This is a great post! How

This is a great post! How would our libraries look if we treated everything as a beta product? Our libraries would be full of contiguous research projects and repositories if we used more betas in different departments. Would we be more willing to try new things if we knew that bugs could be fixed in the next installment? People love testing brand new things. Sometimes the bugs can lead to happy accidents so it is mutually beneficial for library developer and community user. Will our transparency inspire trust in our users and make them believe in us? Possibly, but, listening to customer need makes people believe in your service to them.