Slow Growth Web App

March 31st, 2010 by Jed

Companies like 37signals remind everybody that you don’t need overnight success. Their oft-repeated story about Basecamp is that it took almost a year to start generating enough revenue to pay the bills.

Today ends a record month for WebSort. We’ve had more new sign-ups, more studies created, and more purchases than any other month on record. And it’s taken us eight years to get here. If you would have asked me in 2002 what place WebSort would have on the internets, I’d have responded with something like:

Oh it’ll be long gone. The internet will be totally different by then. People won’t be browsing through website hierarchies to find information.

After I presented an early version of WebSort at the 2002 UPA conference, an employee from a very large software company approached me, made a feature request, and ended with “then you’d have something we’d be interested in acquiring.” I hadn’t even finished my undergraduate degree. WebSort was my first foray into Flash. And PHP. And MySQL1.

I distinctly remember having a phone call with my father (my co-developer) and telling him:

If they offered us $10K, I’d take it.

I honestly didn’t think there were more than 100 people in the world that’d be interested in paying money for an online card sorting application. But we kept chugging along. Each year we got more customers, higher Google rankings, and fewer bugs. We even got a few worthy competitors2.

So thank you to all our customers. Some of you have been with us for the long haul. I have no idea what WebSort will look like in another 8 years. But for now, we’ll keep making tasty web apps.

  1. version numbers are much higher, but these 3 same technologies are still running the show []
  2. Dear future web-preneur: I don’t care how small you think your niche is. Somebody out there is or will be fighting you for it []

Card Sorting, Prototyping, and Remote Research

February 10th, 2010 by Jed

For a limited time, you can get a free Rosenfeld Media book when you make a WebSort purchase.

On the heels of Todd Zaki Warfel’s Prototyping: A Practitioner’s Guide, another great Rosenfeld Media book has been released. It’s Remote Research: Real Users, Real Time, Real Research by Nate Bolt and Tony Tulathimutte.

Prototyping by Todd Zaki Warfel

Prototyping by Todd Zaki Warfel

Card Sorting by Donna Spencer

Card Sorting by Donna Spencer

Remote Research by Nate Bolt & Tony Tulathimutte

Remote Research by Nate Bolt & Tony Tulathimutte

What do these books have in common with Donna Spencer’s Card Sorting? They all mention WebSort or the people behind it. That, and because we love the practical approach of Rosenfeld books, is why we’re excited to announce a new offer. For a limited time, you can get a free Rosenfeld Media Book when you make a WebSort purchase. Check out the details here.

In the case of Prototyping, Todd mentions a conversation we had a couple years ago:

Jed shone some light on something that had been sitting there all along– prototyping as a way to work through your own designs.

I can’t take full credit for the idea, since it really came out of my experience with former grad school professor Chris Conley (who is now also a part of LimeChile). Chris showed us that traditional product designers don’t always sketch ideas of what they already have in mind, but rather they sketch to bring ideas to mind and work them out. Should that corner have a chamfer or radius? Let me sketch it and see.

I realized that same approach applied to the interactive prototyping work I was doing- the type of work that at the time was thought of as something you hired a developer to do once the designer had already specified the details. I’m glad that’s changed as more interaction designers have picked up the skills to actuallymake stuff beyond flowcharts. Even if you don’t dabble with Flash or Javascript, you can find a developer and get them involved early to help you work through little bits and pieces of a design without knowing exactly what it is.

It is this kind of great practical advice that you’ll find in all three of the books that WebSort has available, and we’re really excited to share them with you. So sign up or sign in and get reading!

Update

2010.02.17 – We’ve received such a great response from this promotion that we have decided to keep it going indefinitely. Yes, you read that right – from now on, any WebSort purchase will get you a digital or paperback copy (or both!) of one of the three Rosenfeld Media books listed above. No more ‘limited time’. So if you play your cards right (bad pun intended), you could end up with a free copy of all three. Nice …

Types of Card Sorts

January 26th, 2010 by Sarah

So you’ve decided that you need some user feedback on how to organize your information, and you think that a card sort sounds like the way to go. Now what?

There are different ways to set up a card sort that will affect the kinds of results that you get. How to set it up depends on your situation and your goals. The following is a list of the most common types of card sorts to run and the best times to use them:

