---
title: "Ask for the Step Before the Answer"
description: "Before you trust an AI answer you cannot check, ask for the step it was built from."
author: "Harry Floyd"
publication: "The Durability Curve"
canonical: "https://durabilitycurve.com/blog/ask-for-the-step-before-the-answer/"
date: "2026-09-16"
series: "THE BRIEF"
law: "Law IV"
format: "markdown mirror of the canonical HTML page; figures are named, not embedded"
---

# Ask for the Step Before the Answer

*Before you trust an AI answer you cannot check, ask for the step it was built from.*

By Harry Floyd · 2026-09-16 · canonical: https://durabilitycurve.com/blog/ask-for-the-step-before-the-answer/

*Before you trust an AI answer you cannot check, ask for the step it was built from.*

You asked it to do something finished. Summarise a forty-page report. Pull a growth figure out of a spreadsheet. Read five documents and tell you which supplier to choose.

What came back was clean, quick, and shaped like competent work. So you sent it on, quoted the figure, went with the supplier. It looked right, and looking right was the whole of what you had.

A finished answer is where good work and bad work can start to look most alike. Both arrive fluent, confident and complete. And the finished answer is usually the most expensive thing to check: to test the summary you would have to read the report, to test the figure you would have to rebuild the sum, to test the recommendation you would have to read all five documents yourself. Checking the thing you got back costs you the very work you were trying to hand off.

[Figure: Two smooth answers side by side, the sound one and the flawed one looking identical.]

*A right answer and a wrong one arrive under the same smooth surface, and the surface is the most expensive part to check.*

## Ask for the step before the answer

So do not run your check there. Ask it to stop one step earlier, at something cheaper to check, and check that first.

Before it writes the essay, ask for the outline: one line per point, in the order it will make them. Before it gives you the number, ask for the inputs, the assumptions, and the sum. Before it summarises the report, ask for the passages carrying its main claims, with page numbers. Read that. Only when the step underneath holds up do you let it finish the job.

Each is a smaller part of the task. A summary stands on specific claims and passages. A number stands on inputs, assumptions and a formula. An essay stands on a structure. The finished answer has compressed the sources, assumptions and decisions into one result. Moving one step back exposes those parts separately, where they are easier to inspect. A mistake that could have taken an afternoon to trace through the finished work may be sitting in the open a few lines earlier.

You will not always catch it, and some errors still need an expert eye. But you have made the error cheaper to catch, often much cheaper.

[Figure: A check mark moving back from the finished answer to the outline it was built from.]

*Move your check to the cheaper step: the outline, the inputs, the sources. Approve that, then let the finished answer be built from it.*

> Do not start your check where the work ends. Ask for the step underneath it, while the work is still cheap to inspect.

## The way it fools you

There is a version of this that feels the same and is not. You let it answer, then you ask how it got there.

What comes back is an explanation generated after the answer already exists. You cannot know whether it faithfully represents how the answer was produced, and it is too late either way: you are inspecting an account of the work instead of creating a checkpoint before it.

Asked first, the same request does something else. The answer does not exist yet, so what you approve becomes the thing you can require the answer to be built from. That is the whole difference. Ask afterwards and you get an explanation. Ask beforehand and you get a constraint.

[Figure: Two orders of asking: approval placed before the answer, explanation placed after it.]

*Asked first, the step becomes a checkpoint for the answer that follows. Asked afterwards, the explanation is generated with the finished answer already in place.*

## The two messages

The habit is two messages. Before it starts, send the first:

*"Before you give me the final answer, show me the part I should check first. For this task, that might be the sources, the inputs and assumptions, or the outline. Stop there and wait for me."*

Then, once you have read that and it holds up:

*"Now write the final answer using only what I approved."*

The first message moves your check to the cheap step. The second reduces the chance that the finished answer drifts away from the step you signed off.

That is the whole thing. Ask for the step before the finished answer. Check it first. Then make the final answer come from what you approved.

This is the cheap version of a larger problem: AI is most tempting to trust where checking it is hardest. I wrote about [why an AI looks best exactly where you can check it least](https://durabilitycurve.com/blog/your-ai-looks-best-where-you-check-least/) for the cases where getting this wrong is expensive.