systems-leveragelisted

# Systems Leverage **Problem shape:** the system misbehaves as a whole while every part looks locally fine. Interventions at the parameter level keep failing because the structure — feedback loops, stocks, delays, governance rules — produces the behavior. The move: map the structure, rank the leverage points, intervene as high as is accessible. ## Relevant geniuses | Agent | Use when | |---|---| | [meadows](../../agents/genius/meadows.md) | many possible interventions, unclear where to focus; recurring archetype; confusing accumulation-and-delay behavior | | [beer](../../agents/genius/beer.md) | organization fails despite local fixes — audit the five viable-system functions; variety mismatch with the environment | | [kauffman](../../agents/genius/kauffman.md) | system too rigid or too chaotic — tune connectivity; explore the adjacent possible instead of leaping | | [deming](../../agents/genius/deming.md) | management reacts to noise; quality inspected in at the end instead of built into the process | | [ostrom](../../agents/genius/ostrom.md) | a shared resource (build pipeline, on-call, budget, commons) is being depleted — check the eight design principles, rules-in-use vs rules-on-paper | | [margulis](../../agents/genius/margulis.md) | competing units would gain more by merging — symbiosis as an architectural option | | [rogers](../../agents/genius/rogers.md) | a change/tool isn't being adopted — segment the adopters, diagnose the chasm, audit the innovation's attributes