Skip to content

System Scope Definition

Define the system-of-interest boundary so analysis, responsibility, measurement, and intervention target the right whole.

The Diagnostic Story

Symptom: The same project meeting keeps returning to what are we actually solving and who owns this because no one ever stated what is inside the system and what is not. Metrics contradict each other because different people are counting different populations. Work expands through adjacent requests without a conscious decision to include them. Analysis alternates between too narrow to explain the problem and too broad to act on.

Pivot: State the boundary explicitly — what is inside, what is outside, what is adjacent, and what crosses the line — then connect that boundary to responsibility, measurement, handoffs, and review. The scope decision becomes visible and governable rather than assumed.

Resolution: Participants are reasoning about the same system-of-interest, so analysis is coherent and metrics are comparable. Responsibility aligns with the declared boundary: what is inside is owned; what is adjacent is visible but not implicitly committed. Scope disagreements can be raised and resolved without restarting the entire initiative.

Reach for this when you hear…

[software project management] “We're six weeks in and product and engineering still disagree on whether the notification system is in scope — that ambiguity needs to be a one-page decision document before we write another line of code.”

[public health evaluation] “The intervention covers the clinic population, but we're being held accountable for community outcomes we have no control over — we need to be explicit about what the program boundary actually is.”

[systems analysis] “Every time we model this we either get a toy that ignores the supply chain or a diagram so big no one can identify a lever — we need to agree on the boundary before we go further.”

Mechanisms / Implementations

  • System-of-Interest Definition: This is a systems-engineering or systems-thinking method for naming the system being analyzed, its environment, and its interfaces.
  • Project Scope Statement: A project scope statement records included work, excluded work, deliverables, assumptions, dependencies, and acceptance criteria.
  • Model Boundary Definition: A model boundary definition states what a model represents, what it omits, and where its outputs are valid.
  • Jurisdictional Scope: Defines the territory, authority, population, or matter over which an institution has responsibility.
  • Service Boundary Definition: A service boundary definition specifies what a service owns, what it exposes, which dependencies it accepts, and where handoffs occur.
  • Research Inclusion/Exclusion Criteria: Research inclusion and exclusion criteria implement the archetype by defining which participants, cases, evidence sources, time horizons, or observations are inside a study.
  • Operational Responsibility Map: An operational responsibility map connects the scope boundary to owners, handoffs, escalation paths, and decision rights.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 3 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Project Scope Definition · domain variant · recognized

Defines the included work, excluded work, deliverables, actors, interfaces, and decision rights for a project or initiative.

Model Scope Definition · implementation variant · recognized

Defines what a model represents, what it abstracts away, and which interfaces connect model outputs to real-world decisions.

Responsibility Scope Definition · governance variant · recognized

Defines which actors or units are responsible for which parts of a system, including handoffs and shared interfaces.

Research Scope Definition · domain variant · recognized

Defines the population, cases, variables, time horizon, and evidence base included or excluded from a research claim.