1. Say who the output is for
"Explain this" and "explain this to someone who's never worked in this field" produce very different answers. Naming the audience is the single fastest quality upgrade available.
2. State the format before you need it
Asking for "a table with columns for cost, pros, and cons" upfront saves you a follow-up message almost every time.
3. Give it your constraints, not just your goal
Word limits, tone, things to avoid, what you've already tried. Constraints don't restrict the output — they focus it.
4. Paste the actual thing
Describing your email is much worse than pasting your email. Models work with what's in front of them; secondhand descriptions lose the details that matter.
5. Ask for options, not an answer
"Give me three different approaches, each with a different tradeoff" is often more useful than one confident recommendation — especially early in thinking about a problem.
6. Push back when something's off
"That's too formal" or "you've misunderstood — the audience is internal, not customers" is a normal, expected part of the process. The first response is a draft.
7. Ask it to critique its own output
"What's the weakest part of this?" or "what would a skeptical reader object to?" often surfaces genuine problems, and costs one extra message.
8. Start a new chat when you change topic
Long conversations carry all their earlier context, which can drag responses toward the old topic. A fresh chat for a genuinely new task is usually cleaner.
9. Verify anything that matters
Facts, statistics, citations, legal or medical claims. Fluent phrasing is not evidence of accuracy — see AI Hallucinations Explained.
10. Reuse what works
When a prompt produces great output, save it. Most people's best AI work comes from a handful of prompts they've refined over time, not from writing fresh ones every session.
The pattern behind all ten
Almost every tip here is a variation on one idea: give the model information it can't guess, and don't accept the first draft as final. Everything else is detail.
Our Prompt Library has ready-made templates built on exactly these principles, each with placeholders you fill in.
Habits that matter more than tricks
Most published tip lists are variations on wording. These are about how you work, and they make more difference.
Keep one conversation per project. Context carries forward within a conversation, so the tenth message benefits from the first nine. Starting fresh each time means re-explaining your situation every time.
Paste the real thing. People describe their document instead of pasting it, then wonder why the advice is generic. The model cannot see what you did not show it.
Say what you do not want. Constraints are underused and unusually effective. "No bullet points", "do not use the word leverage", "under 100 words" all work reliably, and they close off the failure modes you already know about.
Ask for the reasoning when it matters. "Explain why you chose that structure" tells you whether there was a reason or whether it defaulted. If the reasoning is thin, so is the answer.
Stop when it is going wrong. If two attempts have missed, a third rarely lands. Change the framing rather than repeating yourself louder.
Things that sound clever and are not
Threatening or bribing it. Offering a tip, claiming your job depends on it, or expressing urgency does not improve output. These circulate widely and do not hold up.
Elaborate role-play stacking. "You are a world-renowned expert with 30 years of experience and three PhDs" adds nothing over "explain this for someone technical." One clear role instruction is enough; the rest is decoration.
Asking it to be confident. Instructing a model not to hedge does not make it more accurate. It removes the hedging while leaving the uncertainty in place, which is worse for you.
Trusting self-assessment. "Are you sure?" often produces a changed answer regardless of whether the first one was right. It measures agreeableness, not accuracy.
The one habit worth building
If you take a single thing from this: treat the first response as a draft and say specifically what is wrong with it. Not "make it better" — "the second paragraph assumes the reader knows what an API is, and they do not."
Almost every genuinely good result comes from two or three rounds of that. People who find these tools disappointing are usually judging them on the first answer, which is like judging a colleague on their first guess before you told them anything about the problem.
Prompt Engineering for Real Work covers the structure behind all of this, and the Prompt Library has templates built on it.