thinking-leverage-points
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:
More from tjboudreaux/cc-thinking-skills
thinking-scientific-method
Hypothesis → Prediction → Test → Revise with explicit falsification. Use for debugging, feature experimentation, performance investigation, and A/B testing design.
29thinking-model-router
Route to the right mental model based on your domain and problem type. The single entry point for all thinking skills.
29thinking-socratic
Systematic questioning framework to deepen understanding, challenge assumptions, and uncover hidden beliefs. Use for requirements gathering, debugging, coaching, and critical analysis.
29thinking-inversion
Approach problems backward by identifying paths to failure, then systematically avoiding them. Use for risk identification, planning, and avoiding obvious mistakes.
28thinking-probabilistic
Express confidence in ranges, update predictions with new information, and track calibration over time. Use for project estimation, risk assessment, and decision making under uncertainty.
27thinking-red-team
Deliberately attack your own plans, systems, and assumptions to find weaknesses before adversaries or reality does. Use for security review, architecture validation, plan stress-testing, and pre-launch preparation.
27