Open

The most fundamental of card sorts, an open sort simply provides the participant with a list of items to be sorted into groups/categories. The number of categories, labels for the categories, etc. are all up to the participant. This type of card sort is by far the best place to start when trying to obtain user feedback on the organization of your items (whether for a website or for general information architecture purposes). Even if there is an existing set of categories for the items, beginning research with an open sort ensures the best quality user feedback (see Card Sorting: Current Practices and Beyond).
Open Sort ImageThere are some pitfalls to be aware of. First of all, when asking participants such an open-ended question, you have to be prepared to get a lot of different answers. To make sure that the information you get is going to be what you need to make good decisions, you need to be very clear in your instructions what the study is for (website menu structure? retail catalog organization?) and you need to cull good participants. Think about who is going to use what you are trying to build and ask them. Don’t just post a link to your study on Facebook and think this is going to do the trick (unless your target demographic is your set of Facebook friends, of course).

One last thing – don’t get too many participants. This may sound odd, but it is backed up by some research. Also, each participant is going to submit unique results. Names of categories don’t often match exactly, items may differ widely in where they are put – in short, you will have a lot of information to sift through that isn’t going to be quickly assimilated. The more participants you have, the more data you will have, and it goes up exponentially. If you’ve worked hard to have quality instructions and quality participants, you won’t need all that many of them to get some good data. In this case, less is more.

To conduct this type of sort using the WebSort interface, simply do not enter anything into the Categories tab of the Study Manager.

Closed

Closed Sort ImageUnlike an open card sort, a closed card sort does not allow participants to make any decisions about the categories into which the items are sorted. Instead, the study administrator provides a pre-existing set of labeled categories into which the participants are asked to place items. While we strongly caution against using a closed sort without first obtaining user feedback with an open sort, a closed sort is excellent for validating results obtained from previous user-based research. It is also useful when adding new items to an older, previously user-validated structure.

To conduct this type of sort using the WebSort interface, enter in the desired labels/titles of the pre-defined categories in the Categories tab of the Study Manager. Be sure to uncheck the ‘Allow creation of new categories’ box at the bottom of the Categories tab.

Mixed

This type of card sort combines the flexibility of user-defined groups and names with the ability to present the participants with a pre-existing set of labeled categories. Participants in a study are given a set of administrator-defined categories, just as in a closed sort. However, unlike a closed sort, participants can rename the groups, delete them, and create new ones.

Some researchers consider this type of sort a ‘guided’ open sort, as the existing categories provide information to the participants as to how the items might be perceived or how an existing organizational structure may be set up. A mixed sort is very useful when you have new items to be added to an existing structure that is old enough to need fresh feedback. And when combined with clear instructions, it can be used when you want to limit the participants to a certain number of categories but allow them to provide the names for them.

Mixed Sort ImageTo conduct this type of sort using the WebSort interface, enter in the desired labels/titles of the pre-defined categories in the Categories tab of the Study Manager. This time, be sure to check the ‘Allow creation of new categories’ box at the bottom of the Categories tab.



While there are other types of card sorts out there (which we will post about in the future), these are the tried-and-true methods that provide the foundation of good card sorting. And don’t forget – you can try them all out for free at WebSort.net. ;)

Introducing PlainFrame: Clickable Menus for Navigation Testing

January 11th, 2010 by Jed

We’re excited to announce a new project we’ve been working on. It’s not publicly available yet, but we’re looking for some good UX/IA peeps to help us shape it into a polished app.

After Card Sorting

You did an open sort to understand how your users think about your content. You did a closed sort to hone in on your early insights. You’ve sliced and diced the results and added your own expertise and intuition. You’ve crafted a brilliant new navigation system to propose to your project manager. But now what— go live and check the site analytics in a month?

You know you should test the navigation in context, but haven’t had a good way to do that. Current solutions have people click through a flat tree structure, but that’s not how users experience navigating a site.

Location matters. That’s why we’ve been building PlainFrame.

PlainFrame Logo

It allows you to easily and quickly put your navigation structure into a clickable “white site.”1 And we not only record the interactions as data for analysis, we let you play them back so you can see how the user interacts with the site dynamically.

