AI for Mere Mortals Part 3: How to Write Better Prompts

Why your AI answers feel generic and how to fix them. Four ingredients of a good prompt, iteration patterns that work, and the common mistakes to avoid.

Writing prompts at a laptop
Updated How we review →
Rob
By Rob11 June 2026 · 11 min read

If you've used ChatGPT for a week and the answers still feel generic, the issue is almost never the model. It's the prompt. The way you phrase a request to AI directly shapes the quality of what comes back, and the gap between an OK answer and a useful one is usually a sentence or two of extra context.

This is the third in our AI for Mere Mortals series. Part 1 explained what AI actually is; Part 2 walked through setting up ChatGPT and writing your first prompts. This piece is the bridge between using AI and getting useful work out of it. By the end, you'll have a repeatable structure for prompts, a feel for when to keep refining versus start fresh, and a short list of the mistakes that produce the genericness you've been bumping into.

Why do AI answers feel generic?

Large language models (LLMs, the technology behind ChatGPT and similar tools) are trained on huge amounts of text. When you ask a vague question, the model averages across that training data and gives you the most statistically likely answer. The most likely answer to "how do I write a CV" is the boring, generic CV advice you've seen on a thousand career sites. There's nothing wrong with the model. The model just doesn't know anything about you.

The fix is to push the model away from the average. You do that by giving it information it can't have guessed: your specific situation, the audience you're writing for, the constraints you're working within. The more specific the prompt, the more specific the answer.

What are the four ingredients of a good prompt?

Every prompt that produces useful output has four things, even if it doesn't look structured. Think of these as ingredients rather than a template: include all four when the result matters, drop the ones that don't apply when you're asking something simple.

01

1. Context

Who you are, what situation you're in, what you've already tried. This is the single most important ingredient. A two-line description of your context turns a generic answer into a targeted one.

02

2. The task

What you actually want the AI to do. "Write", "summarise", "explain", "compare", "give me a list of". Be specific. "Help me with my CV" is not a task. "Rewrite this CV summary to emphasise project management experience" is a task.

03

3. Constraints

Length, tone, audience, what to avoid. Constraints are what stop the model defaulting to the average. "Under 200 words", "plain English, no jargon", "aimed at a non-technical reader", "avoid bullet lists" all radically change the output.

04

4. Output format

How you want the answer structured. A table, three options, a bulleted list, a single paragraph, a script you can paste into something else. If you don't say, the model picks for you and usually picks wrong.

How do you iterate on a bad answer?

The first answer is rarely the final one. Treat the first response as a draft, then push back. The model is very good at refining when you tell it what's wrong. Specific patterns that work:

"This is too generic - add specific examples for a UK reader."

"Cut the bullet lists. Rewrite as flowing paragraphs."

"Take a second pass and remove anything that sounds like marketing copy."

"That third point doesn't apply to my situation - drop it and replace with something about [specific thing]."

"Rewrite this as if you were explaining it to my mum, who's never used the software."

The model has the full context of your conversation, so each follow-up builds on what's already there. This is the single biggest behavioural difference between people who get useful answers from AI and people who don't: heavy users iterate. They don't accept the first answer and complain about it; they ask for a second pass with specific feedback.

When should you start a new chat instead?

Long conversations accumulate context, which sounds useful but sometimes hurts. After 20 or 30 back-and-forth turns the model starts to lose the thread, repeats itself, or confuses one part of the conversation with another. This is sometimes called "context rot" in the AI community and it's a real effect, not a bug you can fix.

Rules of thumb on when to start fresh: when the task changes completely (you were drafting a CV, now you want help planning a holiday), when the AI seems to be looping on the same wrong answer despite corrections, or when you've made significant changes to your underlying material and want a clean read. Copy the relevant context into the new chat - that's the moment to lean on ingredient one (context) again.

How do you give AI your actual material?

The single biggest unlock for most casual users is realising you can paste large amounts of your own material straight into the chat. Email drafts, meeting notes, your draft blog post, a recipe you're tweaking, a contract you don't understand: it all goes in. The model treats it as part of your prompt.

