Skip to content

Lehman's law of conservation of familiarity

Hold the mean change shipped per release of a long-lived software system roughly constant, because the producer and consumer communities have a bounded capacity to absorb novelty, and overdrawing it forces a corrective contraction.

Core Idea

Lehman's fifth law is the empirical observation that the mean incremental change per release of an E-type software system — one whose behavior must continually respond to a real-world environment — stays approximately constant over the system's life. Every release imposes a cognitive update cost on producers and consumers; when releases outrun this combined throughput, a familiarity deficit accumulates and the next release must contract, so the mean returns toward a sustainable band.

Scope of Application

The law lives within software engineering — the empirical-software-evolution and release-engineering subfields where E-type systems are built and shipped.

  • Empirical software evolution — the home turf, one of the eight Lehman laws, first quantified on OS/360.
  • Release engineering — the rationale for fixed-interval release trains capping per-release delta.
  • Open-source project management — the Linux kernel's release train holding delta in a narrow band.
  • Software-quality analysis — reading post-release symptom clusters as one overdrawn-budget diagnosis.
  • Release planning — sizing roadmaps by what a community can absorb, not what a team can produce.

Clarity

The law pulls apart two capacities a roadmap conflates: the rate a team can produce change and the rate communities can absorb it. It lets scattered symptoms — defect spikes, complaint surges, lagging integrators — read as one diagnosis (a familiarity budget overdrawn), and reframes release-size from a free variable into a roughly conserved one set by human cognitive throughput, not staffing.

Manages Complexity

A tangle of social and cognitive variables collapses into one conserved quantity: mean change per release, compared against an absorption band. "Will this release land well?" becomes a one-dimensional reading with three labeled branches — inside the band (sustainable), above it (deficit, contraction due), or held below too long (a different failure mode) — each with a known correction.

Abstract Reasoning

The law licenses symptom-to-cause diagnosis (a symptom bundle implies an overdrawn budget), a contraction-as-regulation reading, feasibility forecasting of a roadmap against the band, regime boundary-drawing across three labeled zones, and an invariant-under-staffing inference (adding contributors does not widen the band).

Knowledge Transfer

Within software engineering the law transfers literally as mechanism across every E-type system, since that precondition defines the domain, carrying from OS/360 to Linux, Apache, and GCC. Beyond software the portable claim — a socio-technical system has bounded human-absorption capacity per cycle, and overdrawing it triggers corrective degradation — travels as the parents conservation_laws, absorptive_capacity, cognitive_load, and homeostasis, not the named law; the software-specific cargo stays home.

Relationships to Other Abstractions

Local relationship map for Lehman's law of conservation of familiarityParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Lehman's law of cons…DOMAINDomain-specific abstraction: Lehman's law of self regulation — presupposesLehman's law ofself regulationDOMAINPrime abstraction: Carrying Capacity — is a decomposition ofCarryingCapacityPRIME

Current abstraction Lehman's law of conservation of familiarity Domain-specific

Parents (2) — more general patterns this builds on

  • Lehman's law of conservation of familiarity presupposes Lehman's law of self regulation Domain-specific

    The fifth law's mean release-delta band presupposes the third law's regulating loop that converts overdraw into corrective contraction.

  • Lehman's law of conservation of familiarity is a decomposition of Carrying Capacity Prime

    The familiarity band is a sustainable load envelope specialized to how much change a software community can absorb per release.

Hierarchy paths (3) — routes to 3 parentless roots

Neighborhood in Abstraction Space

Lehman's law of conservation of familiarity sits in a crowded region of the domain-specific corpus (14th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Software Evolution & Systemic Laws (16 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12