systems-thinking
This Claude Code skill teaches systems thinking frameworks by helping users map complex problems across multiple stakeholders, their incentives, and cascading effects. Use it when analyzing multi-agent dynamics, understanding second and third-order consequences of decisions, identifying leverage points in organizational or platform ecosystems, or designing solutions that account for how changes ripple through interconnected systems rather than treating problems in isolation.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/systems-thinking && cp -r /tmp/systems-thinking/skills/systems-thinking ~/.claude/skills/systems-thinkingSKILL.md
# Systems Thinking Help the user apply systems thinking to complex problems using frameworks and insights from 6 product leaders. ## How to Help When the user asks for help with systems thinking: 1. **Map the system** - Help them identify all players, their incentives, and how they interact with each other 2. **Identify stocks and flows** - Understand what accumulates (stocks) and what moves between states (flows) 3. **Trace second-order effects** - Work through what happens after the first-order impact of any change 4. **Find leverage points** - Identify where small interventions can create large systemic changes ## Core Principles ### See the system Seth Godin: "What does it mean to be a strategic thinker? It means to see the system." Understanding the invisible rules, culture, and interoperability that govern how products and organizations succeed or fail is the foundation of strategic thinking. ### Think about all players and incentives Sriram: "Systems thinking. Think of all the players in the system, think of all of their incentives and how they interact with each other." This approach is superior to Jobs-to-be-Done for handling complex product trade-offs and multi-agent incentives. ### Use stocks and flows Will Larson: "Systems thinking is basically you try to think about stocks and flows. Stocks are things that accumulate and flows are the movement from a stock to another thing." Model business processes like hiring pipelines or user funnels using this framework. ### Consider second, third, and fourth-order effects Hari Srinivasan: "The skillsets that you think through and manage in a complicated ecosystem are quite different." Managing complex ecosystems requires understanding effects that cascade beyond the immediate impact. ### Think beyond today's decisions Nickey Skarstad: "Second order thinking is you being able to think beyond the decisions that you're making today." Consider how current decisions impact future constraints and ecosystem dynamics. ### Automate recurring pains Melissa Perri + Denise Tilles: "Tell me about some process you really hated and ended up trying to automate or build a system around to make it better." Identify recurring manual pains and build automated systems or frameworks to solve them. ## Questions to Help Users - "Who are all the players in this system, and what does each one want?" - "If you make this change, what happens next? And then what happens after that?" - "What accumulates over time in this system (the stocks), and what flows between states?" - "Where are the feedback loops - both reinforcing and balancing?" - "What constraint, if removed, would unlock the most value in this system?" - "What recurring manual pain could be systematized?" ## Common Mistakes to Flag - **Only seeing first-order effects** - Changes ripple through systems in ways that aren't immediately obvious - **Ignoring incentives** - Every player in a system responds to their own incentives, not yours - **Optimizing locally** - Improving one part of a system can make the whole system worse - **Missing feedback loops** - Many systems have self-reinforcing or self-balancing dynamics that amplify or dampen changes - **Treating symptoms instead of causes** - Systems problems often require addressing root causes, not visible symptoms ## Deep Dive For all 6 insights from 6 guests, see `references/guest-insights.md` ## Related Skills - Setting OKRs & Goals - Defining Product Vision - Platform Strategy - Organizational Design
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.