Monash’s First Law of Commercial Semantics explained
Edit: Monash’s First Law is special case of Monash’s Third Law of Commercial Semantics: No market categorization is ever precise.
Below is a three-year-old post of mine from a long-dormant blog, quoted in its entirety:
Maria Winslow notes that “Open Source” is an example of
Monash’s First Law of Commercial Semantics:
Bad jargon drowns out good.
Now, I won’t pretend that’s really original with me — but then, it’s based on Gresham’s Law, for which Sir Thomas Gresham apparently doesn’t deserve the credit he gets either.
The idea behind the “Law” is this: If a term connotes some kind of goodness, marketers scarf it up and apply it to products that don’t really deserve it., making it fairly useless to the products that really do qualify for the more restrictive meaning.
“Predictive analytics” sounded cool, and now covers a fairly broad range of statistical analyses, most of which don’t involve any kind of explicit prediction. Some “native” XML data stores are dressed-up tourists from either the relational or object-oriented worlds, while a lot of “thin clients” actually do their shopping at Lane Bryant. “Transparent” connectivity layers tend to be cloudy, and “portablilty” commonly involves considerable heavy lifting.
By the way, Monash’s Second Law of Commercial Semantics is much more technologically oriented: Where there are ontologies, there is consulting. I first said that at the Text Mining Summit, and it seemed to win immediate, widespread agreement.
Comments
16 Responses to “Monash’s First Law of Commercial Semantics explained”
Leave a Reply
[…] that analyze relationship graphs are commonly grouped under the name social network analysis. As I frequently point out, category names and definitions tend to be imperfect, and that one is no exception. In particular […]
[…] predicted by Monash’s First Law of Commercial Semantics, different vendors have individual variants on those themes. For example, as per a […]
[…] No technology category name is ever perfect. […]
[…] the names of particular portions of a marketecture diagram. Now, I am on record as believing that all product category names are flawed. But while some vagueness or ambiguity may be unavoidable, there is no reason for names to be […]
[…] though similar people are involved in several of the efforts. Notwithstanding my well-documented skepticism about category definitions, I think it might be interesting to pull some of these ideas together in one […]
[…] (That is definitely an inclusive OR.) Suggestions for slicker wording will be gratefully received — but in making them, please try not to run afoul of Monash’s First Law of Commercial Semantics. […]
[…] about columnar technology. (I further suspect that certain vendors are encouraging this confusion, as vendors commonly do.) So here are some basic […]
[…] not necessarily the best way to address the numerous use cases for analytic DBMS technology. And product category names are commonly problematic anyhow. So I don’t much mind this overloading of the EDW term. But in one respect I think the […]
[…] Vertica’s new data warehouse appliances. At first blush, this may seem like an instance of Monash’s First Law of Commercial Semantics (“Bad jargon drives out good”). But I think Vertica’s usage is legitimate, and will […]
[…] http://www.strategicmessaging.com/monashs-first-law-of-commercial-semantics-explained/2009/01/09/ […]
[…] frequently observe that no market categorization is ever precise and, in particular, that bad jargon drives out good. But when it comes to “big data” or “big data analytics”, matters are worse […]
[…] Bad jargon drives out good […]
[…] the industry would be better off if the phrase “real-time” were never used again. Monash’s First Law of Commercial Semantics teaches why this isn’t likely; but a guy can dream, can’t […]
[…] Confusingly, the Teradata Aster library of functions is now called “Discovery” as well, although thankfully without the “data” modifier. Further marketing uses of the term “discovery” will surely follow. […]
[…] more products try to integrate SQL with Hadoop, and discussions of them seem confused, in line with Monash’s First Law of Commercial Semantics. So let’s draw some distinctions, starting with (and these […]
[…] I consul to ever more stealth-mode companies, so perhaps it’s time to pull together some common themes in my advice to them. Here by “stealth mode” I mean the period when new companies — rightly or wrongly — are unwilling to disclose any technological specifics, for fear that their ideas will be preempted by rival vendors’ engineering teams (unlikely) or just by their marketing departments (a more realistic concern). […]