apply-systems-thinking

name	Apply Systems Thinking
description	Understand complex problems by mapping all players, incentives, and feedback loops instead of optimizing individual pieces. See second, third, and fourth-order effects before making decisions. Identify leverage points where small changes create outsized impact. Use stocks and flows to understand what accumulates and what moves. Trigger on: strategy decision, product launch, process redesign, conflict resolution, market analysis, organizational change.
dependencies	[]
connectors	[{"name":"Google Docs","reason":"Diagram systems, map stakeholders, document feedback loops and leverage points"},{"name":"Notion","reason":"Create decision logs and hypothesis tracking as you test system changes"},{"name":"Slack","reason":"Share system diagrams, gather perspectives from different teams and stakeholders"},{"name":"Linear","reason":"Track second and third-order consequences of feature launches or organizational changes"}]
author	Harmony
version	1.0.0
icon	sparkles
cover
screenshots	[]
category	Strategy

Purpose

Systems thinking is the practice of seeing interconnected wholes instead of isolated pieces. Most problems we face aren't siloed—they're embedded in networks of cause and effect, where decisions ripple across time and stakeholders. When you optimize one part of a system without understanding the whole, you create unintended consequences. Systems thinking forces you to map all the players involved, understand what incentives drive their behavior, trace how changes propagate, and identify the highest-leverage intervention points. This discipline prevents you from solving a symptom instead of the root cause.

When to Use

• Strategic decisions with wide impact: When you're deciding on pricing, go-to-market motion, or organizational structure, map the system first
• Resolving persistent conflicts: When the same problem keeps recurring, the symptom treatment isn't working—map the incentives driving the behavior
• Designing marketplaces or platforms: Two-sided networks have complex feedback loops between supply and demand, quality and volume, price and usage
• Product launch planning: Before launching a feature, trace what changes for users, competitors, your business, and adjacent products
• Organizational change or restructuring: Changing reporting lines, compensation, or processes has ripple effects you can't see without systems analysis
• Understanding customer behavior: Why do customers churn? Map the incentives, switching costs, and alternative options—the root cause probably isn't what you think
• Competitive positioning: Don't just compare features—map the entire system of how customers, competitors, and complementary products interact

Instructions

1. Identify the system boundaries and key players

   • Define what you're analyzing: a product feature, a market, an organization, a process
   • List all the actors: your company, customers, competitors, suppliers, regulators, partners
   • Map their incentives: what does each player want? Money, status, convenience, control?
   • Note dependencies: who depends on whom? What happens if one player drops out?
   • Draw this as a simple diagram with boxes (players) and arrows (relationships, money flows, information flows)

2. Define stocks and flows

   • Stocks are quantities that accumulate: customer base, cash, brand reputation, technical debt
   • Flows are rates at which things move between states: customer acquisition rate, churn rate, hiring rate, defect rate
   • Ask for each stock: what fills it (inflow)? What drains it (outflow)? What's the current level?