Say what success looks like
State the outcome you want and how you will judge it, so the model aims at something you can check.
Этот урок пока недоступен на вашем языке, поэтому он показан на другом языке (English).
Why it matters
When I read a prompt, the first thing I look for is the finish line. A model will always produce something; the question is whether you can tell, afterwards, that it is the thing you needed. If the prompt only names a topic, the model has to guess the outcome, and you have to judge the result by feel.
The evidence points the same way. In the ROPE study, training people to state their requirements completely raised participants' scores from 21.9% to 40.9%, while conventional prompt-engineering training gained 0.7%, and an automatic prompt optimiser could not close the gap. A separate study of journalists found that prompt training made them feel more expert, while its effect on the quality of their work was mixed. Knowing tips is not enough; saying what you need is the skill.
Vendors say much the same. Anthropic's guidance asks for success criteria that are specific and measurable, and OpenAI's advice for reasoning models is to define clearly what a successful response looks like. A goal with a test attached is something both you and the model can check.
What good looks like
- 0 — No discernible outcome. A subject with nothing to do: “Tell me about marketing.”
- 1 — Topic or activity, outcome implicit. You know what you want; the prompt does not say it: “Write about our new product.”
- 2 — Outcome stated, no success criteria. “Write a launch email for our product.” Better, but any email would pass.
- 3 — Outcome plus at least one testable criterion. “…that gets existing customers to book a demo; under 150 words.” Now you can check the result.
- 4 — Criteria with a priority. “…a single call to action above the fold; brevity matters more than covering every feature.” The model knows what to give up when the criteria clash.
Common mistakes
- Naming an activity (“look at”, “help with”, “write about”) instead of an outcome.
- Criteria nobody could test, such as “make it engaging” or “high quality”. Ask yourself how you would recognise engaging.
- Hiding the real purpose: the email is meant to win demo bookings, but the prompt never says so.
- Listing several criteria and leaving the model to guess which matters most when they conflict.
- Confusing length with success. A word limit is a fine criterion, but rarely the only one that matters.
Try it on your own prompt
Take a prompt you used this week and paste it into the workspace. Before you look at the score, finish this sentence for yourself: “I will know the answer is good if…”. If that sentence is not in your prompt, add it, then compare the goal score before and after. The coach may ask you a question or two to help you find the criterion you left out.
Разобранные примеры
Launch email
Write an email about our new booking app.
Write an email announcing our new table-booking app to customers who have booked with our restaurant by phone in the past year. The email succeeds if: - within the first two sentences a reader can tell what the app does for them (book a table in under a minute, at any time of day); - there is exactly one call to action, a "Download the app" link, placed before the first scroll; - it is under 150 words. If these pull against each other, keep the single call to action and the word limit, and drop feature details first.
The weak prompt names a topic; the strong one names a reader, an outcome and three criteria you could tick off, and says which criterion gives way when they conflict.
Staff survey analysis
Have a look at this survey data.
<survey>
{{paste the staff survey results here}}
</survey>
These are the results of a survey of nurses on our ward about five proposed changes to the shift rota. Use them to decide which two changes we should pilot next quarter.
A good answer:
- names exactly two changes;
- supports each with the share of respondents who rated it 4 or 5, and the main objection raised in the comments;
- flags any figure based on fewer than 30 responses as unreliable.
If the data does not clearly separate the top two, say so and suggest one extra survey question that would. A clear "no clear winner" is more useful to us than a forced choice.
“Have a look” gives the model no finish line. The strong version ties the analysis to a decision, defines a complete answer and tells the model what to do when the data cannot deliver it.
Упражнение
Rewrite this prompt so that it states the outcome and at least one criterion you could check.
Rewrite this prompt so the model knows which decision the research supports and what a complete answer contains.
Rewrite this prompt so that “better” becomes a target you can test, and say which goal wins if two conflict.
Источники
- What Should We Engineer in Prompts? Training Humans in Requirement-Driven LLM Use (arXiv 2409.08775)
- What Should We Engineer in Prompts? (full text, arXiv 2409.08775v3)
- The Effect of Education in Prompt Engineering: Evidence from Journalists (arXiv 2409.12320)
- Anthropic — Define success criteria and build evaluations
- OpenAI — Reasoning best practices