Problem Analysis
Systems Thinking - Feedback Loop Mapping
Map reinforcing and balancing loops behind a problem that keeps undoing the fix, then pick a high-leverage intervention.
The Prompt
systems-thinking-feedback-loops.md
You are a systems thinker mapping feedback loops behind a persistent problem. THE RECURRING PROBLEM: {{problem}} THE SYSTEM IT LIVES IN: {{system}} WHAT'S BEEN TRIED: {{tried}} INSTRUCTIONS: 1. Identify 5 - 8 key variables (things that go up or down and affect each other). 2. Map causal relationships: for each pair, whether an increase in one causes an increase (reinforcing) or decrease (balancing) in the other. 3. Identify at least one reinforcing loop and one balancing loop relevant to the problem. 4. Explain, using the loop(s), why previous fixes may have failed or reverted. 5. Identify the highest-leverage intervention point (changing a goal, rule, or feedback structure usually beats changing a single parameter). 6. Propose one intervention at that point, and predict how the system might resist or adapt so the resistance can be planned for. OUTPUT FORMAT: - Key variables list - Causal map (one line per link: "A increases → B increases (reinforcing)") - Identified loop(s) with a one-paragraph explanation of how each operates - Why past fixes reverted, via the loop(s) - Highest-leverage intervention + why it's higher-leverage than the others - Proposed intervention + predicted system resistance CONSTRAINTS: - Do not propose a fix before the loop mapping is done. - If this is a one-off, not a recurring system pattern, say so honestly instead of forcing a systems-thinking frame.
Negative prompt
Included when you copy the prompt
Do not skip loop mapping and jump to a fix. Do not force loops onto a one-off incident. Do not invent variables or past fixes that were not described.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 3 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
systems-thinking-feedback-loops.md
Prompt preview
You are a systems thinker mapping feedback loops behind a persistent problem. THE RECURRING PROBLEM: {{problem}} THE SYSTEM IT LIVES IN: {{system}} WHAT'S BEEN TRIED: {{tried}} INSTRUCTIONS: 1. Identify 5 - 8 key variables (things that go up or down and affect each other). 2. Map causal relationships: for each pair, whether an increase in one causes an increase (reinforcing) or decrease (balancing) in the other. 3. Identify at least one reinforcing loop and one balancing loop relevant to the problem. 4. Explain, using the loop(s), why previous fixes may have failed or reverted. 5. Identify the highest-leverage intervention point (changing a goal, rule, or feedback structure usually beats changing a single parameter). 6. Propose one intervention at that point, and predict how the system might resist or adapt so the resistance can be planned for. OUTPUT FORMAT: - Key variables list - Causal map (one line per link: "A increases → B increases (reinforcing)") - Identified loop(s) with a one-paragraph explanation of how each operates - Why past fixes reverted, via the loop(s) - Highest-leverage intervention + why it's higher-leverage than the others - Proposed intervention + predicted system resistance CONSTRAINTS: - Do not propose a fix before the loop mapping is done. - If this is a one-off, not a recurring system pattern, say so honestly instead of forcing a systems-thinking frame.
When to use this prompt
Use it when
- You need help with managers.
- You need help with engineers.
- You need help with operators.
- You need help with founders.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
The output clearly completes “Systems Thinking - Feedback Loop Mapping”: it matches the requested format, uses your filled-in details, and is ready to use without another prompting round.
Common mistakes
- Leaving problem, system, tried vague - the model then invents placeholders.
- Asking ChatGPT, Claude, Gemini, or Perplexity for a shorter answer after a long structured prompt - that throws away the format rules.
- Running it once without providing your constraints, stack, or examples of good/bad output.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: problem, system, tried. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini, Perplexity. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- The output clearly completes “Systems Thinking - Feedback Loop Mapping”: it matches the requested format, uses your filled-in details, and is ready to use without another prompting round.
- What are common mistakes with this prompt?
- Leaving problem, system, tried vague - the model then invents placeholders. Asking ChatGPT, Claude, Gemini, or Perplexity for a shorter answer after a long structured prompt - that throws away the format rules. Running it once without providing your constraints, stack, or examples of good/bad output.
Best for
- Managers
- Engineers
- Operators
- Founders
Related Prompts
More prompts like this — same topic and style.

