Skip to main content

Barack Obama as a "Product"

Positioning a product against a competitor is much like positioning a political candidate against a competitor.

Barack Obama, though he still trails Hillary Clinton in most polls, is the current "darling" of the Democratic field of presidential candidates. Clinton's "positives" may be high, but so are her "negatives" (most people have formed an opinion about her one way or the other).

According to polls, Obama's "positives" far outweigh his "negatives". His biggest strength is that he is a fresh face.

A good marketer - and a good campaign strategist - knows that the best way to defeat a competitor is to find the weakness within his strength and attack at that point.

If being a fresh face is Obama's biggest strength, then it's also a weakness. Maybe he doesn't have the foreign policy experience needed to confront the threat of terrorism. Maybe he doesn't have the executive experience to lead a nation. Whoever runs against Obama should find a focused issue, or something specific in his past, that exemplifies Obama's lack of experience and the liabilities of it.

Obama, on the other hand, should embrace his weakness. He could, for example, acknowledge his inexperience with foreign policy but find a way of spinning it as a strength. Perhaps the world has become so disenchanted with the United States and its leaders that a fresh face with a new approach is just what the United States needs. Whatever; Obama can't deny his lack of experience, so he should find specific ways of showing how it is a strength.

It will be interesting to see which Democratic candidate's campaign strategists understand and apply the principles of product positioning.

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

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

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