Skip to main content

What is Competitive Analysis?

What is competitive analysis?

You might think the following activities qualify as competitive analysis:

  1. Creating a matrix of features that shows how your product performs against competitors'.
  2. Comparing your product's market share, gross sales, etc. against those of your competitors.
These activities can indeed be part of competitive analysis, but they neglect the most important factor. Competitive analysis should primarily be about analysis of customer psychography and perceptions. Don't just compare your product to other products, determine what differs between your customers and those of competing products.

What are the problems your customers are trying to solve, and what are the problems competitors' customers are trying to solve? Document personas not just for the customers of your product, but for competitors' products.

How do people perceive your product versus others? With what single word do they associate your product (i.e. what is your brand)? Compare this word to the words that your competitors "own" in the minds of customers. What do existing and prospective customers perceive as your product's biggest strengths and weaknesses? What do they perceive as your competitors' biggest strengths and weaknesses?

This sort of competitive analysis is what should drive the positioning of your product, which largely determines the relative priority of product requirements and the strategies for marketing and selling your product.

Comments

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

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

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