IDEAS home Printed from https://ideas.repec.org/p/hal/journl/hal-02101085.html
   My bibliography  Save this paper

Why firms implement Coopetitive-Project Teams?

Author

Listed:
  • Anne-Sophie Fernandez

    (MRM - Montpellier Research in Management - UPVM - Université Paul-Valéry - Montpellier 3 - UPVD - Université de Perpignan Via Domitia - Groupe Sup de Co Montpellier (GSCM) - Montpellier Business School - UM - Université de Montpellier)

  • Frédéric Le Roy

    (MRM - Montpellier Research in Management - UPVM - Université Paul-Valéry - Montpellier 3 - UPVD - Université de Perpignan Via Domitia - Groupe Sup de Co Montpellier (GSCM) - Montpellier Business School - UM - Université de Montpellier)

Abstract

Coopetition strategies are driven by the share of the risks and costs of innovation. However, to implement their strategy, coopetitors can rely on two separated projects teams or on a single Coopetitive Project Team (CPT). By pooling their resources in a CPT, coopetitors face a higher level of imitation and spoliation. The question becomes why coopetitors create a CPT and face higher levels of risks when they have other alternatives? Following the literature about risk management in strategic alliances, unilateral contract-based alliances are preferred to minimize relational risks while bilateral contract-based alliances are appropriate to minimize performance risks. We assume that coopetitors create CPT when the performance risks of the project are high. To illustrate our framework, we study the project portfolios of Astrium and TAS in the space industry. Our findings confirm that coopetitors accept higher levels of relational risks and create CPT when the performance risks of the project are high. On the contrary, coopetitors rely on two separated project teams and assume low relational risks when the performance risks of the project are low.

Suggested Citation

  • Anne-Sophie Fernandez & Frédéric Le Roy, 2016. "Why firms implement Coopetitive-Project Teams?," Post-Print hal-02101085, HAL.
    • Handle: RePEc:hal:journl:hal-02101085
    as

    Download full text from publisher

    To our knowledge, this item is not available for download. To find whether it is available, there are three options:
    1. Check below whether another version of this item is available online.
    2. Check on the provider's web page whether it is in fact available.
    3. Perform a search for a similarly titled item that would be available.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:hal:journl:hal-02101085. See general information about how to correct material in RePEc.

    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.

    We have no bibliographic references for this item. You can help adding them by using 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 RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: CCSD (email available below). General contact details of provider: https://hal.archives-ouvertes.fr/ .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.