The Impossibility of User Centered Design?
Eric is right in his initial posting on our blog. Web 2.0 is people (I’m reminded here of Soylent Green, but that’s for another discussion). And of course the Web has always been about people—which is why designing usability and human centered design are such slippery concepts. There is no such thing as universal usability, and certainly no such thing as a universal human subject. So when we design an interface, we must now pay as much attention to the users on the tails of the distribution as we do the “average user.” The analyst in me cringes whenever a few people on a project team decide what is “user friendly,” simply because of the impossibility of nailing down who the “user” is.
Many in this business do various forms of usability testing, mostly based in focus groups or (rarely) videotaping end users on the current interface, or (even more rarely) a prototype of the proposed new system. But in focusing solely on the average end user, those who are not “average” are lost. Rapid prototyping, such as with iRise, provides the best means we currently have of expanding our idea of the “user”—and making the impossible possible. We can push out a prototype not just to focus groups, but even to random sample groups of a significantly large n. Not only will these data help us with designing for the bulk of the distribution, but help us see ways to design the kind of flexibility we need for all potential users. This potential is powerful, and we’re trying at id8 to tap that power for ALL kinds of interfaces.
Like a surprising number of UI folks, I spent a good many years doing textual interpretation for a living, and if the idea postmodernity has taught us anything, it is that meaning is fragmented and contextual. But rather than be paralyzed about the impossibility of meaning, I choose to embrace the multiplicity in meaning. Cultural “texts” present themselves, then, with a great deal more to offer when they can be adaptable and contextual. The same will hold true for user interfaces. The trick with companies like us is to look for ways to make such expanded processes accessible and cost effective.
At some level, I’m always thinking of this idea when I’m working on a UI project. Can we claim “user-centered” design when we don’t know our users, or even a significant sample of them? Why invest so much of our resources unless we’re pretty certain we know what they want and what they’re capable of? To simply decide in a conference room what is user friendly before we build it is a lot like saying that all literature should be written like a newspaper article. We’d be leaving out nuance, style, diversity, and innovation.
I believe it’s time for a paradigm shift in application definition and design. Let’s use more than anecdotal data and make system design itself, not just the end system, a more collaborative process. Let’s see “the user” not as the embodiment of the mean, but as a description of the entire distribution.
I watched
Clay Shirky, in his thought-provoking and humorous keynote address - 
Recent Comments