---
user-invocable: true
name: second-order
description: Think through consequences - and then what? and then what?
tokens: ~250
cloud-ok: true
---

# Second-Order Thinking
#claudeai

## The Framework

First-order thinking: What's the immediate result?
**Second-order thinking: And then what?**

Most people stop at first-order. The best thinkers go 2-3 levels deep.

## How to Use

### Step 1: Identify the action or decision
"If I do X..."

### Step 2: First-order consequence
"...then Y will happen."

### Step 3: Keep asking "And then what?"
"And then Z will happen..."
"And then W will happen..."

### Step 4: Evaluate the full chain
Is the end state better or worse than it appeared at first glance?

## Example

**Decision:** Lower prices to win more customers

**First-order:** More customers (good!)

**Second-order:** Lower margins, need more volume to sustain

**Third-order:** Have to cut costs somewhere, maybe quality or support

**Fourth-order:** Customer experience degrades, churn increases

**Fifth-order:** Back where we started, but with lower prices locked in

**Conclusion:** Price cut might create a trap.

## Output Format

```
## Second-Order Thinking: [Decision/Action]

**Action:** [What you're considering]

**Consequences chain:**

1st order: [Immediate result]
   ↓
2nd order: [And then what?]
   ↓
3rd order: [And then what?]
   ↓
4th order: [And then what?]

**End state:** [Where does this lead?]

**Hidden costs/benefits:**
- [Things not obvious at first order]

**Better informed decision:**
[What you'd do knowing the full chain]
```

## Common Second-Order Effects

| First-Order | Second-Order |
|-------------|--------------|
| Hire fast | Culture dilutes, quality drops |
| Cut prices | Competitors match, race to bottom |
| Add features | Complexity increases, maintenance burden |
| Raise money | Pressure to grow, loss of control |
| Fire someone | Team morale shifts, workload redistributes |
| Say yes to customer request | Sets precedent, more requests |

## The Chesterton's Fence Principle

Before removing something, understand why it exists.

"If you don't understand why a fence was built, don't tear it down."

That "dumb process" might be preventing a second-order problem you haven't experienced yet.

## When to Use

- Big decisions with long-term consequences
- When something seems obviously good (check for hidden costs)
- When something seems obviously bad (check for hidden benefits)
- When changing systems others built

---

*"The most important thing is to think of what the consequences of the consequences are."* — Howard Marks