inversion-thinking

Original source / Raw SKILL.md

---
name: inversion-thinking
description: Apply inversion thinking (thinking backwards) to solve problems, make decisions, and plan projects by identifying failure modes and avoiding them. Use when the user wants to apply Charlie Munger's mental model, wants to think backwards about a problem, asks "what could go wrong", wants to identify risks, or needs to pressure-test a plan or decision.
---

# Inversion Thinking

Inversion thinking is a powerful mental model popularized by Charlie Munger: instead of asking "How do I succeed?", ask "How would I guarantee failure?" By identifying all the ways something could fail, then inverting those failure modes, you reveal non-obvious risks and critical success factors.

## When to Use This Skill

Use inversion thinking when:
- Making important decisions or plans
- The user asks "what could go wrong?"
- Pressure-testing a strategy or approach
- Identifying hidden risks or blind spots
- The stakes are high and failure is costly
- Direct problem-solving feels stuck or incomplete

## Core Methodology

### Step 1: Reframe the Goal

Transform the forward goal into its inverse failure state.

**Pattern:** 
- Forward: "How do I [achieve goal]?"
- Inverse: "How would I guarantee failure at [goal]?"

**Examples:**
- Forward: "How do I build a successful product?" → Inverse: "How would I guarantee product failure?"
- Forward: "How do I improve team morale?" → Inverse: "How would I destroy team morale?"
- Forward: "How do I reduce my Facebook ad CPL?" → Inverse: "How would I make my CPL skyrocket?"

### Step 2: Brainstorm Failure Modes

Generate a comprehensive list of ways to fail. Be specific and concrete. Think across multiple dimensions.

**Key dimensions to explore:**
- Execution failures (poor implementation, timing, resources)
- Strategic failures (wrong market, wrong approach, wrong assumptions)
- People failures (wrong team, poor communication, misaligned incentives)
- External failures (competition, regulation, market shifts)
- Second-order failures (unintended consequences, downstream effects)

**Quality over completeness:** Aim for 5-15 high-impact failure modes rather than 50 superficial ones.

### Step 3: Invert Each Failure Mode

For each failure mode, identify:
1. **The anti-pattern to avoid** - What specifically causes this failure?
2. **The corrective action** - What should you do instead?
3. **Early warning signs** - How would you detect this failure early?

### Step 4: Synthesize Insights

Organize findings into actionable categories:

1. **Critical risks to mitigate** - Failure modes that would be catastrophic
2. **Hidden assumptions to validate** - Beliefs that might be wrong
3. **Non-obvious success factors** - Things you must get right that weren't obvious from forward thinking
4. **Early warning metrics** - Signals to monitor

### Step 5: Create Action Items

Convert insights into concrete next steps:
- What must you start doing?
- What must you stop doing?
- What must you measure or monitor?
- What assumptions must you test?

## Response Format

Structure your inversion analysis clearly:

1. **Restated Goal** - Confirm understanding
2. **Inverse Goal** - The failure state you're exploring
3. **Failure Modes** - Numbered list of specific ways to fail
4. **Inverted Insights** - For each failure mode, the corrective action
5. **Key Takeaways** - Synthesized insights organized by category
6. **Recommended Actions** - Concrete next steps

## Working Example

**User Goal:** "Help me plan my product launch strategy"

**Inverse Goal:** "How would I guarantee my product launch fails miserably?"

**Failure Modes:**
1. Launch with no audience - Build in isolation, tell no one, have zero marketing
2. Launch too early - Ship before the core value works, before testing with users
3. Launch too late - Spend years perfecting, miss market window, burn all resources
4. Wrong positioning - Confuse the market about what it is and who it's for
5. No feedback loop - Launch and disappear, don't iterate based on user response
6. Ignore competition - Assume you're unique, get blindsided by better alternatives
7. Poor technical foundation - Ship buggy product, lose trust immediately
8. No clear next step - Users try it once, don't know what to do next, never return

**Inverted Insights:**

1. **Build audience pre-launch**
   - Anti-pattern: Waiting until launch day to tell anyone
   - Action: Build email list, engage community, create anticipation 2-3 months early
   - Warning sign: No one knows you're building anything

2. **Balance speed with quality**
   - Anti-pattern: Perfect feature set vs. broken core experience
   - Action: Launch with working core value, minimum viable quality bar
   - Warning sign: Delays keep extending, no user feedback yet

3. **Crystal clear positioning**
   - Anti-pattern: "It's like X meets Y for Z use case"
   - Action: One sentence value prop tested with target users
   - Warning sign: Takes more than 10 seconds to explain what it does

**Key Takeaways:**

*Critical risks:*
- Launching to silence (no audience)
- Unclear value proposition

*Hidden assumptions to validate:*
- Users actually want this solution
- Market timing is right
- Core experience is good enough

*Non-obvious success factors:*
- Pre-launch audience building
- Clear positioning tested with users
- Fast iteration post-launch

**Recommended Actions:**
1. Start building email list now (target: 500+ by launch)
2. Write one-sentence value prop, test with 10 target users
3. Set launch quality bar: core feature works smoothly, not all features
4. Plan weekly updates post-launch based on user feedback
5. Research top 3 competitors: how will you differentiate?

## Best Practices

**Make it specific:** Generic failures ("bad execution") are less useful than specific ones ("ship with broken onboarding flow that confuses users")

**Think second-order:** Consider consequences of consequences. "Launch with no marketing" → "No users" → "No feedback" → "Build wrong features" → "Run out of runway"

**Calibrate to stakes:** High-stakes decisions warrant deeper failure analysis. Low-stakes decisions can use lighter treatment.

**Don't just list - analyze:** The value is in understanding WHY each failure mode matters and WHAT to do about it.

**Combine with forward thinking:** Inversion reveals risks and blindspots, but still pair with forward planning. Use both lenses.

## Common Pitfalls to Avoid

**Catastrophizing:** Inversion should reveal actionable risks, not spiral into anxiety. Keep it grounded and solution-focused.

**Analysis paralysis:** Don't let fear of failure prevent action. Use insights to make better decisions, not to avoid decisions.

**Stopping at problems:** Always complete the inversion - identify the corrective actions, not just the failure modes.

## Advanced Techniques

**Pre-mortem:** Imagine it's 6 months from now and the project failed spectacularly. Tell the story of what went wrong. This narrative approach often reveals failure chains.

**Constraints inversion:** Don't just invert the goal - invert your constraints. "What if I had unlimited budget?" or "What if I had to launch in 1 week?" reveals hidden assumptions.

**Stakeholder perspectives:** Apply inversion from different viewpoints - user, competitor, regulator, team member. Each reveals different failure modes.

## Integration with Other Mental Models

Inversion pairs well with:
- **Second-order thinking:** What are the consequences of the consequences?
- **Falsification:** What would prove this wrong?
- **Margin of safety:** How much buffer do you need given these failure modes?
- **Regret minimization:** Which failures would you regret most?

## Example Triggers

When you see phrases like these, consider using inversion thinking:
- "What could go wrong with..."
- "Help me pressure-test..."
- "What are the risks of..."
- "How do I avoid..."
- "What am I missing about..."
- "Charlie Munger would say..."
- "Think backwards about..."