Skip to main content

Rationality and Product Preference

About a year ago, for fun, I went to grocery stores and bought as many different kinds of cola soft drinks as I could find, including:

  • Coke
  • Pepsi
  • HEB Original Cola
  • Safeway Select Cola
  • RC Cola
I then proceeded to administer blind taste tests to guests whenever I had people over to my loft. The results were interesting, mainly because what people thought was their favorite cola differed greatly from their actual preference.

Safeway Select Cola performed best overall. Unfortunately, I can no longer find it at the Randall's stores where I originally bought it.

I administered this test to only a few people (about six, if I recall correctly), so take the results with a grain of salt. But chalk this anecdote up as another example of how customers have all sorts of prejudices that interfere with knowing what they really like.


Kevin Brennan said…
My Dad, for many years, was the head of marketing research for a major beer company. In that industry, it's pretty much taken for granted that the image associated with a brand of beer is far more important in driving consumer choices than the actual taste of the beer (which does vary, but not as much as people tend to believe).
Scott Sehlhorst said…
A fun random anecdote.

When drinking a small sample of a cola, people prefer a sweeter flavor. When drinking an entire can of the cola, people preferred the less sweet flavor.

This was the trick that made the pepsi challenge so successful. It is also the misinterpreted marketing data that lead to the New Coke fiasco.
Mike Lunt said…
I have to second Scott's comment. Gladwell explicitly explains why these taste tests are flawed in 'Blink'.
Scott Sehlhorst said…
Thanks Mike!

I had forgotten where I heard that. Credit to Gladwell.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware