Block and Run Innovative Strategies and their Implications for Project and Knowledge Management Routines : the Case of a Pharmaceutical and Chemical Company
The role of innovation in business has long been recognized, but increased competition among companies has forced them to seek new strategies. In this paper, two types of strategies will be compared. In the first type, patents play a key role in protecting businesses from the entry of new competitors (block). The second strategy is characterized by repeated introduction of new products on the market (run). The focus of this article will be on the implications of these strategies for the firm and its internal procedures. Specifically, we investigate how the choice of innovative strategy determines the type of project management and knowledge management that the company adopts. Based on a case from the chemical and pharmaceutical industry, we will demonstrate that both types of strategy involve “heavyweight project management.” In the block strategy, learning processes are mainly dedicated to scientific knowledge rather than market knowledge. Consequently, development partnerships are established primarily with academic units and research centers of other companies. In contrast, in the run strategy, repeated interactions with customers occur during the development process. This “learn and probe” process is aimed at iteratively defining the new product with the customers. Development partnerships involve the clients themselves and enable joint learning. Because very successful companies have recently combined these two types of strategies, we will elaborate on the implications of such a dual strategy for the company. As each strategy alone is associated with a specific knowledge management approach, internal conflicts might emerge when they are combined. We will conclude with organizational procedures that might reduce such conflicts.
|Date of creation:||2003|
|Publication status:||Published in Gestion 2000, Recherches et Publications en Management A.S.B.L., 2003, pp.83-102|
|Note:||View the original document on HAL open archive server: https://hal.archives-ouvertes.fr/hal-00262566|
|Contact details of provider:|| Web page: https://hal.archives-ouvertes.fr/|
When requesting a correction, please mention this item's handle: RePEc:hal:journl:hal-00262566. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (CCSD)
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
If references are entirely missing, you can add them using this form.
If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.
Please note that corrections may take a couple of weeks to filter through the various RePEc services.