The dark and bright sides of complexity: A dual perspective on supply network resilience

Robert Wiedmer, Zachary Rogers, Mikaella Polyviou, Carlos Mena, Sangho Chae

Research output: Contribution to journalArticleScientificpeer-review

45 Citations (Scopus)

Abstract

Supply networks are regularly affected by events that trigger supply disruptions, entailing severe consequences for firms and their supply networks. Hence, the ability of firms to withstand and recover from disruptions (i.e., their resilience) is vital to their long‐term survival. Prior research suggests that the complexity of a firm’s supply network is critical in determining its resilience to disruptions, but tensions arise when delineating the precise nature of the relationship between supply network complexity and resilience. In this research, we investigate whether and how three facets of supply network complexity—supply complexity (nodes in the network), logistics complexity (arcs in the network), and product complexity (contents moving through the network)—influence a firm’s ability to resist and recover from disruptions. We empirically investigate this relationship in the context of automotive sector shipments from Japan to the United States before, during, and after the 2011 Japanese Earthquake and Tsunami, using the difference‐in‐differences technique. Results indicate that the relationship between supply network complexity and resilience is multifaceted; some aspects of supply network complexity intensify disruption impact, whereas others enhance disruption recovery.
Original languageEnglish
Pages (from-to)336-359
JournalJournal of Business Logistics
Volume42
Issue number3
Early online dateFeb 2021
DOIs
Publication statusPublished - Jul 2021

Keywords

  • difference-in-differences estimation
  • logistics complexity
  • product complexity
  • resilience
  • supply complexity

Fingerprint

Dive into the research topics of 'The dark and bright sides of complexity: A dual perspective on supply network resilience'. Together they form a unique fingerprint.

Cite this