8 responses

  1. Stalin
    May 11, 2010

    Differentiation is made very simple and clear.

    Reply

  2. Shery
    June 17, 2015

    This is an upgrade not just an update.

    Reply

  3. Noman khubaz
    November 24, 2016

    ¤Thnx¤
    ¤Its really help me to understand difference between update and upgrade.¤

    Reply

  4. Harshada
    August 3, 2017

    Very simple, clear n easy explanation..
    Really helped to understand the differentiation..

    Reply

  5. Akernuyea Frank Kpantee
    September 29, 2017

    Thanks a million your website helped me a lot. Actually it give me exactly what I needed, hope you keep it hosted so that we can continue to benefit from it.

    Reply

  6. Usman Sultan
    October 18, 2017

    Its really awesome and informative dear

    Reply

  7. Ted Haeger
    January 12, 2018

    Exactly the distinction I was looking for…but maybe consider revising the phrase “more superior” to just “superior” in order not to undermine your credibility.

    Reply

  8. kevin
    May 7, 2018

    My employer makes hardware that comes with software and firmware. It’s business-to-business or biz-to-gov stuff. We do releases at a pace we can stand, and they always include fixes. Many releases include new, or improved functionality. We don’t charge for that. So that departs from the model you describe.

    Only a new version of hardware (after several years of dev and test) is considered a “new product” and gets a whole new price list structure. And the previous version lingers for a while, for customers with existing fleets or those who need specific, existing integrations with third-party systems, and then ages out and is displaced by the newer-hardware product.
    Otherwise, a customer can pay for any (or a combination) of a very few niche upgrades that modify the base product in specific ways, but those are optional from our perspective. The customer might not consider them optional… due to their industry requirements, but those are the exceptions, and there is a small, finite number of them associated with a product. As in, you could count them on the fingers of one hand, over the life of the product.

    But for keeping-up-with / ahead-of the general market for our kind of products, we just keep watching the industry trends for pain-points and other reasons that customers might want new functionality that we could implement in the current hardware, and then we change the f/w or the s/w or both and post the release with the new features. Customers don’t have to use any that they don’t need, but it’s all included in the initial product and service-contract prices.

    So, your description of the difference-between doesn’t quite fit.

    We’re trying to standardize our language around
    – “If this release is mostly fixes and security stuff, and minimal-or-no feature improvements, then call it an update”.
    – “If this release has some important improvements that we can tout, and that allow existing or prospective customers to enter a new niche or be more competitive in their industry, etc., then call it an upgrade.” (It will also contain fixes, ‘cuz we try not to wait on those.)

    You already pay a premium price for a premium product and service, so either kind – update or upgrade – is no additional charge.

    Actually, if somebody could suggest a different terminology for what we release, I would be happy to promote it at work. But for now, it’s update vs upgrade, and the distinction is blurry, and it doesn’t follow the rule in your article.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top
mobile desktop