10 Things to Know about Card Sorting #UX http://t.co/NcJP4o1V (http://t.co/zyINfShL)
– Measuring Usability (MsrUsability) http://twitter.com/MsrUsability/status/187567109142876161

The definitive guide to card sorting in the Encyclopedia of HCI - with a commentary from yours truly. http://t.co/Mr0RfWsa
– David Travis (userfocus) http://twitter.com/userfocus/status/185393710014541824

Online versus offline card sorts compared. http://t.co/eEOCbQF
– David Travis (userfocus) http://twitter.com/userfocus/status/108499963180355584

"Ein Intranet-Projekt hat viele Baustellen – eine davon ist das Thema “Navigation” – das ich heute ein wenig beleuchten werde. Bevor ich darauf eingehe, möchte ich kurz ein paar Worte zu den Begriffen Informationsarchitektur (IA) und Navigation verlieren. Oft kommen Fragen aus den Fachabteilungen auf wie z.B.: Was bedeutet denn eigentlich IA? In welchem Zusammenhang steht IA mit Navigation? Wie grenzen sich diese Begriffe voneinander ab – grenzen sie sich überhaupt ab? Was ist mit Usability – ist das auch ein Thema der IA? Um nur wenige Beispiele zu nennen."

In this column, I’ll summarize and compare the latest generative and evaluative methods for IA user research. The methods I’ll examine include open card sorting, Modified-Delphi card sorting, closed card sorting, reverse card sorting, card-based classification evaluation, tree testing, and testing information architecture with low-fidelity prototypes. I’ll cover the advantages and disadvantages to consider when choosing between these methods, when it makes sense to use each method, and describe an ideal combination of these methods.

"I find that the big things on the top of the story map look a little like vertebrae. And the cards hanging down look a little like ribs. Those big things on the top are often the essential capabilities the system needs to have. I refer to them as the "backbone" of the software. I stole this term from Dr. Dan Rawsthorne who might use the term slightly differently than I do.



When it comes time to prioritize stories, I don't prioritize the backbone. It just "is." I do prioritize the ribs - the stories hanging down from the backbone. Place them high to indicate they're absolutely necessary, lower to indicate they're less necessary. When you do this, you'll find that all the stories placed high on the story map describe the smallest possible system you could build that would give you end to end functionality. This is what Alistair Cockburn refers to as the "walking skeleton". I always try to build this first."