Patterns that work well:

  • Paste then ask. Drop in the email, then say "Rewrite this to sound less defensive and shorter". The model has the full text - it's not guessing what you mean.
  • Paste, ask, refine. Drop in your draft, ask for a critique, then ask it to apply the critique. Often the critique pass reveals things you'd never have spotted.
  • Paste two things, compare. Drop in two versions and ask which is stronger and why. The reasoning is often more useful than the verdict.

There are obvious privacy implications to be aware of (covered in Part 2) - don't paste sensitive client data or anything legally privileged into the free tier, where conversations may be used to improve models unless you turn that off in settings.

What are the common prompt mistakes that produce generic answers?

Asking yes/no questions when you want a recommendation. "Is X better than Y?" tends to produce hedged, both-sides answers. "I'm choosing between X and Y for [my specific situation] - which fits better and why?" forces a real answer.

Skipping the audience. Same explanation works very differently for a 12-year-old, a developer, and your accountant. Tell the model who's reading.

Asking for too much in one turn. A prompt that asks for a draft, a critique, three alternatives, and a summary will produce a thin version of all four. Split it into separate turns.

Using "best" without criteria. "What's the best budgeting app?" is unanswerable. "What's the best budgeting app for a UK freelancer who wants to track VAT and integrates with a free tier of accounting software?" is answerable.

Treating the AI as a search engine. Search engines reward keyword density; AI rewards full sentences with context. Write the way you'd talk.

Not asking it to show its working. When the answer matters (financial decisions, contract terms, code logic), add "explain your reasoning step by step" to the prompt. You'll catch mistakes you'd otherwise miss.

Three exercises to try this week

  1. Rewrite a real email

    Pick an email you sent last week that wasn't quite right. Paste it into ChatGPT and prompt: "Rewrite this to sound [warmer / firmer / shorter / clearer]. Keep my voice - I'm a [your role]. Don't add anything I didn't already say." Compare the rewrite to your original.

  2. Plan a complicated week

    Give it your actual diary for the week, the deadlines you have, and one personal commitment. Ask it to suggest a realistic order of work that respects energy levels (morning vs afternoon, deep work vs admin). The constraint forces it past generic advice.

  3. Get a second opinion on a decision

    Paste the actual context for a decision you're working through (the offer, the trade-offs, your constraints). Ask the AI to argue for the option you're NOT leaning towards, as the strongest case. The exercise often surfaces something you'd missed.

Frequently asked questions

Q01Do I need to learn "prompt engineering"?
No. Prompt engineering as a discipline is mostly about building reliable prompts for production systems where the same prompt runs thousands of times. For everyday use, the four ingredients above (context, task, constraints, format) cover ~95% of what matters. The rest is iteration.
Q02Should I use ChatGPT, Claude, or Gemini for prompting?
All three respond well to good prompts. They each have small differences in style (Claude tends to be more cautious, Gemini integrates with Google data, ChatGPT has the broadest plugin ecosystem) but the same prompt structure works across all three. If you've already got a free ChatGPT account, stick with that until you have a specific reason to switch.
Q03How long should a prompt be?
Long enough to include the four ingredients, no longer. A two-sentence prompt with a clear task, a clear audience, and a clear constraint will outperform a five-paragraph prompt that buries the actual request.
Q04Is it cheating to use AI like this?
Depends on the context. For drafting personal emails, planning your week, summarising a document you've read, or thinking through a decision - no, it's a tool, the same way a calculator is. For coursework or work output where authorship matters, check the rules. Many universities and employers are still working out where the line sits; assume disclosure is safer than not.
Q05What's the most common prompt mistake you see?
Skipping context. People type the task and leave out who they are. "Help me write a complaint letter" gives you a generic complaint letter; "I'm a small landlord in Sheffield with a tenant who's three months in arrears and won't respond to texts - help me draft a final-warning letter that's firm but not aggressive" gives you something usable.