Design Rules, Volume 1¶
Baldwin, C. Y., & Clark, K. B. (2000). Design Rules, Volume 1: The Power of Modularity. The MIT Press.
Cited by¶
17 citations across 17 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Abstraction
This sourceTheory of modular design via design rules and hidden module parameters.
- Boundary
This sourceTheory of modularity and module boundaries in design and industrial evolution.
- Compatibility
- Listed in the references but not attached to a specific claim.
- Decomposition
- The principle of orthogonal decomposition (parts that do not overlap or interfere) recurs across mathematics, software architecture, organizational design, and cognitive science—a cross-domain transfer Baldwin and Clark (2000) trace explicitly from engineering modularity to industry structure and innovation dynamics.
This sourceTraces modularity from engineering design rules to industry structure and innovation dynamics.
Supported in partVerified against the publisher's abstract
The book's abstract supports modularity's transfer from engineering design rules to industry structure and innovation, not the recurrence of orthogonal decomposition across mathematics, cognitive science, and software architecture.
“They argue that the industry has experienced previously unimaginable levels of innovation and growth because it embraced the concept of modularity, building complex products from smaller subsystems that can be designed independently yet function together as a whole.”
- The principle of orthogonal decomposition (parts that do not overlap or interfere) recurs across mathematics, software architecture, organizational design, and cognitive science—a cross-domain transfer Baldwin and Clark (2000) trace explicitly from engineering modularity to industry structure and innovation dynamics.
- Dependency
This sourceTheory of modular design built on design rules that decouple module-internal decisions from interdependencies across modules.
- Design for Lifecycle Adaptability
- The emphasis on ease of partial modification: change to one element should not require downstream redesign cascades
This sourceDevelops a theory of modular design (hidden vs. visible modules, design rules, and modular operators: splitting, substitution, augmentation, exclusion, inversion, porting) showing modular structure lets components be designed independently and changed without rippling through the whole.
Supported in partVerified against the publisher's abstract
The abstract supports modularity letting subsystems be designed independently, but it says nothing about a change to one element avoiding downstream redesign cascades, so only the frame is backed.
“building complex products from smaller subsystems that can be designed independently yet function together as a whole. Modularity freed designers to experiment with different approaches, as long as they obeyed the established design rules.”
- The emphasis on ease of partial modification: change to one element should not require downstream redesign cascades
- Interface
- The concept emerges from engineering (mechanical connections, electrical pinouts, protocol stacks), computer science (APIs, ABIs, system calls), biology (cell membranes, synaptic clefts, hormonal signaling), human-computer interaction (UI affordances and hidden complexity), economics (market zones between buyers and sellers), and organizational management (team boundaries, cross-functional handoffs)—a cross-domain pattern Baldwin and Clark (2000) document as the universal logic of modularity.
Supported in partVerified against the publisher's abstract
The abstract supports modularity as a design principle in the computer industry, but it does not state that Baldwin and Clark document a universal logic of modularity across the listed domains.
“They argue that the industry has experienced previously unimaginable levels of innovation and growth because it embraced the concept of modularity, building complex products from smaller subsystems that can be designed independently yet function together as a whole. Modularity freed designers to experiment with different approaches, as long as they obeyed the established design rules. Drawing upon the literatures of …”
- The concept emerges from engineering (mechanical connections, electrical pinouts, protocol stacks), computer science (APIs, ABIs, system calls), biology (cell membranes, synaptic clefts, hormonal signaling), human-computer interaction (UI affordances and hidden complexity), economics (market zones between buyers and sellers), and organizational management (team boundaries, cross-functional handoffs)—a cross-domain pattern Baldwin and Clark (2000) document as the universal logic of modularity.
- Layering
- Listed in the references but not attached to a specific claim.
- Minimalism
- Listed in the references but not attached to a specific claim.
- Modularity
- Modular architecture allows a large organization (or ecosystem of firms) to work on different modules simultaneously without constant synchronization
Supported in partVerified against the publisher's abstract
The publisher abstract backs modularity as independent design of subsystems that still function as a whole, but it names products and designers, not large organizations or firm ecosystems working without synchronization.
“They argue that the industry has experienced previously unimaginable levels of innovation and growth because it embraced the concept of modularity, building complex products from smaller subsystems that can be designed independently yet function together as a whole.”
- Modular architecture allows a large organization (or ecosystem of firms) to work on different modules simultaneously without constant synchronization
- Platform Design
- Specialization
- Modular system design generalizes the principle: Baldwin and Clark (2000) show that drawing clean module boundaries lets each module specialize and improve independently, but only by paying an up-front cost to define and freeze the interfaces — the design rules — across which the specialized modules must agree.
Supported in partVerified against the publisher's abstract
Baldwin & Clark's abstract states that modularity lets subsystems be designed independently while obeying established design rules; it does not state the up-front cost of defining and freezing those rules.
“building complex products from smaller subsystems that can be designed independently yet function together as a whole. Modularity freed designers to experiment with different approaches, as long as they obeyed the established design rules.”
- Modular system design generalizes the principle: Baldwin and Clark (2000) show that drawing clean module boundaries lets each module specialize and improve independently, but only by paying an up-front cost to define and freeze the interfaces — the design rules — across which the specialized modules must agree.
- Substitutability
- This language creates a bridge between engineering design (interfaces, specs, tolerances), organizational structure (role definitions, accountability), and biological systems (plasticity, redundancy)—the same bridge Baldwin and Clark (2000) trace in Design Rules, where modular architectures generate "option value" precisely by making components substitutable through visible design rules and hidden implementation choices.
Supported in partVerified against the publisher's abstract
The book's abstract confirms modularity, obeyed design rules and real options as its core, but says nothing of biological systems or a visible/hidden substitutability mechanism.
“Modularity freed designers to experiment with different approaches, as long as they obeyed the established design rules. Drawing upon the literatures of industrial organization, real options, and computer architecture, the authors provide insight into the forces of change that drive today's economy.”
- This language creates a bridge between engineering design (interfaces, specs, tolerances), organizational structure (role definitions, accountability), and biological systems (plasticity, redundancy)—the same bridge Baldwin and Clark (2000) trace in Design Rules, where modular architectures generate "option value" precisely by making components substitutable through visible design rules and hidden implementation choices.
- Task Interdependence
- Listed in the references but not attached to a specific claim.
Mechanisms¶
- Modular Architecture Design
- Modularity is, in effect, purchased option value on future adaptation.
This sourceModels modular architecture as creating real options for future independent experimentation, substitution, and adaptation.
- Modularity is, in effect, purchased option value on future adaptation.
- Modular Capacity Expansion
- It misleads when the increment is wrong-sized: many small units suffer diseconomies and integration overhead
This sourceModule granularity must balance the costs of creating, testing, and integrating modules against modular flexibility.
- It misleads when the increment is wrong-sized: many small units suffer diseconomies and integration overhead
- Modular Design Option
- This is the design-time face of what engineering-economics calls modularity as embedded real options — a modular architecture is literally a portfolio of options to substitute or upgrade parts independently.
This sourceTreats modular architecture as creating real options to substitute or improve components independently.
- This is the design-time face of what engineering-economics calls modularity as embedded real options — a modular architecture is literally a portfolio of options to substitute or upgrade parts independently.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 6 of 17 citations: 6 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 3 other ways.
- https://doi.org/10.7551/mitpress/2366.001.0001 ×3
- https://direct.mit.edu/books/monograph/1856/Design-RulesVolume-1The-Power-of-Modularity ×2
- https://mitpress.mit.edu/9780262538206/design-rules-volume-1/ ×1
Registry ID ref:eb1468a2f985 · see in the full table