Beyond Tree Testing

Site structures have multiple starting points and subdivisions. Real menus have position and size and interaction. These design elements play a huge role in the ultimate usability and ease of navigation for your site. PlainFrame puts your site structure into the context of real, clickable menus.

See what happened

Site analytics and click paths are like punctuation; they show you the entrance and exit of each page, but not everything in between. PlainFrame records every mouse move so you can replay any test as it happened. Or you can watch it at 8x speed. Combining stats and data with viewable replays gives you the best of qualitative and quantitative worlds.

Sound interesting to you? We’d love it if you’ll join us in shaping the public version of PlainFrame. Check out the home page or jump straight to the sign-up form.

  1. Some ideas just take a long time to develop, even in the high-speed web 2.0 world. The idea for PlainFrame, and my introduction to term “white site,” came from a hallway conversation at UPA 2003 between me, Janice James, Carol Righi, and WebSort co-creator Larry Wood. []

How long will this take? – Planning for Participants

January 4th, 2010 by Larry

How do I estimate how long it will take participants to complete my study?

Often in your instructions, it can be helpful to include “this will take approximately…”. In order to have that statement be based on data, rather than intuition, we did a statistical regression study on the relationship between number of items and mean completion times, using a sample of 25 studies. The relationship is:

Mean completion time = .34 (number of items) + 4.

For example, if you have 50 items in your study then Mean completion time = .34(50) + 4 = 21 minutes

Of course, all the standard disclaimers apply: your ridiculously long item descriptions might slow people down, or having 250 items might force your participants into reckless speed-sorting mode.  But this equation is definitely handy to have as a rule of thumb.

Once you actually have your study up and running, you can get the actual completion times from the WebSort Study Manager. Just go to the Results tab and choose Other Downloads from the dropdown menu and download the Items x Participants table. At the top of each column (starting the second one), you will see the Participant ID, and underneath that the date & time they took the study (second row) and the number of minutes it took them to complete the study (third row). Using this information is of course the best way to get an idea of how long it will take!

For other helpful tips and answers on how to set up and run a quality card sort study, check out our new FAQs page.

Before Card Sorting: User Input on Labels

December 7th, 2009 by Jed

Labels are a vital but often glossed-over element of successful information architecture. Designers (or worse yet, Department Managers) come up with their own labels and stick with them. A University of Minnesota grad student shows us why we’re missing out.

There’s a big gap between staring at the results of a card sort and launching a new and improved information architecture. Fortunately there are several tools and techniques to help you translate your results into usable navigation. But even experienced designers sometimes skip two other important gaps between a card sort and the user experience: what content to include, and what labels to display. Both of these questions need to be addressed before you run a card sort.

The earliest working prototype of WebSort (circa 2001) required participants to complete two distinct steps. First, they were shown long descriptions of items (which represented a feature of an application, or the content found on a page) and asked to provide a short label for each item. Then they continued on to a card sort of those items, which now showed the labels they provided. We thought this was fantastic.

Turns out, not many other people did.

As development of WebSort progressed, the whole feature was scrapped. This summer when I chatted with our long-time clients and card sorting experts at UPA, I was reminded of the importance of content labeling. Two months later, Jakob wrote about a similar issue of avoiding bias of terminology matching. Finally, Josh Carroll contacted us about a labeling study he was planning, and we were happy to provide a bit of technical support and consultation.

Below are links to a short case study of Josh’s experience, as well as a much longer paper. Let me just highlight one of the unexpected gems:

Some … responses were long, rambling narratives that would never be used on a website. However, the lengthier labels provided more insight into participants’ vocabulary and context.

Just as the organization of items in a card sort does not equal a perfect final web site architecture, the labels provided by users don’t need to be perfect usable link text; the real value is in getting a better understanding of how your users think about your content.


You can download the 5-page and 25-page versions of Josh’s report below. Josh is a Senior Usability Consultant at the University of Minnesota. You can contact him at carr0234 at umn dot edu.

Case Study – User Input on Labels (short version, pdf)

Case Study – User Input on Labels (full version, pdf)

Crowdsourcing our logos via crowdSPRING

