Model Note / Sep 2, 2026Back to Model Notes →
A model’s response to correction can matter more than its first answer.
For real work, test whether the system can absorb specific feedback inside the task and produce a cleaner second pass without reintroducing old mistakes. A strong first answer is pleasant, but most business work includes revision. The more important question is whether the model can preserve what was right, fix what was wrong, and respect a correction consistently across the rest of the task. That behavior often predicts day-to-day usefulness better than a flashy first response.
Practical suggestions
- Keep one test prompt where you intentionally give the model a correction after its first response.
- Score whether the second pass fixes the requested issue without breaking previously correct details.
- If the same mistake returns repeatedly, treat that as a workflow limitation and add a stronger verification step.
