Thoughts on the Value of Ethnographic Methods

By on

Our group has been thinking and talking a bit about ethnography as a research method.  The discussion was started when we read a paper from CHI 2006, called Why We Tag: Motivations for Annotation in Mobile and Online Media. This paper investigates the motives of a small group of people for tagging photos they upload to Flickr via a mobile app called ZoneTag.

As our group uses mostly quantitative methods (with some exceptions), this paper was a departure for us.  As a result, our paper meeting quickly digressed from a discussion of tagging activity in online systems to a generic discussion of methodology.  One of the most interesting points made in the discussion was: there is deep learning that happens in an ethnography, but it is very hard to communicate that deep learning in a peer reviewed publication.

I agree with this.  It is hard to understand what is generalizable from the set of quotes or the (often unsupported) theoretical models that tend to appear in ethnographic studies.  However, ethnographies appear to be among the more nuanced of research methods.  Thus, I have several thoughts about the value of these studies to me.

Perhaps ethnographers have deep insights, and are therefore in a unique position to contribute design implications.

Darn it.  I read more about this one, and it turns out that a preeminent voice in the field has argued directly against my intuition.  Paul Dourish wrote a CHI paper (as well as a follow-up to appear in DUX 2007) arguing that ethnographies should not be evaluated on the basis of their arguments for design implications.  Rather, design implications are shallow, whereas human culture and thought is deep.  A very interesting perspective, that to me argues for rethinking the design of ethnographic studies in many cases.  Ethnographic studies should be designed to understand people rather than design – but I fear that (HCI-focused) ethnographic studies are usually designed to understand design rather than people.

Perhaps ethnographies are useful up front for understanding ways of designing technology.

Clearly, there are different methodologies for different reasons.  There is no single method that dominates others.  They are situational.  Thus, we might ask where ethnography fits into this puzzle.  One answer is that ethnography is a useful way of gaining a deep understanding of people to guide early design decisions.  One could base survey questions on the results of an ethnography, or design user interaction based on users’ existing practices.

However, I often wonder if users really know what’s best.  Users cannot see innovations, but they can illustrate ways of making existing practices better, or perhaps ways of applying new techniques to old problems.  Thus, I am torn.

Perhaps ethnographies are interesting and a good vehicle for initiating discussion.

This is clearly true.  Stories are more interesting than numbers to most people.

All this has become particularly relevant to my thoughts as I contribute to a paper based on the work that I conducted over the summer.  While our research is not based on ethnographic methods, we do try to learn from observations, and through open-ended survey and interview methods.  It’s my belief that using several methods together (quantitative methods + qualitative methods) makes for strong and interesting research.  I am curious how we will tie stories to data, and the extent to which we will feel at liberty to generalize from a relatively small sample of users in a unique setting.

Is your mind open?

By on

A recent article in the NY Times "Revisiting the Canon Wars" (http://www.nytimes.com/2007/09/16/books/review/Donadio-t.html) took a 20 year retrospective look at the controversy over Alan Bloom’s book "The Closing of the American Mind". Bloom argued that American universities had been "dumbed down" by abandoning the classical Western canon.

Lots to argue about here, and the article gives a taste of the argument. However, I was most struck by the way the article ended:

Bloom believed education should be transformative… that it should provide a student with “four years of freedom”
— “a space between the intellectual wasteland he has left behind and
the inevitable dreary professional training that awaits him after the
baccalaureate.” Whether students today see college as a time of freedom
or a compulsory phase of credentialing is an open question. From
Bloom’s perspective, “the importance of these years for an American
cannot be overestimated. They are civilization’s only chance to get to
him.”

Wow, that was bracing and brutal! I’m curious what others think about it.

Switching to GMail

By on

After much debate I finally decide to switch to Gmail from Thunderbird.  The three features that decided me on the switch were:

1) Labels.  I’ve been using folders for two decades now.  Folders are clearly a browse feature.  Labels are (can be?) a search feature.  I wanted to experiment with search-based email.

2) A unified address book.  Since Gmail is web-based, I no longer have the problem of having my address book be different on every client.

3) Fast startup.  I keep a big inbox (just over 6000 messages right now), and the IMAP startup overhead was getting me down.

So far the switch is okay.  I’m using the *essential* Gmail macros package so I can enter labels from the keyboard.  (I use the version by Brent Nef, which has the wonderful feature of being able to create a new label with the "N" key.)  The keybindings Google has chosen are weird, and it’s killing me not to be able to rebind them.  The two biggest pains, though, are:

1) Having to hit an extra "x" character to select the message header the caret is on before I can operate on that message.  If no other message is selected isn’t it obvious I intend to delete the message the caret is on?!

2) Importing all my old mbox files.  I’ve found a couple of programs (Gmail Loader and gExodus) that offer to help with the import.  Their solution is a brutal hack: they email the messages one at a time to Gmail.  Years ago this was not just a hack, it was a disaster: the messages would update their timestamps when Gmail received them.  This problem is improved now, since a diligent user can email them to a secondary Gmail account, and then slurp them into the primary account using Gmail-to-Gmail import.  Rumor has it that the import will reset the timestamps.

The problem for me is that the messages will import without labels.  Ugh!  gExodus has a hack solution: the program will prepend arbitrary text in the subject line.  In principle, a user might then write a filter for each incoming mbox file that would assign the appropriate Gmail label to it according to the prepended text.  (E.g., [Riedl:Folder:Foo] might be labelled "Foo".)  Unfortunately, I have 390 folders (two decades, remember), and as far as I can tell the filters would have to be written separately for each folder (no wildcarding in Gmail filters).

Another possible solution would be to use one of the Gmail APIs.  For instance, this Java API is sufficient to write a nearly full-featured desktop email client that uses Gmail as its backend.  There are a number of similar Python APIs.  Sadly, none of these are support by Gmail, so using them might be risky.  Even more sadly, none of the ones I’ve found support assigning labels through the API.  Otherwise, I could use the mail trick in gExodus, and have a separate program use the API to assign the labels.

Any ideas?

John 

Wikipedia implementing trust ratings for authors

By on

Wikipedia is going to implement Alfaro et al’s algorithm to assign trust levels to individual chunks of text within articles based on the reputation of the author of the chunk. The interface will use color coding to visualize trust levels. 

http://technology.newscientist.com/channel/tech/mg19526226.200-wikipedia-20–now-with-added-trust.html

Wikipedia: Quality over Quantity?

By on

Interesting article in the LA Times about Wikipedia and the battle over quality versus quantity.  The heart of the story is the frenzy over Jimmy Wales creating an article about a little barbecue restaurant he likes.  The article was deleted as "not notable".  Wild discussion ensued, with many arguing that the article would have been deleted without question if it hadn’t been created by Wales.

The interesting angle to me is the question about why something should be deleted from Wikipedia if it is accurate and interesting to some people.  There’s a good information theory argument that if people are mostly browsing to find information it’s important to avoid having too much: even log growth eventually becomes too much.  However, it seems to me that most of the finding of information on Wikipedia is through search.  In this case, most of the growth of the indexes is Google’s problem: the rest of us never notice most of the stuff on Wikipedia.

A weakness in this argument is that as the index space becomes polluted with references to the irrelevant, successful searches will require more keywords to be sufficiently selective.  In effect, the change from browse to search may have little information theoretic difference on usability: in browse I click more, while in search I type more.

I wonder if these ideas can be formalized and tested?  What would be a good test-bed?

John