Skip to main content

Aim High

I mentioned in a previous entry that a significant amount of what a product manager does is recommend strategy that contradicts basic instincts. I listed four examples of such instincts.

One of the instincts I failed to mention, however, was the seemingly unstoppable temptation to lower prices or offer temporary discounts to stimulate demand for a company's product. In most cases, a good product manager will advise the opposite - maintain a stable price that reflects the value of the product rather than offer discounts.

I've mentioned that John Moore, in his Brand Autopsy blog, recommended that company executives visit the Brand Autopsy Discount Detox Center when they become addicted to price discounts.

Skimming through one of my favorite classic books on marketing, Al Ries and Jack Trout's Marketing Warfare, I recently came across these passages (excerpted from pages 90-92):
"Psychologist Robert B. Cialdini tells the story of a jewelry store in Arizona that couldn't sell an allotment of turquoise pieces. Just before leaving on a trip, the owner scribbled a note to her head sales person - 'Everything in this case, price x 1/2,' - hoping to get rid of the jewelry, even at a loss. When she returned a few days later, every article was gone. But because the salesperson had read the 1/2 in the scrawled message as a 2, the entire batch had been sold at twice the original price, not half. For many products, high price is a benefit. The price adds credibility to the product."
And later:
"There are two good reasons why high price represents more of a marketing opportunity than low price. One is the tendency of the prospect to equate quality with price. 'You get what you pay for.' The other is the potential for higher profit margins with a higher price. The higher margins allow you to finance the critical 'pursuit' stage of a flanking attack."
Brand management isn't about instincts, it's about well-established branding principles.


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

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 problem