MENTAL MODEL · M2181

Scope Creep

BusinessHigh supportManagement

Included

Version 1.0.0 · Updated 2026-07-30

CORE DEFINITION

During a project, the client continuously adds "small features" or "minor modifications," causing the project boundaries to grow uncontrollably like vines, ultimately leading to delays or budget overruns.

SCAFFOLDING EFFECT

psychology

Reduce cognitive load

- Boundary defense: Learn to say "no." Any requirement not in the initial SOW (Statement of Work), no matter how small, must go through the formal change process (additional cost/schedule impact). This is the only dam protecting the project's survival.

anchor

Anchor fast decisions

Scope creep refers to the uncontrolled accumulation of requirements or changes during project execution, causing scope, schedule, and cost to silently expand. The mechanism is the "invisibility of small increments"—individual "minor modifications" seem harmless, but their accumulation breaks boundaries; and without a formal change process, implicit commitments accumulate into explicit loss of control.

MINIMUM ACTION

In progress 0/1

Practice this model in one real situation:

Lock down the SOW (Statement of Work) and boundaries at project initiation. 2. Any new requirement must go through the change process (assess schedule/cost impact). 3. Dare to say "no" to "small requests" outside the SOW, or defer them to the next phase. 4. Designate a single point of contact (scope gatekeeper) to receive changes uniformly. 5. Regularly review against the baseline to identify hidden creep.

Check to track your progress (stored locally)

Learning progress0%

account_treeGenealogyexpand_more

menu_bookReferencesexpand_more

Source support: Explicit

link
zh.wikipedia.orghttps://zh.wikipedia.org/wiki/%E7%AF%84%E5%9C%8D%E8%94%93%E5%BB%B6ZH · Explicit
verified

RELATED MODELS