Skip to content

Scope Creep

Version
v1 · 2026-08-24 · History
Prime #
1163
Origin domain
Systems Thinking & Cybernetics
Subdomain
project dynamics → Systems Thinking & Cybernetics

Core Idea

A bounded undertaking expands beyond its original perimeter through a sequence of small additions, each defensible against the current boundary but none accountable for the cumulative trajectory. The baseline against which "small" is measured drifts with every accepted increment, so the perimeter ratchets outward with no owner of the motion.

How would you explain it like I'm…

Just One More Tower

Imagine building a small sandcastle, and each friend asks you to add 'just one more tower.' Every single tower seems fine on its own, so you keep saying yes. But by the end it's a giant castle you never meant to build, and you can't point to the one tower that was too much.

The Sliding Starting Line

Scope creep is when a project that started small grows way bigger, not from one big decision but from lots of little 'just add this' steps. Each small addition looks reasonable compared to where things are right now, so people keep saying yes. The trouble is the starting line keeps sliding forward, so you measure each new 'small' thing against the already-grown version, not the original plan. Saying yes is easy because it's just one small thing, but saying no is hard because you'd have to defend the boundary. In the end you're far from where you began, yet no single step was clearly the wrong one.

Boundary Drift With No Author

Scope creep is when a bounded undertaking expands past its original perimeter not through one deliberate decision but through a sequence of small additions, each defensible against the current boundary, none accountable for the overall trajectory. The baseline you measure 'small' against drifts with every accepted increment, so the perimeter ratchets outward and rarely retracts. It needs three conditions, and is absent if any is missing: a definable initial scope that existed before the additions; an evaluation procedure that judges each new request against the current state rather than the original; and asymmetric costs for yes versus no, where saying yes just means accommodating a small ask while saying no means doing the effortful, unrewarded work of defending the boundary. Together these make a moving reference frame with no single author — which is exactly why the growth is invisible while it happens, since at each step people are judging a defensible local add-on, not the indefensible total.

 

Scope creep is when a bounded undertaking expands beyond its original perimeter not through a single deliberate decision but through a sequence of small additions, each individually defensible against the current boundary, none accountable for the cumulative trajectory. The baseline against which 'small' is measured drifts with every accepted increment, so the perimeter ratchets outward and rarely retracts; the undertaking ends up far from where it began, yet no single step can be identified as the wrong one, because each was reasonable against the state that immediately preceded it. The pattern requires three structural conditions and is absent when any is missing. First, a definable initial scope — a perimeter that existed before the additions began. Second, an evaluation procedure that judges each proposed addition against the current state rather than the original state, so the reference frame moves with the work. Third, asymmetric costs for assent versus refusal: saying yes requires only accommodating a small request, while saying no requires defending the boundary, an effortful and often unrewarded act. Together these produce a moving reference frame whose motion has no single author. The load-bearing content is precisely this — not that projects grow, but that they grow through baseline-relative approval under asymmetric refusal cost, which makes the growth invisible to participants while it happens, since at each step they evaluate a defensible local increment rather than the indefensible cumulative trajectory. The prime also separates two outcomes that look alike from outside: deliberate re-scoping, where someone explicitly owns the new perimeter, versus drift, where the new perimeter has no owner at all — and the intervention space differs for each.

Broad Use

  • Software development: features added one at a time, each cheap against the current release, until the project ships late — feature creep.
  • Military operations: a mission acquires policing, then nation-building, then counterinsurgency — mission creep.
  • Regulation: a statute targeting one harm is reinterpreted to cover adjacent cases far beyond its drafters' intent.
  • Personal commitments: a one-time favor grows into a standing obligation; a volunteer role absorbs new responsibilities.
  • Science: a paper's question expands as reviewers ask for one more analysis, and a thesis swells past completability.
  • Meetings: agendas accept one more topic until they outrun their time slot.

Clarity

Makes visible the trajectory the local view hides — the boundary as a moving reference frame with no single author — so "have we drifted?" becomes askable where "is this addition reasonable?" never permits.

Manages Complexity

Compresses a long sequence of micro-decisions into a single shape — a ratcheting boundary — that distant actors can audit as a first-class object even when they cannot evaluate each step's merits.

Abstract Reasoning

Licenses substrate-neutral moves keyed to the structural conditions: anchor to the original baseline, periodically re-charter, impose symmetric assent costs, and assign a boundary owner.

Knowledge Transfer

  • Software to finance: the "displace-something" rule appears as work-in-progress limits and zero-base budgeting.
  • Finance to law: the periodic re-charter is the zero-base audit and the legislative sunset clause.
  • Any substrate: the diagnostic — judged against the original charter or a drifting baseline, and who owns the trajectory? — travels unchanged.

Example

A release chartered for features A, B, C accepts D (small against {A,B,C}), then E (against {A,B,C,D}); the baseline drifts with each yes, and the release ends at {A...K} late, with no single addition nameable as the wrong one.

Relationships to Other Abstractions

Local relationship map for Scope CreepParents 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.Scope CreepPRIMEPrime abstraction: Ratchet Effect — is a kind ofRatchet EffectPRIMEDomain-specific abstraction: Feature Creep — is a kind ofFeature CreepDOMAIN

Current abstraction Scope Creep Prime

Parents (1) — more general patterns this builds on

  • Scope Creep is a kind of Ratchet Effect Prime

    Scope Creep is a specialization of Ratchet Effect, retaining the parent's defining structure while adding the child's specific commitments.

Children (1) — more specific cases that build on this

  • Feature Creep Domain-specific is a kind of Scope Creep

    Feature creep is scope creep specialized to product capabilities admitted one at a time while their system-wide interaction and maintenance costs compound.

Hierarchy paths (3) — routes to 3 parentless roots

Not to Be Confused With

  • Scope Creep is not Parkinson's Law because the former grows the requirement set, whereas Parkinson's Law holds requirements fixed while work expands to fill its allocation.
  • Scope Creep is not the Ratchet Effect in general because the former specifies the particular lock (drifting baseline) and driver (asymmetric assent), whereas the generic ratchet needs only any lock.
  • Scope Creep is not Deliberate Re-Scoping because the former has an absent trajectory owner, whereas re-scoping is an accountable party affirmatively owning a new perimeter.