Skip to main content

Positioning: Strength within Weakness

What is the strength within the product's biggest weakness?
This question is the fourth of several questions I've enumerated that a product manager should answer to most effectively position a product. You've already identified the biggest weakness of your product. Now find the strength within it.

As I mentioned in the previous entry, Listerine's weakness of tasting like medicine serves as a good example. The other side of the coin is its supposed effectiveness in killing germs. Its bad taste actually strengthens this positive message.

Another example is a product that is expensive to produce (relative to the competition), such as food containing all-natural ingredients. If your product is expensive to produce, you either need to lower production costs or tout the benefits to the customer that result from the expense.

When you position your product according to the strength within its biggest weakness, you:
  1. Differentiate your brand in a manner clear to prospective customers.
  2. By embracing your weakness, you increase the credibility of your positive message.
  3. Make it difficult or impossible for a competitor to attack the product's weakness without indirectly supporting your key message.
Keep in mind that identifying the strength within your product's biggest weakness is but one question you need to answer before deciding how to position your product. Stay tuned as future entries examine the remaining questions.


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

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the

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