Systems Thinking Skill

Goal

To understand the system as a whole, specifically focusing on relationships, feedback loops, and delays, rather than looking at isolated parts. Use this when solving stubborn, recurring problems or designing robust architectures.

Steps

1. The Iceberg Model Analysis

   • Events (React): What just happened? (The bug/incident)
   • Patterns (Anticipate): What trends have been happening over time?
   • Structures (Design): What influenced the patterns? (Architecture, Org chart, Incentives)
   • Mental Models (Transform): What assumptions/beliefs keep the system in place?

2. Causal Loop Diagramming (CLD)

   • Identify variables (e.g., "Code Quality", "Velocity", "Tech Debt").
   • Map relationships (S = Same direction, O = Opposite direction).
   • Identify Loops:
     • Reinforcing (R): Exponential growth/collapse (Virtuous/Vicious cycles).
     • Balancing (B): Goal-seeking/Stabilizing.
   • Output: Mermaid diagram or text-based CLD.