thinking-systems

1# Systems Mapping and Leverage
2 
3Treat the problem as structure and interaction, not isolated parts. Map boundary, stocks/flows, loops/delays, and recurring patterns; intervene at the highest feasible leverage after a side-effect check.
4 
5## When to Use
6 
7- Symptom spans services/components; single-stack fixes fail or bounce.
8- A change in one place breaks another; behavior is emergent.
9- Problem recurs despite local fixes (structure, not only symptom).
10- Need to rank interventions when parameter/buffer tweaks do not stick.
11 
12## When NOT to Use
13 
14- Single-component linear bug with clear stack/diff—trace and fix.
15- Throughput limited by one obvious stage—use theory-of-constraints.
16- Decision is a consequence chain of one proposed action—use second-order.
17- Approach selection (plan vs probe vs stabilize)—use cynefin first.
18 
19## Procedure
20 
211. **Bound the system.** Name purpose, actors, boundary, and in/out flows. Exclude noise outside the decision horizon; include any path that can feed the symptom.
222. **Map stocks and flows.** List accumulating stocks (queue depth, debt, cache size, WIP) and the rates that fill/drain them. Note what changes slowly even when flows jump.
23…