Blog · Building · · 8 min read

Teaching an assistant step by step

AI assistants learn faster and fail more visibly when each step of a task is checked as it happens, rather than the whole task getting one pass-or-fail grade at the end. Step-level checks also give people a clearer view of where things went wrong.

A sunlit wooden baker's workbench with a ceramic bowl of rising bread dough under a linen cloth, a wooden spoon, a small jar of yeast, and stalks of wheat.

When an assistant attempts a twenty-step task, training often waits until the end and marks the whole attempt as a failure if the result is wrong. The assistant learns that it failed, but not whether the mistake was at step two or step nineteen, so it has to guess what to change. Researchers call this the credit assignment problem.

The guessing trap of end-to-end scores

To see why this guessing is so wasteful, picture a maze with ten successive doorways. If an assistant takes nine correct turns and stumbles at the tenth, an end-of-run score simply says no.

Unable to see which turn was wrong, the assistant begins changing everything at random. It alters the first turn, scrambles the third turn, and replaces good choices with bad ones. It may try hundreds of variations before stumbling across the exit again.

This trial-and-error cycle consumes huge amounts of electrical power and computing time. Worse still, it makes assistants brittle. A system trained by pure trial and error often memorizes specific sequences rather than understanding why each step works.

Checking the steps as they happen

Comparison of end-of-run scoring versus step-by-step diagnostic feedback A diagram comparing two learning approaches. On the left, an assistant receives a single fail grade after ten steps, leaving it to guess which step failed. On the right, each step is verified in sequence, catching an error at step four immediately with a clear explanation. END-OF-RUN SCORING Blind Guessing Steps 1 to 3: Planning Good steps, but unconfirmed Step 4: Silent Error Flawed assumption passes unnoted Steps 5 to 10: Downstream Actions waste energy on bad premise Evaluation: Single 0/10 Score "The task failed. Try again." Assistant cannot tell which step failed. It reshuffles all 10 steps blindly. STEP-WISE FEEDBACK Targeted Repair Steps 1 to 3: Verified OK Premises checked and preserved Step 4: Pinpointed Here Linter catches exact failing line Targeted Revision Rewrites step 4 without touching 1 to 3 Outcome: Zero Regressions "Step 4 corrected. All checks pass." Learns in up to 35 times fewer trials. Audit trail remains clear to the user.
End-of-run scoring leaves an assistant guessing which of ten steps went wrong. Step-wise feedback isolates the exact error, fixing the problem without disturbing good work.

Recent research offers a much cleaner path forward. Instead of scoring the entire run as one lump, training tools evaluate individual reasoning steps as atomic units.1

When an assistant takes a step, the harness checks that specific action against known rules. Did it read a valid file? Did it follow the safety policy? Did its intermediate calculation hold up?

If step four contains a flaw, the system pauses right there. It tells the assistant exactly what went wrong in plain language. The assistant corrects step four and continues its errand, keeping steps one through three intact.

The difference in performance is striking. Computer scientists have found that step-level feedback allows models to solve complex multi-step problems with far greater accuracy.1 Even more surprisingly, using natural language reflection to diagnose why a step failed can outperform traditional trial-and-error training while using up to thirty-five times fewer trial runs.2

Words work better than numbers

Why does plain language teach an assistant so much faster than a numerical score?

Consider what happens when you give an assistant a number like minus five. A number has no structure. It tells the software that something went wrong, but it contains zero information about why.

Now consider what happens when a diagnostic checker provides a sentence: "You tried to send the email before verifying the recipient address." That sentence contains rich semantic cues. It tells the model which tool call failed, which policy rule was violated, and what prerequisite action was skipped.

Because modern language models are designed to understand words, they can digest that written critique immediately. They do not need thousands of random attempts to figure out what the penalty meant. They read the explanation and adjust their plan on the very next try.

What this means

Giving an AI assistant a single grade at the end wastes time and power. Pointing to the exact step where it stumbled makes learning fast and transparent.

What this means for everyday people

You might wonder why training techniques inside research labs matter to someone using an assistant at home or work. The answer comes down to safety and inspectability.

When an assistant is trained only on end-of-run scores, its internal reasoning remains an opaque black box. If it makes a costly blunder, nobody can trace which assumption led it astray. The software vendor will tell you to try again with a different prompt.

When an assistant operates step by step, its entire journey becomes visible. Before taking an irreversible action, like spending money or deleting a record, it records the exact reasoning step that led there. You do not have to trust a mysterious feeling or a secret algorithm. You can read the steps yourself.

Clear steps keep humans in charge

As automated assistants take on larger roles in healthcare, local government, and small businesses, we cannot afford systems that learn by blind guessing. We need assistants that think in legible steps and learn from specific corrections.

Teaching assistants step by step does not just save electricity. It builds tools whose thinking we can follow, audit, and gently guide when things go off track.

1. Xin Lai, Zhuotao Tian, Yukang Chen, Senqiao Yang, Xiangru Peng, and Jiaya Jia, Step-DPO: Step-wise Preference Optimization for Long-chain Reasoning of LLMs, arXiv:2406.18629 (June 2024 / ICLR 2025).

2. Ayush Agrawal, et al., GEPA: Reflective Prompt Evolution Can Outperform Reinforcement Learning, arXiv:2507.19457 (July 2025 / ICLR 2026 Oral).

← All articles

Recent articles

Protecting ·

When an invoice gives orders to your assistant

Giving an AI assistant eyes and ears opens a hidden door. Discover why assistants mistake billing data for instructions, and how out-of-band sign-offs keep you safe.

Read · 8 min

Governing ·

Why a public decision cannot hide in a black box

When software decides who qualifies for housing, benefits, or public care, agencies cannot accept a vendor's trade secret. Here is why public choices need an open blueprint.

Read · 7 min

Seeing ·

Why an assistant needs an open logbook

Autonomous digital assistants sound confident when they finish a task, but silent mistakes slip past cheerful summaries. Here is why every automated helper needs an auditable logbook.

Read · 7 min