Protocol

Define the system boundary before optimizing

Optimization starts by deciding what is inside the model.

About 1 min read

Before you use it

Use when
  • When a local process looks inefficient but upstream causes and downstream consequences are unclear.

Keep this limit in mind

  • A causal map is a hypothesis, not proof. Keep evidence, time scale, boundary choices and alternative explanations visible before acting on a loop.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Name the outcome, time horizon, actors, stocks, flows and dependencies included in the analysis, plus important factors deliberately left outside. Revisit the boundary if the proposed fix pushes cost beyond it.

Steps

  1. State the outcome and time horizon.
  2. List included actors, resources and dependencies.
  3. List major exclusions.
  4. Ask where cost or risk could be displaced.

An example

A support team wants faster ticket closure; widening the boundary reveals that premature closure moves rework into customer escalations.

Check your result

The boundary is explicit and the proposed improvement cannot succeed merely by exporting the problem.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingDefine the system boundary before optimizing

Evidence and sources
Supports

System dynamics work emphasizes that well-intended interventions can be defeated by feedback-driven system responses, a pattern described as policy resistance.

A qualitative feedback story is not enough; links, delays and predicted behavior still need empirical or operational checking.

System Dynamics Modeling: Tools for Learning in a Complex World · Abstract

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details