Download presentation
Presentation is loading. Please wait.
Published byPatricia Gaines Modified over 9 years ago
1
1 © Carliss Y. Baldwin and Kim B. Clark, 2002 Where Do Transactions Come From? Carliss Y. Baldwin Harvard Business School Presented at NBER Organizational Economics Conference, November 22, 2002
2
2 © Carliss Y. Baldwin and Kim B. Clark, 2002 Transaction Cost/Incomplete Contracts Williamson, 1985: A transaction occurs “when a good or service is transferred across a technologically separable interface. … [R]arely is the choice among alternative organization forms determined by technology.” UpstreamDownstream “Technologically separable interface” In this literature, technologies and designs are fixed, asset ownership and decision rights move around.
3
3 © Carliss Y. Baldwin and Kim B. Clark, 2002 But suppose designs and product definitions are not fixed a priori, Then, where do Transactions Come From?
4
4 © Carliss Y. Baldwin and Kim B. Clark, 2002 But suppose designs and product definitions are not fixed a priori, Then, where do Transactions Come From? From the engineering design of a system of production…
5
5 © Carliss Y. Baldwin and Kim B. Clark, 2002 Our thesis: The modular structure of a system of production reveals the places where: –The division of cognitive labor is high, and –Mundane transaction costs are low. Transactions should go/can go only at those places.
6
6 © Carliss Y. Baldwin and Kim B. Clark, 2002 Outline of the paper T&T Network defined Mapping technique—TSM Encapsulation of T&T “blocks” Pinching the T&T Network Conclusion: Modular structure and mundane transaction costs
7
7 © Carliss Y. Baldwin and Kim B. Clark, 2002 Disclaimer We believe what we are saying is neither radical nor new Many predecessors: –Coase (1937) –Alchian and Demsetz (1972) –Barzel (1989) and North (1990) –Cremer (1980) and Aoki (2001) –Sako (1992) and Fixson and Sako (2001) We aim for a clarification of language.
8
8 © Carliss Y. Baldwin and Kim B. Clark, 2002 The T&T Network Defined
9
9 © Carliss Y. Baldwin and Kim B. Clark, 2002 Task & Transfer (T&T) Network All tasks and transfers needed to complete production of artifacts in the economy Engineering Design is the work of designing the T&T Network Transfers are ubiquitous –Because “agents” have bounded cognition and physical capacity –True for both people and machines
10
10 © Carliss Y. Baldwin and Kim B. Clark, 2002 What gets transferred? Material Energy Information –Data –Designs –“Tags” »Property rights and decision rights are a special form of tag Money or credit = Purchasing Power
11
11 © Carliss Y. Baldwin and Kim B. Clark, 2002 Transfers are Dictated by technology Complex Logical Necessary (because of bounded capacity) Designed But not planned centrally
12
12 © Carliss Y. Baldwin and Kim B. Clark, 2002 Not all transfers are transactions A “transaction” requires –Standardizing transfers –Counting transfers –Payment for the units transferred These are extra and costly tasks – => “Mundane” Transaction Costs (MTC) MTC vary depending on complexity of transfers –Contingent, interdependent, iterative transfers are very complex –Hence such transfers are very costly to make into transactions
13
13 © Carliss Y. Baldwin and Kim B. Clark, 2002 Mapping the T&T Network
14
14 © Carliss Y. Baldwin and Kim B. Clark, 2002 Mapping Technique = “Task Structure Matrix” (TSM)
15
15 © Carliss Y. Baldwin and Kim B. Clark, 2002 Intel T&T Network—1993
16
16 © Carliss Y. Baldwin and Kim B. Clark, 2002 Intel T&T Network—1993
17
17 © Carliss Y. Baldwin and Kim B. Clark, 2002 TSMs show where transfers occur, but not what gets transferred
18
18 © Carliss Y. Baldwin and Kim B. Clark, 2002 Where do transactions go?
19
19 © Carliss Y. Baldwin and Kim B. Clark, 2002 The Smiths and the Cooks
20
20 © Carliss Y. Baldwin and Kim B. Clark, 2002 TSMs reveal T&T “Bottlenecks” Transfer Bottleneck
21
21 © Carliss Y. Baldwin and Kim B. Clark, 2002 Bottlenecks = Transactional “Gateways” “Place Transaction HERE” — Few transfers; One-way transfers; Maximum “Division of cogitive labor”
22
22 © Carliss Y. Baldwin and Kim B. Clark, 2002 Bottlenecks = Transactional “Gateways” “Place Transaction HERE” — Because Mundane Transaction Costs are Probably Low
23
23 © Carliss Y. Baldwin and Kim B. Clark, 2002 Encapsulation
24
24 © Carliss Y. Baldwin and Kim B. Clark, 2002 Design Problem: If every transfer had to be a transaction, little work would get done.
25
25 © Carliss Y. Baldwin and Kim B. Clark, 2002 Solution: Transaction-free zones “Encapsulated Local Systems” –Predecessors: Families, communes, tribes –Merchants and Proto-firms –Then: Full-functioned firms (1750s) and Limited-liability Corporations (1830s) with Affirmative and Defensive Asset Partitioning
26
26 © Carliss Y. Baldwin and Kim B. Clark, 2002 Creating an Encapsulated Local System 1 Materials Energy People Machines Internal Flows are Designed by Engineers Data Agents and Resources Come In; Products Come Out
27
27 © Carliss Y. Baldwin and Kim B. Clark, 2002 Creating an Encapsulated Local System 2 Materials Energy People Machines Data Today All are Obtained Via Transactions $ $ $ $ $ $$$$ Internal Flows are Designed by Engineers
28
28 © Carliss Y. Baldwin and Kim B. Clark, 2002 Creating an Encapsulated Local System 3 Materials Energy People Machines Data Transaction- Free Zone: By design, many complex, contingent transfers occur inside the TFZ Internal Flows are Designed by Engineers
29
29 © Carliss Y. Baldwin and Kim B. Clark, 2002 Boundaries of the Capsule Materials Energy People Machines Data Boundaries = Where Transfers take the form of Transactions, according to the Design of the Enterprise Boundaries are Designed by Engineers, too!
30
30 © Carliss Y. Baldwin and Kim B. Clark, 2002 Financial Sufficiency Materials Energy People Machines Data When all Claimants Have been Paid… $ $ $ $ $ Revenue $$$$ $$$$$$$$$$$ Money is left over! Costs:
31
31 © Carliss Y. Baldwin and Kim B. Clark, 2002 Financial Sufficiency = Survival in a Money/Market Economy Materials Energy People Machines Data When all Claimants Have been Paid… $ $ $ $ $ Revenue $$$$ $$$$$$$$$$$ Money is left over! Local System can survive. Costs:
32
32 © Carliss Y. Baldwin and Kim B. Clark, 2002 Encapsulated Local System = the “Kernel” of a Firm
33
33 © Carliss Y. Baldwin and Kim B. Clark, 2002 Encapsulated Local System = the “Kernel” of a Firm Why only “kernel”?
34
34 © Carliss Y. Baldwin and Kim B. Clark, 2002 Because… Can assemble several Encapsulated Local Systems within “a bigger firm” Can have transactions within “a bigger firm” Transaction costs/incomplete contracts/ property rights economics basically looks at different configurations of kernels within/across firms In practice, Mergers, Acquisitions & Alliances serve to adjust kernel boundaries across firms
35
35 © Carliss Y. Baldwin and Kim B. Clark, 2002 In summary— Encapsulation is a technology in the engineering design of the T&T Network Encapsulation creates the kernels of firms Kernel boundaries are artifacts, which can be designed and re-designed (within constraints of physics and logic of technology) Mergers, Acquisitions & Alliances are visible adjustments of kernel boundaries
36
36 © Carliss Y. Baldwin and Kim B. Clark, 2002 “Pinching” the T&T Network
37
37 © Carliss Y. Baldwin and Kim B. Clark, 2002 An Example from Practice: Engineering plastics company (=designer and supplier) Auto manufacturing company (=customer and user) Product to be designed: –High heat resistant plastic compound
38
38 © Carliss Y. Baldwin and Kim B. Clark, 2002 “Natural” TSM
39
39 © Carliss Y. Baldwin and Kim B. Clark, 2002 Transaction-supporting TSM Is “more Modular” (by defn of Design Rules, Vol. 1)
40
40 © Carliss Y. Baldwin and Kim B. Clark, 2002 Transaction-supporting TSM “Mundane” transaction costs
41
41 © Carliss Y. Baldwin and Kim B. Clark, 2002 Transaction-supporting TSM Standards: To Define “Gateway”
42
42 © Carliss Y. Baldwin and Kim B. Clark, 2002 But Standards were incomplete… [A]s development proceeded, it became clear... that there were other characteristics of the material that were very important to important players in the auto company, which were not in the specs. (Example: the interior designers wanted a material with a “rich, lustrous appearance.”) They were not in the specs, because the auto company had no way to make the requirement specific, no testing protocol and no standard to use in the specifications.
43
43 © Carliss Y. Baldwin and Kim B. Clark, 2002 Transaction-supporting TSM “Relational” or “Obligational” contract needed
44
44 © Carliss Y. Baldwin and Kim B. Clark, 2002 Mundane transactions costs are used to create a “more modular” task structure “Relational” or “obligational” contract needed “Mundane” transaction costs Standards: To Define “Gateway”
45
45 © Carliss Y. Baldwin and Kim B. Clark, 2002 “Pinching” is an Investment In a Task Structure and Relationships that support a strict(er) partition of cognitive labor Value of “Pinching” = + Avoided cost of real-time interdependency/iteration (clt) – MTC (mundane transaction costs) + Free-riding (smaller unit, better individual incentives) – Upstream-Downstream opportunism (in supply chain)
46
46 © Carliss Y. Baldwin and Kim B. Clark, 2002 Conclusion
47
47 © Carliss Y. Baldwin and Kim B. Clark, 2002 Where do Transactions Come From? The modular structure of a system of production reveals where: The division of cognitive labor is high… and Mundane transaction costs are low.
48
48 © Carliss Y. Baldwin and Kim B. Clark, 2002 The modular structure of a T&T Network Can be mapped using TSM graphs Transactions go at the “bottlenecks” of network –Transfers few and simple –Division of cognitive labor high Blocks need to be “transaction-free zones” –Encapsulated via transactions at the boundaries of the zone –Encapsulated Local Systems = Kernels of Firm “Pinching” can create a more modular structure –Costs = Mundane Transaction Costs –Standardizing, Counting, Valuing, Payment
49
49 © Carliss Y. Baldwin and Kim B. Clark, 2002 Thank you!
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.