How to Improve AI Responses

To improve a weak AI response, name what is wrong with it specifically, trace that fault to what was missing or unclear in your prompt, and fix that one thing. Asking the model to "make it better" rarely works because it has no more information than it had the first time. Small faults are best corrected with a precise follow-up; faults in the foundations are best corrected by rewriting the prompt and starting again.

Read the answer before reacting to it

The instinct on seeing a disappointing reply is to regenerate or to type "try again". Both repeat the same request with the same gaps. Spend a minute on the output instead and finish this sentence: "This is weak because ___." If the blank is "it's just not good", read it again. The blank needs to be something a person could act on: too long, wrong audience, misses the second requirement, states things I never told it.

Match the symptom to the cause

Most weak answers fall into a small number of patterns, and each points back to a specific gap.

Generic, could-apply-to-anyone content

Likely cause: the model had no specifics to work with, so it produced the average answer.

Fix: supply the particulars: your audience, your product, your constraints, an example of what you consider good. Asking for "more specific" without adding information only produces invented specifics.

Invented facts, names or figures

Likely cause: the task needed information the prompt did not contain, and nothing told the model what to do about the gap.

Fix: paste in the source material and restrict the model to it, with an explicit fallback.

Use only the report below. If the report does not state a figure,
write "not stated in the report" in its place. Do not estimate.

Vendor documentation consistently recommends grounding answers in supplied reference text for this reason. Verification is still your responsibility.

Right content, wrong shape

Likely cause: format, length or structure was left to chance.

Fix: specify it with numbers and names. "Under 120 words, three bullets, each starting with a verb." If the layout is unusual, show a blank skeleton of it.

Wrong tone or level

Likely cause: the reader was never identified.

Fix: describe the reader and the setting. "For a finance director who has not seen the project; neutral, no jargon" does more than "professional tone". A short sample of writing in the register you want is stronger still.

Part of the request ignored

Likely cause: several asks packed into one paragraph, or two instructions that conflict.

Fix: number the requirements, one per line. If two pull against each other, such as "comprehensive" and "brief", say which wins.

Shallow reasoning or a wrong conclusion

Likely cause: the model went straight to an answer on a problem that needed working through.

Fix: ask for the analysis before the verdict, or split the job in two. OpenAI's guide calls this giving the model time to think; Anthropic's documentation suggests also asking the model to check its work before finishing.

Too cautious or too padded

Likely cause: no signal about how direct to be, so the reply hedges and restates the question.

Fix: say what to drop. "No introduction, no summary of my question, no closing offer. Start with the recommendation."

Follow up or start over?

A follow-up message is the right tool when the answer is mostly there:

• The structure is right and one section is thin.
• The length or tone needs adjusting.
• You want an alternative version of one part.

Start a fresh conversation with a rewritten prompt when:

• The model misunderstood the task itself.
• Key context was missing from the start.
• You have already sent several corrections and the replies are getting more tangled.

The reason for the second rule is practical. Everything in the conversation, including the weak drafts and your earlier corrections, remains part of what the model is working from. A clean prompt containing what you have learned usually beats a sixth patch. It also leaves you with a prompt you can reuse.

Writing a follow-up that works

A useful correction has three parts: what to keep, what to change, and how.

Keep the structure and the first two sections as they are.

Section 3 is too abstract. Replace it with one concrete example
from a small online shop, including what they changed and what
they measured afterward. Use only details I gave you earlier;
if you need a detail I haven't provided, ask me for it.

Then cut the whole piece to under 400 words by removing the
closing summary.

Compare that with "section 3 needs work", which forces the model to guess what kind of work.

Two further habits help:

• Quote the problem. Paste the sentence or paragraph you object to. It removes ambiguity about which part you mean.
• Explain the why. "Shorter, because this is read on a phone between meetings" lets the model make related decisions you did not list, such as front-loading the conclusion.

Use the model as a reviewer

Before rewriting, you can ask the model to diagnose its own output against your intent:

Here is what I was trying to get: a one-page brief a contractor
could act on without a call. Compare your answer against that.
List what is missing or unclear, then ask me up to three
questions whose answers would let you fix it.

The questions it asks are often a direct list of what your original prompt left out. Answer them, then fold those answers into the prompt itself for next time. The prompt optimizer applies a similar review to the prompt instead of the output.

A short example of the loop

First attempt:

Write an email to customers about our price increase.

The reply is polite, vague and three paragraphs too long. Diagnosis: no facts, no audience, no length, no stance. Revised prompt:

Draft an email to existing subscribers of a meal-planning app.

Facts: the monthly plan rises from $8 to $10 on March 1. Annual
plans are unchanged until renewal. Reason: recipe licensing costs.

Reader: long-standing customers; some will be annoyed. Be direct
and respectful; do not apologize repeatedly or oversell.

Under 130 words. Subject line plus body. State the change in the
first two sentences. End with how to switch to annual billing.

Nothing clever was added. Each line answers one of the diagnosed gaps.

When the prompt is not the problem

Sometimes iteration stalls for reasons wording cannot fix: the task needs current or private information the model does not have, the output needs expert verification you cannot shortcut, or the job is too large for a single reply. In the last case, splitting the work is covered in prompt chaining. If a prompt works sometimes and fails at other times, that is a consistency question; how to test AI prompts explains how to check it. For editing drafts specifically, the editing prompt builds the keep-change-how pattern into its instructions.