Heuristic
Ask 'and then what?' before taking the first-order win
The first consequence gets the headline. The second one often sends the invoice.
When it fits
- A decision has an attractive immediate effect but may change incentives, maintenance, behavior or future options.
When to avoid it
- Do not invent an endless consequence chain; uncertainty grows with each step, so stop when the branch no longer changes the decision or test plan.
Why it matters
Write the immediate likely effect of the decision, then ask what that effect makes more likely next. Repeat for a few meaningful branches and time horizons. Look especially for feedback, adaptation, lock-in and transferred costs. Treat later consequences as scenarios to investigate, not predictions disguised as certainty.
An example
Automating a manual review may save time first, then reduce human exposure to edge cases, which may change how quickly new failure modes are noticed.
Check your result
The decision record includes at least one plausible downstream effect that changes a safeguard, metric or choice.
Keep this limit in mind
- Do not invent an endless consequence chain; uncertainty grows with each step, so stop when the branch no longer changes the decision or test plan.
Evidence and sources
Untools presents second-order thinking as examining immediate effects and repeatedly asking 'And then what?' to consider downstream consequences.
Further-order consequences become increasingly uncertain; the exercise should surface possibilities and tests rather than pretend to forecast everything.
Second-order thinking · How to use it