Premium
Complementarity, Compatibility, and Product Change: Breaking with the Past?
Author(s) -
Dhebar Anirudh
Publication year - 1995
Publication title -
journal of product innovation management
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.646
H-Index - 144
eISSN - 1540-5885
pISSN - 0737-6782
DOI - 10.1111/1540-5885.1220136
Subject(s) - new product development , obsolescence , product management , core product , marketing , business , product lifecycle , product proliferation , product (mathematics) , industrial organization , profit (economics) , economics , microeconomics , geometry , mathematics
Product managers are caught between a rock and a cliche (or two). The market response to “new” Coke seems to support those who argue, “If it ain't broke, don't fix it.” On the other hand, rapidly shrinking product life‐cycles lend credence to the notion that the only constant is change. Preserving the status quo places both the product and the company on a fast track to obsolescence. To remain competitive, companies need a structured approach to understanding and managing product change. Anirudh Dhebar offers such an approach by focusing on three interrelationships in which a product is involved. These interrelationships, or complementarities, are between a product and its users, other products with which the product is typically used, and databases that are created and repeatedly modified with the help of the product. These complementarities define the context in which the product is used. By understanding them, a company can better anticipate how a planned product change will affect consumers. In planning product changes, it is important to remember that effective use of the product requires compatibility between the product and its complements. A change that somehow disrupts the product's complementarities can be viewed as a break with the past. In other words, such a change creates a new version of the product which is incompatible with the old version. This type of change results in a switching cost for the consumer. That is, the consumer may have to invest time, money, and effort to reestablishing the complementarities that have been disrupted by the product change. For example, if a new software release includes significant changes to the user interface, consumers must weigh the potential benefits of any new features against the time and effort involved in relearning the interface. If these switching costs are too high, the new release will fail in the marketplace. When planning product changes, a company must recognize the extent of a product's complementarities, and assess how a break in any of them will affect consumers' switching costs. It is important to recognize that the switching costs and the perceived benefits of the new product version may not be the same for all consumers. Finally, careful consideration must be given to the implementation of the product change. For example, the company must decide whether to offer some sort of bridge that helps consumers make the break with the past. The company also needs to decide whether the change is implemented throughout the product line or only in selected models.