Skip to main content

Vodka Delusions

Sorry, but Grey Goose is mediocre. Ditto for Ketel One. At least according to a tasting panel at the New York Times.

The tasting panel sampled 21 unflavored vodkas, mostly on the high end. But for kicks, they decided to include lowly Smirnoff in the mix. The results?
[A]t the end of our tasting it was Smirnoff at the top of our list, ahead of many other names that are no doubt of higher status in stylish bars and lounges. Some of those names did not even make our Top 10. Grey Goose from France, one of the most popular vodkas, was felt to lack balance and seemed to have more than a touch of sweetness. Ketel One from the Netherlands, another top name, was felt to be routine and sharp, although Mr. Klemm did describe it as "a good mixer."
Here were the top ten:
  1. Smirnoff United States Grain
  2. Wyborowa Poland Single Estate Rye
  3. Belvedere Poland Rye
  4. Absolut Sweden Level Grain
  5. Hangar 1 United States Straight Wheat and Grain
  6. Vox Netherlands Wheat
  7. Olifant Netherlands Grain
  8. 42 Below New Zealand Wheat
  9. Skyy United States Grain
  10. Teton Glacier United States Potato
The placebo affect [sic] is alive and well.

Comments

Mat said…
Vodka is definitely one of those products that elicit the placebo effect. They all are basically tasteless..
Look at the quote for Teton Glacier: 'Clean and light on the palate; odorless and tasteless'

For most, vodka preference is an accessory; A decoration of self that has little to do with taste, and everything to do with image.

Let's see if I can affect consumer preference even a little..

Real Austinites drink Tito's.. It's an award winning Vodka made in the heart of the Lone Star state. Try it.

http://www.titos-vodka.com/
Sat Feb 16, 08:55:00 PM 2008
Post a Comment

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
32 comments
Read more

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
8 comments
Read more

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio
15 comments
Read more