- We design and build extraordinary applications for companies looking to make the next great idea a reality.
- learn more
On the use of “user”
“I’m sick of users,” announced Josh Bernoff in
a recent blog entry, leading one to initially believe that he has joined the
ranks of indifferent (or outright hostile) developers, clients, and other uninterested
parties reluctantly associated with producing applications and websites. However,
Bernoff’s distaste is semantic, not social. He argues that the term “user”
emphasizes technology over relationships and encourages a flattened and skewed
view of the people interacting with the products. He challenges the readers to “try,
just for a day, to stop using this word. You’ll be amazed at how differently
you think about the world.”
Unsurprisingly,
Bernoff’s modest proposal unleashed a torrent of unfavorable comments and
accusations that the substitution of more contextually specific appellations such
as “people,” “customers,” or “employees” was an attempt to fix something that
isn’t broken. A few readers were quick to brandish the smackdown stick of a
failed attempt at elaborate political correctness in Bernoff’s suggestion. And
of course, the old joke that only drug dealers and IT professionals refer to
their constituency as “users” was brought up (twice, in fact).
I agree with the
commentators who stated that “user” is a well-understood term, not
intentionally pejorative, and is, in fact, hard to replace without awkwardness
or lack of precision. My one objection regards the use of the term when
referring to usability testing. Often referred to as “user testing,” here the
term—perhaps unintentionally, but surely—puts the focus of evaluation on the
participant and not the system. I even prefer taking the term “testing” out of
the equation, instead calling the process “usability assessment.” I’ve dealt
with too many participants suffering performance anxiety and brightly uttered
the set piece that “we’re evaluating the system, not you” far too many times.
Of course, I’m not advocating that we keep the user out of the assessment, but
instead focus on the point of the activity. This is probably the one scenario
where people are directly and personally exposed to the term “user,” which is
almost exclusively used internally in design and development teams. Although we’re
all users, we are so in the third person only.
Leave a comment
About Pathfinder
Recent
- Dealing With A Legacy
- Big Changes Underway at LinkedIn for Groups
- Four blatant iPhone usability blunders (and one constant annoyance)
- Flash/Flex physics engines and examples
- A Rails Story, Or An Engine That Really Could
- Data visualization and the art of conveying information
- What’s In Your Junk Drawer?
- Selling Git on the Business End
- IE8 Beta 2 Released
- Faster JavaScript for Firefox 3.1 Thru JIT
Archives
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006

