domains / families / general / thinking-second-order

thinking-second-order

separate

When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

When to use

• Strategic, policy, incentive, or architecture choices with lasting coupling.
• The obvious fix feels too easy or has known backfire patterns.
• Success or scale would create new problems (load, gaming, debt).
• Need to compare options by delayed effects, not only day-one benefit.

When not to use

• Local reversible edit with no incentive or cross-component coupling—just ship and observe.
• Full system structure (stocks, many loops, leverage ranking) is the goal—use systems.
• Pre-mortem of failure modes for a plan already chosen—use pre-mortem.
• Pure mechanical changes (rename, format) with no behavioral effect.

Skill page

Source