Skip to main content

Positioning and Distinctive Competence

You're trying to decide on the key themes and messages to use in your product marketing campaign. As I mentioned in my article, "How to Formulate Marketing Messages", you can use three approaches to identifying candidate messages:

1. Portray your product as an antidote to a prospect problem.
2. Highlight the strength within your product's weakness.
3. Attack the weakness within your leading competitor's strength.

It just so happens that weaknesses and strengths often derive from a company's distinctive competence. A company's distinctive competence may be a patent, its personnel, or an established position in the marketplace. These competencies do not always directly benefit customers; sometimes a distinctive competence merely enables the company to better deliver some benefits to customers.

When considering how to attack the weakness within your leading competitor's strength, keep in mind that your competitor's strength may simply be its distinctive competence. When you attack a weakness within that strength, you strike at the competitor's core. Any attempt by the competitor to deny the weakness implicitly denies its core strength.


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