How to Ask Questions to ChatGPT
Questions about how to phrase a prompt: how much context to include, how to ask for a format, how to get specifics rather than generalities, how to push back on a weak answer, and which questions to verify elsewhere before acting on them.
The questions
Open any question for the note
What makes a prompt specific enough?
Why ask it
Name the audience, the length, the constraint and the thing you already tried. "Help me write an email to my landlord" and "Write six lines to my landlord asking for a repair date, we have asked twice, I want it firm but not threatening" produce answers that are not comparable. Vagueness in, average of everything out.
How much background should I paste in?
Why ask it
Include anything that would change the answer and nothing that would not. The common failure is the opposite of what people fear: too little context, so the reply is written for a generic situation. If you find yourself editing out wrong assumptions, those assumptions are the context you left out.
Does telling it to act as an expert help?
Why ask it
Mildly, and mostly because it forces you to specify the audience and register you actually want. "Act as a lawyer" does not make the answer reliable; "explain this clause as if to a tenant with no legal training" changes the wording usefully. Treat role framing as a way of describing the output, not as a qualification.
How do I ask for a particular format?
Why ask it
State it as part of the question: a table with these columns, five bullets of ten words, JSON with these keys, no preamble. Asking afterwards costs a round trip and often loses detail from the first answer, since the rewrite optimises for shape.
Is it worth asking it to work through the problem step by step?
Why ask it
For anything with several dependent steps, yes, because it makes the reasoning visible enough to check. The gain is yours rather than the model's: you can see which step is wrong, which is impossible when the answer arrives as a single confident conclusion.
What do I do when the answer is generic?
Why ask it
Do not repeat the question. Say what was wrong with the answer and add the missing constraint: too long, wrong audience, ignore the first two suggestions, assume I already know the basics. A second identical question produces a second average answer.
How do I get it to disagree with me?
Why ask it
Ask for the strongest case against your plan, or for three reasons it fails, rather than asking whether it is a good idea. Questions phrased as a check for approval tend to get approval, and the polite agreement is worth nothing to you.
How do I ask for options rather than one answer?
Why ask it
Ask for a specific number of genuinely different approaches, plus the trade-off for each. Without the number you get one recommendation with hedging attached; without the trade-offs you get three variations on the same idea in different words.
How do I ask it to explain something at my level?
Why ask it
Say what you already know rather than asking for it to be simple. "I understand basic statistics but not regression" is actionable; "explain it simply" produces an analogy about pizza that leaves you no further forward.
How do I get examples that match my situation?
Why ask it
Give one example of your own first, even a rough one, and ask for more in that shape. Requests for examples without a sample come back generic, and you cannot tell whether the generic version failed because of the question or the subject.
How do I ask a follow-up without losing the thread?
Why ask it
Refer to the specific part you want changed, by quoting or numbering it. A follow-up saying "make it better" applies to everything and usually rewrites the parts you liked, which is how people end up with a worse fourth draft than second.
When should I start a new chat instead of continuing?
Why ask it
When the subject has changed, or when several corrections have accumulated and the answers keep drifting back to an early wrong assumption. Long threads carry their own history, and it is often faster to restate the problem cleanly than to argue it out of a bad start.
How do I ask about something where being wrong would matter?
Why ask it
Ask for the answer and separately for what you should check, then check it. Fluent, confident, wrong is the failure mode to plan for, including invented citations and references that look right and do not exist, so treat anything checkable as a lead rather than a fact.
How do I ask it to check its own work?
Why ask it
Ask it to find the errors in a specific answer, or to redo a calculation independently and compare, rather than asking whether it is sure. A direct challenge to confidence usually produces an apology and a changed answer regardless of whether the original was right.
How do I ask for writing help without ending up with something bland?
Why ask it
Give it your own draft, however bad, and ask for edits rather than a replacement. Prompts that ask for writing from nothing return the average of everything written on that subject, which reads smooth and says nothing.
How do I ask for a change to one part only?
Why ask it
Say which part, and say to leave the rest untouched. Without that instruction a rewrite usually arrives, and comparing two long versions to find what moved costs more time than writing the change yourself.
How do I ask a coding or debugging question?
Why ask it
Include the actual error text, the versions involved, the code that produces it and what you expected instead. Describing a bug in prose gets a plausible answer about a different bug, which is the most expensive kind of wrong answer to receive.
How do I ask about a document or a set of data I provide?
Why ask it
Say explicitly to use only what you have supplied and to say so if the answer is not in there. Otherwise gaps get filled from general knowledge, and the answer that blends your document with plausible outside detail is very hard to audit.
How do I ask about anything recent or time-sensitive?
Why ask it
Ask it to say what it does not know rather than assuming currency, and check prices, dates, laws, schedules and news against a primary source. Time-sensitive answers can be stale without being flagged as such, which is the point where confident wording does the most damage.
What should I not ask it?
Why ask it
Anything requiring facts about your specific medical, legal or financial position, where a professional is looking at your actual case, and anything involving other people's private information or credentials you would not paste into a public form. It is useful for preparing the questions you take to that professional, which is a different job from answering them.
Writing better prompts
Practical guidance for the conversation itself
Four habits that change the output
Say who the answer is for
Audience and register do more work than any other single addition. A colleague, a client, a child and a regulator need different answers to the same question.
State the constraint
Length, tone, format, what to leave out, what you have already tried. Constraints are what stop the answer from being the average of everything.
Bring your own draft
Editing beats generating. A weak first attempt from you narrows the response far more effectively than a longer request.
Ask for the counter-argument
Requesting the strongest objection to your plan is the cheapest way to get something other than agreement.
Prompt shapes worth reusing
- Explain: "I already understand [X]. Explain [Y] in terms of that, in under 200 words."
- Options: "Give me three genuinely different approaches, with the main trade-off of each, then say which you would pick and why."
- Critique: "Here is my plan. List the three strongest reasons it fails."
- Edit: "Here is my draft. Tighten paragraph two only, keep my wording elsewhere."
- Grounded: "Answer using only the text below. If it is not in there, say so."
- Verify: "Answer, then list what I should check independently and where."
Habits that waste your time
Asking the same question again
Repetition without new information produces a different average, not a better answer. Add a constraint or say what was wrong.
Trusting fluency
Well-formed prose is not evidence of accuracy, and invented references read exactly like real ones. Check anything you would be embarrassed to be wrong about.
Asking whether it is sure
This tends to produce a reversal rather than a check. Ask for the working, or ask it to redo the step independently.
Letting a long thread drift
After several corrections, the conversation carries more wrong assumptions than useful context. Start again with a clean statement of the problem.
Pasting things you should not
Other people's personal data, credentials and confidential documents. Assume anything you type may be stored or reviewed, and check your own organisation's rules.