Copernicus Consulting

Entries from November 2007

What Designers Can Learn From Facebook’s Beacon: the collision of “fronts”

November 30, 2007 · 17 Comments

The blogosphere (and even the regular old newspaper-sphere) is alight with stories of Facebook’s online advertising flop, Beacon. What can designers learn from this flop? It’s not about privacy; it’s about the presentation of self. People have different “selves” for different places — virtual or otherwise — and designs must be consistent with these variety of selves.

Boing Boing’s Cory Doctorow posted an interesting story on InformationWeek that predicted the decline of Facebook because of its own success. He predicts that the more people that are one Facebook, the more confusing it is. Your “creepy coworkers,” your boss, and your friends you met at Burning Man are all in the same “place,” making it confusing, embarrassing and difficult for everyone.

What Doctorow is really describing is sociologist Erving Goffman’s notion of “the front.” Using the theatre as a metaphor Goffman argued that we actually “perform” multiple selves. Each place we go has a “front” that we learn to incorporate. A front has a wardrobe, a setting, a decor, make-up, a script and stage direction. We have a “front stage self” that we perform for everyone to see, a “back stage self” for only our closest intimates to see, and a “core self,” which is deeply private.

A doctor, for example, has a front that includes an office, a lab coat, a stethoscope and medical jargon. This is her “front stage” self. But when she’s talking to her best friend, she may use a “back stage self,” being less formal, not wearing a lab coat, or using less formal language. Her “core” self is secretly wishing she were a full-time marathoner, but she tells no one that.

Facebook’s Beacon didn’t work because it forces people to use multiple fronts AT THE SAME TIME. If I tag a recipe from Epicurious.com, but I broadcast that fact to friends that perceive me to be a party girl, I have a collision of fronts. If my boss demands to be my friend, I have a collision of fronts. If I rent The Notebook on Netflix, and my friends think I am a Goth, I have a collision of fronts.

Facebook’s Beacon forces its users to combine multiple selves. Goffman considers the collision of fronts to be a source of embarrassment or shame. Take, for example, the hilarious “Meeting in a Swimming Pool” gag on Just for Laughs. Swimmers have their swimming front (including a bathing suit, casual demeanour) and forced into a meeting, with its serious demeanour and fully clothed attendants. This is embarrassing.

Facebook has done the same thing by forcing its users to expose their selves to different fronts simultaneously. It is embarrassing, even shameful.

What Designers Can Learn From Facebook’s Beacon

  • Discover your users’ fronts: If you are designing a product or a virtual place, ask your potential users what they consider the character of this “place” to be. Is is a formal place? Is it a casual atmosphere? What kinds of “props” are expected here? What would be an embarrassing topic of conversation or incident?
  • Design using the theatre metaphor: Make the product consistent with that place, as if you were writing a play. Ensure that what you design is part of a script that users understand or expect.
  • Pay attention to embarrassment: If your users mention shame or embarrassment in any way, gently press them about it. Discover the character of the “collision of fronts” that is the source of that embarrassment, and, above all, avoid forcing users to feel embarrassment.

Update: The New York Times is reporting that Facebook’s lawyers have not succeeded in having documents about its founder Zuckerman removed from an online magazine. These documents are “embarrassing.”

Update (12/19/07): Mashable is reporting that FB is now allowing people to “group” their friends, but they haven’t quite mastered the collision of fronts problem.

Categories: beacon · facebook · goffman · online advertising · product design · qualitative research · technology design · user experience
Tagged: , , , , , ,

Why customer satisfaction surveys are useless

November 12, 2007 · 3 Comments

Many readers seem to enjoy my qualitative versus quantitative research post. I take this to mean that designers are hungry insight that beyond the requisite (and useless) customer satisfaction survey.

I’m not a huge fan of customer satisfaction surveys because they are usually 100% reliable but 0% valid; they tell you nothing (but consistently tell you nothing). Witness, for example, the Foresee customer satisfaction survey. This survey is designed to give pop up as a user leaves a Web site. They are asked a variety of customized questions and then a variety of demographic information. Foresee tallies these results regularly and even ranks your Web site (or company in general) in comparison to your competitors.

What does a designer learn from this? Almost nothing.

Why? Several reasons.

  1. Consumers have “satisfaction” fatigue: consumers are surveyed to death these days. We are all familiar with the Likert scale “strongly agree” to “strongly disagree.” Few survey researchers actually rework their surveys for validity. It’s called “acquiescence bias” where people tend to just answer the same way repeatedly. Survey researchers who know better use reverse-scoring techniques; but most don’t. These surveys, therefore, result in a questionable assertion that they are actually valid representations of how consumers actually feel.
  2. Satisfaction surveys breed incremental “metricism”: surveys tell you nothing new: designers need to innovate their products, Web sites, and images. Satisfaction surveys tell you nothing you don’t already know. What’s more, they may actually inhibit creativity because they draw attention to minute changes that may be due to chance alone. Once organizations become regular consumers of satisfaction surveys, even small improvements become cause for celebration — even if they don’t reflect real improvements (see number 1).
  3. Surveys provide numbers, not detail: designers need thick description to make their designs truly evocative of lived experiences. Satisfaction surveys are simply stripped down representations of how people feel (or more accurately, how they say they feel). Designers need richer information to spark creative solutions.
  4. Customer satisfaction is a poor predictor of looming competition: Imagine a company that had consistently high customer satisfaction scores. Imagine also that this company falls victim to “incremental metricism,” and fails to see a competitor’s new, better designed product on the horizon. This competitive product would never appear in customer satisfaction surveys. It’s possible for customers to be “satisfied,” only to have them lured away by an innovative, better design.

Instead of customer satisfaction surveys, I recommend designers pore over free trend-spotting data, like the Pew Internet and American Life Project, which is a comprehensive and rigorous survey of current attitudes and beliefs. It’s harder to pull out insights from data that don’t look like they’re relevant, but the return is so much better than from a tired, staid customer satisfaction survey.

Categories: Research Methods · customer satisfaction · product design · quantitative research
Tagged: , , ,