How Not to Generate Positive Word of Mouth

Rayfes writes about a case study in how not to generate positive word of mouth for your business:

Stopped by Champion's Sports Bar for lunch today. Hadn't been so figured it would be good to try.

First impression is that it was yet another chain in Austin which isn't surprising since it's in some Mariott derivative hotel by the convention center.

Bartender messed up my order and another guy sitting at the bar. That's ok, it happens and he offered the other guy a free mystery beer.

Later the guy wanted to watch something other than what was playing. There are 3 customers at the bar and 5 tvs. It's Thursday afternoon and not much is going on. The bartender tells him that he's not allowed to change any of the tvs. Customer asks for the manager. Manager doesn't come for 10 minutes. He says that he can't put anything other than sports on (even if it's muted) since they are a "sports bar."

At which point I decide I am not going to come back to a place with overpriced food that won't take care of their customers.

Guess they can join the list with Iron Cactus and a few other places that are too good for their own customers.

It's when you have a only a few customers that you have a great opportunity to go the extra mile to make them happy. Don't blow it.

Comments

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...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problems she faces or the ...

Cauvin

Search This Blog