How Do Committees Invent?

Conway, M. E. (1968). How Do Committees Invent?. Datamation, 14(4), 28-31.

Type

Journal article

Intellectual base

Primary research

Year

1968

Link

http://www.melconway.com/Home/pdf/committees.pdf

Cited from

economics_finance, library_information_science, organizational_management, philosophy, systems_cybernetics

Cited by

17 citations across 17 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Boundary Critique
  • … systems architecture**: The "system under test," the "microservice boundary," the "bounded context" in domain-driven design, and the "security perimeter" are all boundary choices with strong downstream consequences for architecture, operation, and accountability; Conway's Law (organizations produce designs mirroring
• Complexity
  • Organizational management: Conway's law states that a system's architecture mirrors the communication structure of the organization building it—a modular organization produces modular systems; a hierarchical organization produces hierarchical systems

    This sourceVolume/issue/pages correct.

• Conway's Law
  • The original statement — "any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure" — generalizes once stripped of software vocabulary: when a coordination network produces a modular artifact, the module boundaries of the artifact track the communication boundaries of the producers, because every inter-module interface in the artifact has to be negotiated across the producer-producer link that owns it, and links that are absent or costly produce interfaces that are absent or costly.
• Coordination

  • This sourceStates Conway's Law: organizations that design systems are constrained to produce designs that copy their own communication structures; a coordination-structure constraint on system design.

• Division of Labor
  • Listed in the references but not attached to a specific claim.
• Environmental Coupling Strength
  • Listed in the references but not attached to a specific claim.
• Hierarchy
  • Conway's Law (Conwayist) insight

    This sourceOrigin of "Conway's Law": establishes a homomorphism between an organization's communication structure and the structure of the systems it designs, explaining why organizational and software hierarchies tend to mirror one another.

• Inconsistent Shared Model
  • … health (epidemiology and clinical-care models with measurably different transmission parameters, surfacing only at policy formulation), multi-team software engineering** (backend and frontend holding divergent models of a shared API contract until deployment forces joint execution, a Conway's-law inevitability

    This sourceConway's law — systems mirror the communication structure of the organizations that build them, making divergent cross-team models of a shared interface a structural inevitability.

• Layered Coordination & Oversight
  • Listed in the references but not attached to a specific claim.
• Oversight Capacity
  • Listed in the references but not attached to a specific claim.
• Systemic Fragmentation
  • The coordination-deficit infrastructure where communication channels, governance structures, or integrative mechanisms across boundaries are weak or absent

    This sourceOrigin of "Conway's Law": establishes a homomorphism between an organization's communication structure and the structure of the systems it designs, explaining why organizational and software hierarchies tend to mirror one another.

• Task Interdependence
  • The density of interdependence (how many other tasks each task connects to; sparse versus dense networks)
• Unity Test
  • And whole boundaries as design surfaces: in engineered systems the unity test is itself a design choice with consequences for change, ownership, and accountability, which is why a system's structure so often mirrors the structure of the teams that built it — an observation about implicit unity tests in architecture.

    This sourceStates Conway's law — that a system's structure mirrors the communication structure of the organization that designed it — an observation about implicit unity tests in architecture.

Domain-specific

• Fallacy of One Administrator
  • In enterprise IT and "single systems" that span business units, the fallacy reappears as Conway's-law fracture lines: a platform marketed internally as one system silently has one admin per business unit, and the org-chart seams become the outage seams where two change boards fail to align

    This sourceEstablishes the design-time half only - that a system's structure copies the communication structure of the organisation that designs it; the carry-over of those seams into runtime outages and misaligned change boards is the article's extension.

Mechanisms

• Organization–Artifact Topology Overlay
  • It is the fastest way to see the mirror Conway's law predicts instead of arguing about whether it exists.

    This sourceStates that organizations tend to produce system structures that mirror their communication structures.

• Organizational Team Boundaries
  • It is most powerful when team boundaries are drawn to match the structure of the work, since communication paths and system structure tend to mirror each other.

    This sourceArgues that systems reproduce the communication structures of the organizations that design them.

• Organizational Unit Model
  • Its strength is making coordination cost visible exactly where the individual and the aggregate views both hide it; it resonates with Conway's law, the observation that a system's structure tends to mirror the communication structure of the org that builds it

    This sourceArgues that a designed system’s structure reflects the communication structure of the organization that produced it.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 5 other ways.

• https://www.melconway.com/Home/Committees_Paper.html ×4
• https://www.bitsavers.org/magazines/Datamation/196804.pdf ×2
• http://www.melconway.com/Home/Committees_Paper.html ×1
• https://jglobal.jst.go.jp/en/detail?JGLOBAL_ID=201602021356431990 ×1
• https://www.melconway.com/research/committees.html ×1

Registry ID ref:1f81c02b4470 · see in the full table