Abstract

How do firms create and capture value in large technical systems? In this paper, I argue that the points of both value creation and value capture are the system’s bottlenecks. Bottlenecks arise first as important technical problems to be solved. Once the problem is solved, the solution in combination with organizational boundaries and property rights can be used to capture a stream of rents. The tools a firm can use to manage bottlenecks are, first, an understanding of the technical architecture of the system; and, second, an understanding of the industry architecture in which the technical system is embedded. Although these tools involve disparate bodies of knowledge, they must be used in tandem to achieve maximum effect. Dynamic architectural capabilities provide managers with the ability to see a complex technical system in an abstract way and change the system’s structure to manage bottlenecks and modules in conjunction with the firm’s organizational boundaries and property rights.

Highlights

  • Large technical systems made up of many interacting components are becoming more common every day

  • How do firms create and capture value in large technical systems? In this paper, I argue that the points of both value creation and value capture are the system’s bottlenecks

  • How do firms create and capture value in the increasingly large technical systems emerging today? In this paper, I argue that the points of both value creation and value capture are the system’s bottlenecks

Read more

Summary

Introduction

Large technical systems made up of many interacting components are becoming more common every day. How do firms create and capture value in the increasingly large technical systems emerging today? Today large technical systems have expanded to involve many firms, and managers must have a sophisticated understanding of BOTTLENECKS, MODULES AND CAPABILITIES. Architectural capabilities are an important subset of dynamic capabilities that provide managers with the ability to see a complex technical system in an abstract way and change the system’s structure by rearranging its components (Teece, Pisano and Shuen, 1997; Pisano and Teece, 2007). Purposeful architectural change can be used to create and capture value at different points in the technical system. In this paper I argue that value-enhancing architectural change arises through the effective management of bottlenecks and modules in conjunction with the firm’s organizational boundaries and property rights.

Technical and Industry Architecture
Solving Technical Bottlenecks
Protecting Strategic Bottlenecks
Acquiring Architectural Knowledge and Capabilities
Findings
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call