thinking-leverage-pointslisted

# Leverage Points ## Overview Donella Meadows' "Places to Intervene in a System" provides a hierarchy of intervention points ranked by their power to change system behavior. Most effort goes into low-leverage interventions (parameters, buffers) when high-leverage points (goals, paradigms) offer transformational change with less force. **Core Principle:** The higher in the hierarchy, the more leverage—but also the more resistance. Find the highest leverage point you can actually move. ## When to Use - Choosing where to focus engineering effort - Prioritizing system improvements - Organizational change initiatives - Architecture evolution decisions - Process optimization - Resource allocation - When incremental changes aren't working Decision flow: ``` Want to change system behavior? → Have you tried high-leverage interventions? → no → START HIGHER → Are you stuck at low leverage? → yes → MOVE UP THE HIERARCHY → Is change not sticking? → yes → LOOK FOR BALANCING LOOPS ``` ## The 12 Leverage Points (Low to High) ### Level 12: Constants and Parameters (LOWEST LEVERAGE) **What:** Numbers—budgets, rates, thresholds, timeouts **Examples:** - Adjusting cache TTL - Changing retry counts - Modifying timeout values - Tweaking rate limits **Why low leverage:** Parameters rarely change behavior fundamentally. The system absorbs parameter changes and continues its pattern. ``` Intervention: Increase server timeout from 30s to 60s Result: Slow requests succeed, but root c