Skip to main content

Positioning Series

When you hire a product manager, one of the first series of tasks she should complete is to position the product. Positioning a product means defining your target market and key messages you will use to appeal to them.

Positioning the product in the most effective way typically requires leaving the office and doing substantial market research, including quantitative research (questionnaires) and qualitative research (prospect interviews and ethnographic studies).

Positioning a product should be an iterative effort. But as your new product manager educates herself by interacting internally within the company (talking to executives, sales, marcom, and developers; reading existing documents), she can begin filling out a preliminary template. She should answer the following questions:

  1. What is the company's distinctive competence?
  2. What are the top three problems the product solves?
  3. What is the product's biggest weakness?
  4. What is the strength within the product's biggest weakness?
  5. What is the product's biggest competitor?
  6. What is the competitor's biggest strength?

This list is by no means exhaustive but includes the most important questions for simple cases. Fitting the product into the positioning umbrella of the company or a line or suite of products may be necessary. Profiling prospective buyers and sizing the market are also important.

However, answering these preliminary questions goes a long way towards determining the best position for your product. After taking an initial stab at them, your product manager should conduct the market research necessary to validate and flesh out the answers.

In future entries, I will discuss what each of the questions means and how to obtain the answers.


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

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