Skip to main content

"Marketing [sic] Research"

Some people say "market research". Some people say "marketing research". Which term is correct?

Well, maybe both terms are correct in some sense, but they mean different things. Common sense dictates:

market research - research into a market
marketing research - research into marketing

Webster's formal definitions agree with common sense:

market research - research into the size, location, and makeup of a product market
marketing research - research into the means of promoting, selling, and distributing a product or service

I suspect that most people mean "market research" when they say "marketing research".

Comments

Unknown said…
I have the same challenge with the phrase "MarketING requirements." Development hears it as "ideas from the marketing department." That's why I advocate the phrase "Market Requirements" -- that is, requirements from the market.

Market research is how we determine what the market will buy. And thus what we should build. But the trick is to learn what the market needs, not just what it is asking for.
Unknown said…
Forget the word research. The issue is that people are misusing the terms Market and Marketing. They are two completely different things. When you understand the definition of each, it becomes quite clear what Market Research and Marketing Research are.

Another example would be the words analysis and analytics. People accidentally treat them as synonymous.

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

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