Skip to main content

Great Marketing Ruffles Feathers

Execs, here's what we marketers face:
Great marketing pleases everyone on the team, sooner or later. But at the beginning, great marketing pleases almost no one. At the beginning, great marketing is counter-intuitive, non-obvious, challenging and apparently risky. Of course your friends, shareholders, stakeholders and bosses won't like it. But they're not doing the marketing, you are.
Whether we're naming, positioning, or pricing your product, marketing is not common sense.

Comments

dan said…
Cauvin,

You seem to say that others will never like your marketing ideas, good or bad, so what metrics can they use to hold you accountable for good marketing?
Roger L. Cauvin said…
Fair question, Dan. I believe the original quote from Seth Godin holds part of the answer.

It states that great marketing eventually pleases everyone on the team. So some patience in measuring the marketer's performance is important.

As for the specific metrics, it depends on the nature of the marketing.

I have written that a 360 review of product managers is a good way of evaluating a product manager's performance.

For a marcom professional executing outbound campaigns and tactics, some of the standard forms of measurement make sense (e.g. setting up landing pages and measuring leads).

Note that, in both cases, the team must invest some initial trust in the marketer's efforts before measuring the results makes sense.

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

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

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