Skip to content

Bus Factor

The minimum number of team members whose sudden simultaneous loss would halt a project — a per-capability count of how many people could take a subsystem, credential, or relationship over tomorrow, exposing where tacit human knowledge is dangerously concentrated.

Core Idea

The bus factor of a project is the minimum number of team members whose sudden simultaneous unavailability would halt it — a count of one meaning the project depends on knowledge, credentials, or capability held by exactly one irreplaceable person. The mechanism is concentration of unique human-held assets: tacit mental models, sole credentials, single-author code. Because these live in people, not artifacts, they resist replication, and the true bus factor is usually lower than a surface audit suggests.

Scope of Application

Lives across software engineering and adjacent knowledge-intensive cooperative work — people holding hard-to-replicate knowledge.

  • Internal engineering teams — the home: code one engineer authored that no one else can confidently modify.
  • Open-source maintenance — a critical library on one volunteer maintainer (the xz-utils and core-js episodes).
  • DevOps and operations — secrets, cloud-account ownership, and runbook knowledge concentrated in one engineer.
  • Academic research groups — a postdoc's mental model of a multi-year experiment lost on departure.
  • Family firms and critical-systems operation — a founder's tacit relationships, or legacy COBOL specialists with no successor.

Clarity

Naming the bus factor converts diffuse unease into an auditable quantity: "the auth subsystem has a bus factor of 1" forces an inventory and ranks remediation. It relocates succession from an HR question to a reliability one. Its sharpest work is the distinction "shared knowledge" collapses — familiarity versus substitutability — which exposes why documentation often fails to move the number, and it flags that proxies under-count exactly the tacit assets that matter, so a clean audit warrants suspicion.

Manages Complexity

A project's vulnerability to personnel loss is an unbounded who-knows-what tangle. Bus factor collapses it to a single cardinal per asset — how many could provide this tomorrow — so the manager reasons over a sorted list of depths rather than the full matrix. Any asset at depth 1 is a halting single point of failure; depth 4-or-more is effectively safe. The familiarity-versus-substitutability cut keeps the integer small, and the proxy-underestimation correction is applied uniformly: a clean audit means look harder.

Abstract Reasoning

The concept supports a diagnostic move (infer hidden concentration from authorship and access proxies, treating the inferred depth as a ceiling on the true one), boundary-drawing (does a holder count toward depth via the substitutability cut, and is this capability in scope), an interventionist move (sort by depth and raise the 1s with genuine deputies, not documentation, reading the diminishing-returns curve), and an order-of-operations prediction (read the failure ordering off the depths before any incident).

Knowledge Transfer

Within software and adjacent cooperative work the bus factor transfers as full mechanism — the per-capability depth count, the substitutability cut, the diminishing-returns curve, the deputy-not-documentation remedy, and the proxy-underestimation correction — carrying literally into open source, DevOps, research groups, and family firms, since each is people holding tacit assets. Beyond human work it is the human-capital instance of a more general mechanism; the cross-domain weight is carried by the parent single_point_of_failure (with redundancy and concentration risk), while the "hit by a bus" framing and tacit-asset proxies stay home.

Relationships to Other Abstractions

Local relationship map for Bus FactorParents 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.Bus FactorDOMAINPrime abstraction: Dependency Distribution Concentration — is a decomposition ofDependency Dist…PRIME

Current abstraction Bus Factor Domain-specific

Parents (1) — more general patterns this builds on

  • Bus Factor is a decomposition of Dependency Distribution Concentration Prime

    Removing the team and tacit-knowledge framing leaves a measure of how system-critical dependency weight is concentrated across providers.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Bus Factor sits in a moderately populated region (41st percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Software Evolution & Systemic Laws (16 abstractions)

Nearest neighbors

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