January 9, 2009

Monash’s First Law of Commercial Semantics explained

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

5 Responses to “Monash’s First Law of Commercial Semantics explained”

  1. Social network analysis, aka relationship analytics | DBMS2 -- DataBase Management System Services on August 21st, 2009 6:10 am

    [...] 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 [...]

  2. Clearing up MapReduce confusion, yet again | DBMS2 -- DataBase Management System Services on December 30th, 2009 5:51 am

    [...] predicted by Monash’s First Law of Commercial Semantics, different vendors have individual variants on those themes. For example, as per a [...]

  3. The Naming of the Foo | DBMS2 -- DataBase Management System Services on March 13th, 2010 5:47 pm

    [...] No technology category name is ever perfect. [...]

  4. Obfuscate clearly! | Strategic Messaging on July 24th, 2010 9:52 pm

    [...] 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 [...]

  5. So what is an analyst anyway? | Strategic Messaging on July 25th, 2010 11:42 pm

    [...] 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 [...]

Leave a Reply




Feed including blog about strategic marketing and messaging in technology and politics Subscribe to the Monash Research feed via RSS or email:

Login

Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.