Menu
"The symptom you see is downstream from the structure you built." Systems thinking for founders: map causal loops, find leverage points, trace effects, diagnose delays, and match system archetypes.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | systems-orchestrator |
| description | The symptom you see is downstream from the structure you built. |
| Systems thinking for founders | map causal loops, find leverage points, trace effects, diagnose delays, and match system archetypes. |
| category | deep-thinking |
| version | 1.0.0 |
| tags | ["systems-thinking","causal-loop-diagrams","leverage-points","feedback-loops","archetypes","founder-decisions"] |
| operations | ["map-system","find-leverage","trace-effects","diagnose-delays","archetype-match"] |
The Systems Orchestrator is a framework for founders to see beyond symptoms and understand the underlying structures that drive their startups' behavior. It equips you to diagnose complex problems, identify high-leverage interventions, and anticipate cascading effects of your decisions.
Core Philosophy: "The symptom you see is downstream from the structure you built."
This skill provides a structured approach to:
Startup challenges rarely have simple, single-cause solutions. Problems like:
are often symptoms of underlying system structures, not isolated problems. Systems thinking helps you see the whole picture and fix the root cause, not just the symptom.
Visualize the system's structure by mapping causal relationships and feedback loops.
Step-by-Step Protocol:
A → B means "A causes B to change in the same direction"A ← B means "A causes B to change in the opposite direction"R: Reinforcing loop (amplification)B: Balancing loop (stabilization)|| symbolsKey Questions:
Identify where interventions will have the greatest impact using Donella Meadows' hierarchy of leverage points (from most to least powerful):
Step-by-Step Protocol:
Key Questions:
Anticipate second-, third-, and Nth-order effects of a decision.
Step-by-Step Protocol:
Key Questions:
Delays often cause oscillation, instability, and wrong decisions.
Step-by-Step Protocol:
Key Questions:
Match your situation to common archetypes to access proven solutions.
Step-by-Step Protocol:
Key Archetypes & Solutions:
| Archetype | Symptoms | Solution |
|---|---|---|
| Fixes That Fail | Problem comes back worse | Stop the fix; address root cause |
| Shifting the Burden | Dependency on symptomatic fixes | Strengthen the fundamental solution |
| Limits to Growth | Growth stalls | Remove or attenuate the limit |
| Eroding Goals | Standards keep slipping | Lock in goals; create better feedback |
| Escalation | Competitive spiral | Break the loop; find win-win |
| Success to Successful | Winners take all | Diversify allocation; level playing field |
For most founder challenges, follow this workflow:
1. map-system
↓
2. archetype-match (see if it's a known pattern)
↓
3. find-leverage (identify high-impact interventions)
↓
4. trace-effects (anticipate consequences)
↓
5. diagnose-delays (check for timing issues)
↓
6. Iterate as needed
Shortcut: If it's clearly one of the classic archetypes, you can jump straight to archetype-match, but mapping first is still recommended.
Symptom: User acquisition goes up when we spend on ads, then crashes right after, even with continued spending.
map-system Output:
Ad Spend → New Users → Churn → (loss of users)
↓
Monthly Active Users (MAU)
↓
Revenue ← Ad Spend (cost)
↓
Profit ↓ → Ad Budget Cuts || → Ad Spend ↓
(delay: reporting takes 2 weeks)
archetype-match: Oscillation from delayed feedback
find-leverage:
trace-effects of real-time reporting:
Outcome: Smoother user growth without wild oscillations
Symptom: We rush to ship features, team works overtime, burns out, productivity drops, then we rush even more to catch up.
map-system Output:
Deadline Pressure → Overtime → Burnout || → Productivity ↓
↑ ↓
Missed Deadlines ← Delivery Delay ← Productivity ↓
archetype-match: Escalation + Fixes That Fail (the "fix" of overtime makes the problem worse)
find-leverage:
trace-effects of overtime limit:
Outcome: Breaking the burnout cycle and building a sustainable team
Symptom: We grew fast for 6 months by hiring more salespeople, but now growth is flat even with more hires.
map-system Output:
Hiring → Sales Team Size → New Customers ← Market Saturation ||
↑ ↓
Revenue ← New Customers → (Market approaches saturation)
archetype-match: Limits to Growth
find-leverage:
trace-effects of expanding to new market:
Outcome: Breaking through the growth ceiling by expanding the market
| Goal | Operation |
|---|---|
| Understand what's really going on | map-system |
| Find where to intervene for max impact | find-leverage |
| Avoid unintended consequences | trace-effects |
| Fix oscillations or instability | diagnose-delays |
| Use proven solutions for classic problems | archetype-match |
| What You See | Likely Archetype |
|---|---|
| Problem keeps coming back worse | Fixes That Fail |
| Addicted to quick fixes | Shifting the Burden |
| Growth stalls despite effort | Limits to Growth |
| Standards keep slipping | Eroding Goals |
| Competitive arms race | Escalation |
| Rich get richer, poor get poorer | Success to the Successful |
This skill will evolve as you apply it:
"Systems thinking is a discipline for seeing wholes. It is a framework for seeing interrelationships rather than things, for seeing patterns of change rather than static 'snapshots.'" — Peter Senge
Uncovers, challenges, and validates hidden assumptions in ideas, plans, and decisions. Helps users excavate implicit beliefs, categorize them by risk and impact, design tests to validate them, build dashboards to track them, and stress-test them under various scenarios.
Systematically applies Charlie Munger's inversion principle to identify failure modes, work backwards from success, and design robust strategies by asking "What would guarantee this fails?" before asking "How to make this succeed?"
A framework for managing paradoxes and polarities that founders face, not solving them. Helps identify tensions, map polarities, diagnose current positions, generate corrective actions, and monitor polarity balance over time.
Decision framework engine that serves as the central coordination hub for skill selection, context synthesis, and multi-domain problem decomposition. Analyzes user requests and orchestrates appropriate skills to generate optimal solutions.
Helps users rapidly learn any domain and build cross-domain knowledge connections, becoming a "T-shaped" generalist who can connect experts across fields. Use when users need to quickly understand a new field, find cross-domain connections, or build efficient learning paths.
Guides users from vague ideas to clear direction through the "Doubt + Reconstruction" framework, helping users clarify their true needs and establish a clear development roadmap.