Heuristic

Ask 'and then what?' before taking the first-order win

The first consequence gets the headline. The second one often sends the invoice.

About 1 min read

Before you use it

Use when
  • A decision has an attractive immediate effect but may change incentives, maintenance, behavior or future options.

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.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

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.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingAsk 'and then what?' before taking the first-order win

Evidence and sources
Supports

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details