systems-thinking

refoundai/lenny-skills

Apply systems thinking to understand complex dynamics, multi-stakeholder problems, and second-order effects.

What is systems-thinking?

This skill helps you think systematically about complex problems by mapping players and incentives, identifying stocks and flows, tracing cascading effects, and finding high-leverage intervention points. Use it when dealing with multi-stakeholder challenges, platform ecosystems, organizational dynamics, or situations where first-order solutions create unintended consequences.

Map systems by identifying all players, their incentives, and interactions
Distinguish stocks (things that accumulate) from flows (movement between states)
Trace second, third, and fourth-order effects of decisions
Identify feedback loops—both reinforcing and balancing
Find leverage points where small interventions create large systemic changes
Systematize recurring manual pains into automated processes or frameworks

How to install systems-thinking

npx skills add https://github.com/refoundai/lenny-skills --skill systems-thinking

Claude Code

Cursor

Windsurf

Cline

How to use systems-thinking

1.Identify all players in the system and map their individual incentives
2.List what accumulates (stocks) and what moves between states (flows) in your system
3.Trace the immediate impact of a proposed change, then work through second and third-order effects
4.Identify reinforcing and balancing feedback loops that amplify or dampen changes
5.Ask: what constraint, if removed, would unlock the most value?
6.Look for recurring manual pains that could be systematized or automated

Use cases

Good for

Analyzing how a product change ripples through a multi-sided marketplace and affects all user groups
Understanding hiring pipeline dynamics and bottlenecks in organizational growth
Designing platform ecosystems where developer, user, and company incentives must align
Evaluating organizational restructuring impacts across teams and workflows
Identifying root causes of recurring problems rather than treating symptoms

Who it's for

Product managers handling complex multi-stakeholder trade-offs
Platform and ecosystem leaders
Organizational strategists and leaders
Anyone analyzing complex systems with interdependent parts

systems-thinking FAQ

When should I use systems thinking vs. other frameworks like Jobs-to-be-Done?

Systems thinking excels at handling complex product trade-offs and multi-agent incentives where multiple stakeholders have competing goals. Use it when you need to understand how all players interact, not just end-user motivations.

How do I avoid optimizing one part of the system and making the whole system worse?

Always trace effects beyond the immediate change. Ask what happens next, and then what happens after that. Map feedback loops to see if your optimization creates unintended consequences elsewhere in the system.

What's the difference between stocks and flows?

Stocks are things that accumulate over time (like users in a funnel, cash in a bank account, or institutional knowledge). Flows are the movement between states (like new user signups, cash transfers, or knowledge transfer between team members).

How do I identify the highest-leverage intervention point?

Look for constraints that, if removed, would unlock disproportionate value. These are often bottlenecks in flows, misaligned incentives between key players, or feedback loops that are currently dampening growth.

What's a common mistake when applying systems thinking?

Only seeing first-order effects and ignoring how changes ripple through the system. Also common: assuming all players share your incentives rather than responding to their own. Always map incentives explicitly.

Full instructions (SKILL.md)

Source of truth, from refoundai/lenny-skills.

name: systems-thinking description: Help users think in systems and understand complex dynamics. Use when someone is dealing with multi-stakeholder problems, trying to understand second-order effects, managing platform ecosystems, or analyzing complex organizational dynamics.

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:

Map the system - Help them identify all players, their incentives, and how they interact with each other
Identify stocks and flows - Understand what accumulates (stocks) and what moves between states (flows)
Trace second-order effects - Work through what happens after the first-order impact of any change
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