November 4th, 2009 by Jed
flaming lime

The company behind WebSort is Lime & Chile Productions (how we came up with that name is another story). Until recently, Lime+Chile didn’t have a homepage, let alone a logo. Our team has some strong design background, but none of us is a proper graphic designer. And all the proper ones we do know are too busy to help right now! So we looked elsewhere for some ideas.

That brings us to crowdsourcing. I’m fascinated with the trend. Card sorting itself is a form of crowdsourcing. So we decided to give fellow Chicago-based crowdSPRING (cS) a shot.

In addition to a Lime+Chile logo, we asked designers to come up with logos for our three applications. The plan was to choose the set of 4 logos that worked best as a family. In the end, we picked one submission for our three apps, and plucked the Lime+Chile logo from a different designer (cS allows you to give out more than one reward).

If you submit a project to cS, don’t get discouraged by early entries. Above all else, provide feedback — that’s what gets your submission count going. And work to make that feedback clear and directional; keep your waffling behind the scenes! If your experience is anything like ours you’ll be very pleased with the end result. You can also check out our cS project page.

Finally, unlike some other related services, cS doesn’t restrict direct communication between the buyer and seller. Now we can follow-up with our winning designer and have him design the logo for our next app (hint hint…)

How many participants are needed for reliable results?

October 19th, 2009 by Larry

Editor’s Note: This article was originally presented as a poster at UPA 2004.  It was also previously published on our blog on December 19th, 2007.  We recommend that you also review Jakob Nielsen’s response.

Tom Tullis, Fidelity Investments, Inc.

Larry Wood, ParallaxLC

Introduction

As card sorting has become more popular, several methodological questions/issues have arisen, such as the effect of instructions on participants, the differences in results from in-person vs. remote studies, and the number of participants needed for reliable results.  This report addresses this last issue (i.e., how many participants are needed for a study to produce reliable results).  The study was conducted online by the Usability Department at Fidelity Investments, Inc.  A total of 46 cards (items) were used in the study, many of which represented services offered internally by the the Usability Department, such as prototyping, usability testing, and card-sorting. Categories were not predefined; each user created and named their own categories (considered an “open sort”).

