thinking-second-order

1# Second-Order Consequence Chains
2 
3Do not stop at the intended first effect. Trace what happens next across actors, time, and feedback until the chain stops changing the decision.
4 
5## When to Use
6 
7- Strategic, policy, incentive, or architecture choices with lasting coupling.
8- The obvious fix feels too easy or has known backfire patterns.
9- Success or scale would create new problems (load, gaming, debt).
10- Need to compare options by delayed effects, not only day-one benefit.
11 
12## When NOT to Use
13 
14- Local reversible edit with no incentive or cross-component coupling—just ship and observe.
15- Full system structure (stocks, many loops, leverage ranking) is the goal—use systems.
16- Pre-mortem of failure modes for a plan already chosen—use pre-mortem.
17- Pure mechanical changes (rename, format) with no behavioral effect.
18 
19## Procedure
20 
211. **State decision and first-order effect.** One sentence each: action and intended immediate result.
222. **Chain "and then what?"** At least two further orders. For each link record: effect, who responds, rough probability (high/med/low), timing (immediate / next cycle / at scale), and whether it feeds back into the original problem (reinforce or counteract).
233. **Expand affected parties.** Who else reacts (users, operators, other teams, attackers, markets)? What incentives does the change create or destroy?
244. **Scale test.** Ask what happens if everyone does this or usage grows 10x. Mark paths that only appear under scale or repetition.
25…