How do I write a prompt that gets a useful answer?
Context, specificity and format — the three things that separate a vague answer from a useful one.
- Difficulty
- beginner
- Time
- 15 min
- Read
- 2 min
Short answer
Say who it is for, what you actually want, and what form you want it in. Most disappointing answers come from questions that were too short, not from the tool being weak.
These tools respond to what they are given. A one-line question gets a generic answer because a generic answer is the only reasonable response to a generic question. The fix is boring and effective: provide more context.
Step by step
- Give the context.Who it is for, what you are trying to achieve, what constraints apply. "Explain this to a colleague who has never used a spreadsheet" produces something quite different from "explain this".
- Be specific about the output you want.Length, format, tone, structure. "Five bullet points, plain English, under 100 words" gets you something usable rather than an essay.
- Provide the source material.Pasting the text and asking it to work from that is far more reliable than asking it to recall something. It also cuts the invention rate sharply.
- Say what you do not want."Without jargon", "do not include an introduction", "no bullet points". Negative constraints work well and are underused.
- Give an example if you have one.One example of the style or format you want is worth several paragraphs of description.
- Iterate rather than restarting.Ask for adjustments — shorter, more formal, focus on this part. The conversation carries context, so refining is usually faster than rewriting the question.
- Ask it to ask you questions."What do you need to know to do this well?" surfaces the context you forgot to give, and it is a genuinely effective technique.
- Break big requests into steps.One large multi-part request produces shallow coverage of everything. Sequential focused requests produce better results at each stage.
Tips
- Length is not the goal — relevance is. A specific three-line prompt beats a rambling paragraph.
- If the answer is generic, the question was. That is almost always where to look first.
- Save prompts that work. Most people ask the same few kinds of question repeatedly.
Questions people ask
Why do I get such generic answers?
Usually because the question was generic. Add who it is for, what you are trying to achieve, and what format you want.
Is there a right way to write prompts?
No formula, but context, specificity and a stated output format reliably help. Asking the tool what else it needs to know is a good shortcut.