Modularity, flexibility, and knowledge management in product and organization design.¶
Sanchez, R., & Mahoney, J. T. (1996). Modularity, flexibility, and knowledge management in product and organization design. Strategic Management Journal, 17, 63-76.
Cited by¶
10 citations across 10 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Abstraction
This sourceStandardized interfaces embed coordination, enabling modular product and organization design.
- Boundary
- Listed in the references but not attached to a specific claim.
- Compatibility
- Listed in the references but not attached to a specific claim.
- Decomposition
- Listed in the references but not attached to a specific claim.
- Dependency
This sourceArgues standardized interfaces embed coordination, so module dependencies need not be actively managed once interfaces are fixed.
- 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
- A common failure is specifying rigid interfaces that become bottlenecks (every change requires interface redesign) or overly flexible interfaces that are complex to understand and implement correctly
This sourceArgues that standardized interfaces between modular components embed hierarchical coordination, enabling firms to recombine product and organizational components for strategic flexibility without redesigning the system as a whole.
- A common failure is specifying rigid interfaces that become bottlenecks (every change requires interface redesign) or overly flexible interfaces that are complex to understand and implement correctly
- Preparatory Field Conditioning
- Task Interdependence
- Listed in the references but not attached to a specific claim.
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? Not recorded. Neither this nor any other of the 10 citations of this work carries a recorded support check.
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 1 other way.
Registry ID ref:9c4a5f7a6356 · see in the full table