Beyond card sorting and into tree testing
February 9th, 2009Card sorting is great. That’s why we built OptimalSort.
But card sorting is not enough. Here’s why.
In user centered design (UCD), the process hinges on the premise that end user feedback will help refine and validate the quality of a design. We see this in practice all the time through the most commonly practiced UCD method - usability testing.
However, usability testing rarely tests the information architecture itself. It will provide some insights into labels that may be confusing or categories that failed to get users’ attention. More often than not however, findings from user testing focuses around the interaction and presentation (user interface) levels. Specific feedback on the information architecture itself is rare.
This makes sense because an information architecture is like a building’s foundations - invisible but central to the building’s strength and viability. People will tell you that they don’t like the colours on the walls or the placement of the windows, but they won’t - they can’t - tell you anything about the foundations.
Card sorting is the most popular research method for the creation of an information architecture. It provides the insight into how people organise and label information. A designer takes this information, applies his or her experience, balances the needs of the organisation and creates an information architecture. Unfortunately, that’s often where it stops.
According to UCD, this is only the start of the process. Feedback needs to be solicited, findings applied to refine the design and this process repeated as much as possible until a happy medium is reached.
Dare I suggest that the reason we don’t do this for information architectures, is because it’s too hard. Any system where an information architect is required suggests that the system has a lot of content and is relatively disorganised. Having to test the effectiveness of such a large system is daunting at best. And it’s daunting because none of it is currently automated.
Testing an IA is actually incredibly simple, albeit long winded. Assign participants with representative tasks and observe where in the information architecture they end up, and note the path they took. Do this with enough tasks and enough people and very soon you’ll notice where your structure is inefficient or if certain labels are misleading. Make changes to either, test again and keep going until you run out of time, money or both.
Unfortunately, doing this is both time intensive and somewhat mind numbing. Fortunately, computers are great at doing mind numbing things really quickly so we don’t have to.
Our team longed for a solution, and recently we did something about it. Treejack is an online software tool that allows you to test your information architecture by treating it like an online survey:
- Upload your existing or draft information architecture.
- Create as many representative tasks as you can think of.
- Email the URL of this “tree test” survey to stakeholders, end users or colleagues.
- See how well your IA performed by viewing success, confidence and speed measures for each task.
With Treejack, we can tell in a matter of hours what aspects of an IA need work, what is effective and what to change. Additionally with automated reporting, decision makers are now more interested because of the presence of data that is easy to understand.
At the high level, Treejack provides reporting of:
- Task success - did people end up in the category or categories you expected them to?
- Confidence - how sure were they? Was their path direct or indirect?
- Speed - how long did they take?
More detailed reporting shows which categories participants ended up in, the full path taken, any back tracking and the skip rate for each task.
More information can be found on the Optimal Workshop website. A free public version of Treejack will be available from the 16th February 2009.
