AFG AI Field Guide Fix a bad AI answer

AI Field Guide - First recording path

The first AI answer is a draft. Fix it before you judge it.

A rough answer does not mean AI failed. It usually means the draft needs direction: shorter, clearer, more like you, turned into a checklist, or checked for assumptions.

Copy the fix prompts Start the free beginner guide Join Classroom

Starter video path

Step 1

First, name what is wrong.

Do not just say, "This is bad." Pick the problem. AI answers are easier to fix when you tell the tool exactly what missed.

Common problems

  • Too long.
  • Too stiff or corporate.
  • Too vague.
  • Missed the real job.
  • Invented facts, prices, dates, or promises.

Better first move

Point at the problem, keep what worked, and ask for one specific change. That is faster than starting over.

Step 2

Use one fix prompt at a time.

The first answer is not the final answer. Use these short follow-ups to steer the draft without making the chat messy. 

Take your last answer and fix it.

What is wrong:
[too long / too stiff / too vague / missed the real job / invented details]

Keep:
[what worked]

Change:
[what should be different]

Return:
1. a better version
2. what changed and why
3. what I should verify before using it

Step 2B

Use this simple bad-to-better pattern.

When a beginner says, "AI gave me junk," the next move is not to quit. Keep the useful piece, name the bad piece, and ask for a smaller corrected draft.

Bad first answer

We value your business and will provide a comprehensive solution tailored to your needs at our earliest convenience.

Better after one fix

Thanks for sending this over. I can help. Send me the size, timing, and one photo if you have it, and I will give you the next clear step. 

This answer sounds too vague and corporate.

Keep the useful intent, but rewrite it so a normal person would actually say it.
Make it shorter.
Give one clear next step.
Do not invent prices, dates, proof, or promises.

Step 3

Make it sound like you.

A beginner mistake is accepting wording that sounds like a brochure. Ask for plain, honest, useful language and remove the hype before you send anything.

Stiff answer

We are delighted to inform you that your inquiry is important to us and we value your continued patronage.

Plain answer

Thanks for reaching out. I can help. Send me the size, timing, and one photo if you have it, and I will give you the next step.

Rewrite this in my voice:
- plain
- honest
- not hypey
- easy for a normal person to read

Keep the meaning. Remove anything that sounds fake, stiff, or too salesy.

Step 4

Turn a messy answer into a checklist.

If the answer is too much, make it useful by changing the shape. A checklist is easier to use than a wall of advice.

Cut

Remove repeated or fluffy lines.

Order

Put steps in the sequence someone should follow.

Check

Mark anything that needs human review.

Save

Keep the version that is useful enough to reuse.

Turn this answer into a checklist I can use.

Rules:
- keep it short
- put the steps in order
- mark anything I should verify
- remove advice that does not apply to my situation

Step 5

Verify before using it.

AI can sound confident and still be wrong. Before sending, posting, quoting, or building from the answer, ask what needs a human check.

Ask it to mark

  • Facts.
  • Names.
  • Dates.
  • Prices.
  • Promises.
  • Assumptions.

Do not use yet if...

  • It invented proof.
  • It guessed at details you did not give.
  • It sounds ready to send without review.
  • It touches money, legal, health, or private information.
Before I use this answer, list what I should verify.

Mark:
- facts
- names
- dates
- prices
- promises
- assumptions
- anything that could be wrong or risky

Step 6

Save the useful version.

The win is not getting a perfect answer once. The win is saving the prompt, the fix, and the final useful result so you can use it again.

Task

What job did this answer help with?

Bad sign

What was wrong with the first answer?

Fix prompt

What follow-up made it better?

Final check

What did you verify before using it?