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

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

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

ID: MHC-D-RESEARCH-0341 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/ask-and-then-what-before-taking-the-first-order-win

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

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

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

### Avoid when

- 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.

### Explanation

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.

### 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

The decision record includes at least one plausible downstream effect that changes a safeguard, metric or choice.

### Limits

- 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

- supports: Untools presents second-order thinking as examining immediate effects and repeatedly asking 'And then what?' to consider downstream consequences. — RS-27D35EF007D811A8. Further-order consequences become increasingly uncertain; the exercise should surface possibilities and tests rather than pretend to forecast everything. (How to use it)
- RS-27D35EF007D811A8: Second-order thinking — https://www.untools.co/second-order-thinking/

No review details supplied.
