Previous post:

Next post:

Why customer satisfaction surveys are useless

by Sam Ladner on November 12, 2007 · 3 comments

in Research Methods, customer satisfaction, product design, quantitative research

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.

Share:
  • Twitter
  • del.icio.us
  • Facebook
  • FriendFeed
  • StumbleUpon
  • Digg
  • LinkedIn
  • Technorati
  • email

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

{ 1 trackback }

Customers more satisfied when served by white males « Design Research
July 19, 2009 at 6:45 pm

{ 2 comments… read them below or add one }

1 Avi November 30, 2007 at 10:48 pm

I’d respectfully add that such surveys don’t provide any point of reference. They aren’t normed. Is 3.5 on a five point scale a high score? What does ’satsified’ mean?
(And this, mea culpa, from someone who has written his fair share of ‘evaluation forms’.)

Reply

2 Friedbeef July 15, 2008 at 7:04 am

Supplement Customer Satisfaction with Quali to make the exploratory big learnings, and move with incremental improvements via quanti?

Reply

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Previous post:

Next post:

Blog
design
qualitative research
product design
Services
Research design
Ethnography
In-depth Interviewing
Usability testing
Projects
Consumer Electronics
High technology
Health Care