A total of 168 employees participated in the card-sorting study. From their data a similarity matrix was created, showing the frequency with which each pair of items was placed in the same category across all 168 participants. Therefore, the maximum similarity was 168 (all of the participants placed those two items in the same category), and the minimum was 0 (none of the participants placed the two items in the same category.

Data Analysis

The similarity matrix referred to above is the basis on which a statistical cluster analysis is performed, the result of which effectively “averages” the categorization accumulated across a set of participants. The resulting cluster analysis is then displayed as a hierarchical tree structure (known formally as a dendrogram), which shows clusters of similar items on which organization of content in a web site can be based.

The major goal of our research was to assess the degree of similarity of an organizational tree structure derived from random samples of participants to a structure based on the full set of 168 participants. This could then be used to estimate the minimum number of participants needed to produce an effective organization. As a means to that end, correlation coefficients were calculated between the similarity matrices for each sample size and the matrix for all 168 participants. The assumption is that the more similar the trees, the higher should be the correlation between the similarity matrices on which those trees are based. Thus, correlation coefficients between the sample similarity matrices and the full similarity matrix were calculated for 10 random samples each of sizes 2, 5, 8, 12, 15, 20, 30, 40, 50, 60, and 70 participants . A graph of the resulting mean correlation coefficients is shown in Figure 1.

Figure 1. Correlation coefficients for various sample sizes, with error bars.

As shown in the graph, the relationship between the sample size and the average correlation is a negatively increasing function. Thus, the increase is more dramatic at the smaller sample sizes so that as the size increases beyond 20-30, there is little increase in the size of the correlation coefficient. Also note that the variance of the values, as indicated by the error bars, is much greater for the smaller samples.

An important question is how the function shown in Figure 1 relates to the similarity of the actual tree structures as a function of sample size. One practical implication is that the structures derived from sample sizes above 30 are very similar to that derived from the full set of participants, while those based on smaller sample sizes are increasingly different with smaller sample sizes. To the extent that this is true, it would have implications for determining the minimum number of users needed to obtain valid information.

Conclusions

A general conclusion that can be drawn on the basis of this research is that it may not be cost effective to spend resources to gather information from more than 20-30 participants in a card-sorting study. However, it is important to note that even the trees based on the smallest sample sizes are probably closer to the one for all 168 participants than might be obtained from speculation by a designer who is not a potential user of the content or application for which the organization is being developed. As always, we must exercise appropriate caution in generalizing results from one study. Results will obviously differ as a function of the homogeneity of the participants in a sample and such things as the instructions given to the participants for the card-sorting task.

RE: “Card Sorting: Mistakes Made and Lessons Learned”

October 6th, 2009 by Larry

(this post originally written and published on September 17th, 2007)

I enjoyed Sam’s article and agree with most of it, but I’d like to take issue with two points. The first is the statement

Card sorting certainly can provide input into an organization system—what content goes together—and a labeling system—what to call things—but it’s got very little to do with a navigation system or a search system.

Taken at face value, the statement implies that a coherent organization of a body of information has little or no connection to navigating through the information. I respectfully disagree with that conclusion. Admittedly I’m not aware of any published studies specifically directed at the relationship between organizing and finding. However, my experience leads me to believe that organizing and categorizing a body of information according to the way people think about it will have a positive effect on their being able to navigate through it.

My second disagreement is with the statement

I’m no statistician, and neither are most usability professionals. So, frankly, I avoid statistical analysis methods that I cannot explain to others.

This is representative of a number of similar statements I’ve seen recently, directed against the use of Cluster Analysis and their attendant dendrograms (tree diagrams).

A dendrogram can simply be characterized as a kind of “average” of the way a group of participants have organized a set of content items in a card sorting task. Most people don’t have to be “statisticians” to understand the concept of an “average”. A dendrogram has all the advantages (e.g., one number or set of numbers used to represent something about a number of individuals) as well as all the disadvantages (e.g., no one individual’s behavior may match the average, exactly) of any average. For those reasons, we should never resort to an average as the sole source of information used to make decisions. However, that’s not a solid argument for avoiding quantitative methods altogether.

In addition, simply because a person doesn’t understand all of the calculations that go into the creation of a dendrogram, doesn’t mean they can’t find it a very useful tool in understanding the results. Perhaps a relevant analogy would be the pervasive use of weather maps.

In spite of the fact that dendrograms can look overwhelming they are very useful tools for making sense of a card sort. We will be writing more here soon about how to make the best use of your card sorting data.

RE: Sunlight Labs & the FCC

October 5th, 2009 by Sarah

Here at WebSort, we have the chance to take part in a lot of great initiatives and endeavors.  Recently, we had the opportunity to work with the designers at Sunlight Labs, “an open-source community … focused on the digitization of government data and … making government websites easily accessible” (read more).

Having slogged through more than my fair share of government websites in the last few years, I decided to take a quick look at some of the projects done by Sunlight Labs. Their proposed redesign of the U.S. Supreme Court website was impressive enough that I was happy to involve WebSort with their work in tackling a behemoth of a government entity – the FCC.

Talk about a mountain of information to organize – the Federal Communications Commission’s main page has enough text links and upper level data categories to make your head spin. No wonder the folks at Sunlight Labs wanted to start with a card sort to help them create an organization that would actually make sense to the user.

To read about the results of their card sort, you can check out their full post here. But I’ll go ahead and quote one of my favorite parts:

Before any organization embarks on a card sorting exercise they should go through their content to get rid of the excess, make sure everything is understandable to a user, and combine content areas that are similar in nature. Doing this first will make it easier for the people participating in the card sorting and will mean less time spent analyzing the final data.

We’ll definitely be posting more about this soon, as preparing to do a card sort is as important as doing the sort itself. Because, as with many things, you get out what you put into it.  But even without having a strict methodology to follow, simply taking the time to thoughtfully try to weed out redundancies, artificially similar wordings, and ambiguous terms can go a long way in making the results of a card sort a lot more useful.

Beyond Card Sorting

  • Do you use video in your user research? The team behind WebSort also runs GuapoVideo. Upload, annotate, & share your research videos, all from a web-based interface.

Ready to try WebSort for online card sorting? Get started for free