Skip to main content

Backwards Compatibility Requirements

When your company upgrades a product, you and your product manager may concern yourselves with backwards compatibility.

Backwards compatibility refers to the extent to which the upgraded product works with existing ways of using the product. The upgrade may introduce new features and new ways of interacting with the product. But if a user can interact with the new version in the exact same manner and achieve the exact same results as with the old version, then it is fully backwards compatible.

However, backwards compatibility is not an end in itself. It avoids the following problems associated with existing users' lack of familiarity:
  • Relearning/retraining. To use a product that isn't backwards compatible efficiently, a user may undergo a punitive learning curve to get up to speed.
  • Mistakes. A user unfamiliar with the new interface may be more likely to make mistakes while using the product, causing possible physical, psychological, or monetary damage.
  • Fear of upgrading. Even if upgrading would be worth it from a cost/benefit perspective, users may be reluctant to buy or use the new version.
Your product manager should generally avoid making backwards compability a requirement. Instead, the requirements should include measurable constraints on the learning curve and the probability of destructive mistakes. The testing team should create and execute tests that ensure the upgrade meets these constraints before release.

Some degree of backwards compatibility will likely be a part of satisfying these requirements, but designers may find superior ways of satisfying them. For example, a designer may conceive of a new user interface that is so much simpler that it's easier to learn the new way of using the product than it is to use it the old way.

Armed with metrics showing that the learning curve and risk of destructive mistakes are minimal, your sales team has a powerful way of overcoming the fear of upgrading, regardless of whether the upgrade is backwards compatible.

Comments

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

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing