systems-thinking-leverage

What this skill does

# Systems Thinking & Leverage Points

## Workflow

Copy this checklist and track your progress:

```
Systems Thinking & Leverage Progress:
- [ ] Step 1: Define system and problem
- [ ] Step 2: Map system structure
- [ ] Step 3: Identify leverage points
- [ ] Step 4: Validate and test interventions
- [ ] Step 5: Design high-leverage strategy
```

**Step 1: Define system and problem**

Clarify system boundaries (what's in/out of system), key variables (stocks that accumulate, flows that change them), and problem symptom vs. underlying pattern. Use [System Definition](#system-definition) section below.

**Step 2: Map system structure**

For simple cases → Use [resources/template.md](resources/template.md) for quick causal loop diagram and stock-flow identification. For complex cases → Study [resources/methodology.md](resources/methodology.md) for system archetypes, multi-loop analysis, and time delays.

**Step 3: Identify leverage points**

Apply Meadows' leverage hierarchy (parameters < buffers < structure < delays < balancing loops < reinforcing loops < information < rules < self-organization < goals < paradigms). See [Leverage Points Analysis](#leverage-points-analysis) below and [resources/methodology.md](resources/methodology.md) for techniques.

**Step 4: Validate and test interventions**

Self-assess using [resources/evaluators/rubric_systems_thinking_leverage.json](resources/evaluators/rubric_systems_thinking_leverage.json). Test mental models: what happens if we push here? What are second-order effects? What delays might undermine intervention? See [Validation](#validation) section.

**Step 5: Design high-leverage strategy**

Create `systems-thinking-leverage.md` with system map, leverage point ranking, recommended interventions, and predicted outcomes. See [Delivery Format](#delivery-format) section.

---

## System Definition

Before mapping, clarify:

**1. System Boundary**
- **What's inside the system?** (components you're analyzing)
- **What's outside?** (external forces you can't control)
- **Why this boundary?** (pragmatic scope for intervention)

**2. Key Variables**
- **Stocks**: Things that accumulate (employee count, technical debt, customer base, trust, knowledge)
- **Flows**: Rates of change (hiring rate, bug introduction rate, churn rate, relationship building rate)
- **Goals**: What the system is trying to achieve (may be implicit)

**3. Time Horizon**
- **Short-term** (weeks-months): Focus on flows and immediate feedback
- **Long-term** (years): Focus on stocks, paradigms, and structural change

**4. Problem Statement**
- **Symptom**: What's the observable issue? (e.g., "customer churn is 30%/year")
- **Pattern**: What's the recurring dynamic? (e.g., "onboarding improvements work briefly then churn returns")
- **Hypothesis**: What feedback loop might explain this? (e.g., "quick onboarding sacrifices depth → users don't see value → churn → pressure for faster onboarding")

---

## Leverage Points Analysis

**Meadows' 12 Leverage Points** (ascending order of effectiveness):

**12. Parameters** (weak) - Constants, numbers (tax rates, salaries, prices)
- Easy to change, low resistance
- Effects are linear and temporary
- Example: Increase training budget 20%

**11. Buffers** - Stock sizes relative to flows (reserves, inventories)
- Larger buffers increase stability but reduce responsiveness
- Example: Increase runway from 6 to 12 months

**10. Stock-and-Flow Structures** - Physical system design
- Hard to change once built (buildings, infrastructure)
- Example: Redesign office for collaboration vs. heads-down work

**9. Delays** - Time lags in information flows
- Reducing delays improves responsiveness (if system is agile)
- Too-short delays can cause instability
- Example: Daily feedback vs. annual reviews

**8. Balancing Feedback Loops** - Strength of stabilizing forces
- Weaken to enable growth, strengthen to prevent overshoot
- Example: Make incident post-mortems blameless (weaken fear loop)

**7. Reinforcing Feedback Loops** - Strength of amplifying forces
- Strengthen positive loops (learning), weaken negative loops (burnout)
- Example: Invest in developer tools → faster builds → more experiments → better tools

**6. Information Flows** - Who has access to what information
- Make consequences visible to those who can act
- Example: Show developers the support tickets caused by their code

**5. Rules** - Incentives, constraints, punishments
- Shape what behaviors are rewarded
- Example: Tie bonuses to team outcomes not individual metrics

**4. Self-Organization** - Power to add/change/evolve structure
- Enable system to adapt and evolve
- Example: Let teams choose their own tools and processes

**3. Goals** - Purpose the system serves
- Changing goals redirects the entire system
- Example: Shift from "ship features fast" to "solve user problems sustainably"

**2. Paradigms** - Mindset from which the system arises
- Assumptions, worldview, mental models
- Example: Shift from "employees are costs" to "employees are investors of human capital"

**1. Transcending Paradigms** (strongest) - Ability to shift between paradigms
- Meta-level: recognizing paradigms are just one lens
- Example: Hold "growth" and "sustainability" paradigms simultaneously, choose contextually

**How to Use This Hierarchy:**
1. List all possible intervention points
2. Classify each by leverage level (1-12)
3. Prioritize high-leverage interventions (1-7) over low-leverage (8-12)
4. Consider feasibility: High leverage often faces high resistance

---

## Validation

Before finalizing, check:

**System Map Quality:**
- [ ] All major feedback loops identified (R for reinforcing, B for balancing)?
- [ ] Stocks and flows distinguished (nouns vs. verbs)?
- [ ] Delays explicitly noted (with estimated time lag)?
- [ ] System boundary clear (what's in/out)?
- [ ] Connections show polarity (+ same direction, - opposite direction)?

**Leverage Point Analysis:**
- [ ] Multiple intervention points considered (not just first idea)?
- [ ] Each intervention classified by leverage level (1-12)?
- [ ] High-leverage interventions identified and prioritized?
- [ ] Trade-offs acknowledged (leverage vs. feasibility)?
- [ ] Second-order effects anticipated (what else changes)?

**Archetype Recognition** (if applicable):
- [ ] Does system match known archetype (fixes that fail, shifting the burden, tragedy of commons, etc.)?
- [ ] If yes, what's the typical failure mode for this archetype?
- [ ] What's the high-leverage intervention for this archetype?

**Mental Model Testing:**
- [ ] What happens if we intervene at this leverage point?
- [ ] What are unintended consequences (delays, compensating loops)?
- [ ] Will the system resist this intervention? How?
- [ ] What needs to change for intervention to stick?

**Minimum Standard:** Use rubric (resources/evaluators/rubric_systems_thinking_leverage.json). Average score ≥ 3.5/5 before delivering.

---

## Delivery Format

Create `systems-thinking-leverage.md` with:

**1. System Overview**
- Boundary definition
- Key stocks and flows
- Problem statement (symptom → pattern → hypothesis)

**2. System Map**
- Causal loop diagram (text or ASCII representation)
- Feedback loops identified (R1, R2, B1, B2, etc.)
- Stock-flow structure (if relevant)
- Delays noted

**3. Leverage Point Analysis**
- All candidate interventions listed
- Classification by leverage level (1-12)
- Trade-off analysis (leverage vs. feasibility)
- Recommended high-leverage interventions (rank-ordered)

**4. Intervention Strategy**
- Primary intervention (highest leverage and feasible)
- Supporting interventions (reinforce primary)
- Predicted outcomes (based on feedback loop dynamics)
- Risks and unintended consequences
- Success metrics (leading and lagging indicators)

**5. Implementation Considerations**
- Resistance points (where system will push back)
- Time horizon (when to expect results given delays)
- Monitoring plan (what to track to validate model)

---

##