Test and Improve Your Prompts

Not Every Prompt Works Every Time

You write a prompt. It works great. You use it again next week. Different topic. It does not work as well.

That is normal. Prompts are not magic. They need testing and tweaking.

How to Test a Prompt

The Three-Run Test

Run your prompt three times with different inputs. Check if the output is consistent and good.

Step 1: Run It Once

Use your prompt with real input. Look at the output.

Example: Prompt: "Write a professional email to [person]. I want to [goal]. Key points: [list]. Keep it under 150 words."

You fill in:

• [person]: "My boss Sarah"
• [goal]: "ask for a budget increase"
• [list]: "Sales up 30%, team growing, tools are outdated"

Output: An email about 180 words.

Qestion: Is it good? Is it the right tone? Did it cover your points?

Step 2: Run It Again with Different Input

Use the same prompt with a different topic.

You fill in:

• [person]: "A customer"
• [goal]: "ask them to try our new feature"
• [list]: "Saves 5 hours per week, integrates with Slack, free for 30 days"

Output: Another email.

Question: Did the prompt work the same way? Is the quality consistent?

Step 3: Run It a Third Time

One more time with different input. Pay attention to patterns.

After three runs, you will know:

• Does this prompt usually work?
• What output is it good at?
• What does it struggle with?

How to Improve a Prompt

If testing shows problems, improve it. There are four main ways.

Improvement 1: Add More Context

If the output is vague or off-topic, the prompt might be missing context.

Weaker prompt: "Write an email."

Better prompt: "Write a professional email to a customer. They are upset because our tool deleted their file. I want to apologize and offer a solution. Make it warm and sincere. Under 150 words."

Why better: More context = more specific output.

Improvement 2: Tighten Constraints

If the output is too long, too casual, or goes off-track, add tighter rules.

Weaker prompt: "Write a report."

Better prompt: "Write a weekly status report. Include: three accomplishments (bullet points), next week's plans (three items), and one blocker. Keep it under 300 words. Use simple language. No jargon."

Why better: Specific format and word limit = more control.

Improvement 3: Add an Example

If AI is not matching the style or format you want, show an example.

Weaker prompt: "Write a subject line for an email."

Better prompt: "Write a subject line for an email. It should be short and clear and include a specific benefit. Example: 'Save 3 hours a week with our new tool'. Now write a subject line for this topic: [your topic]."

Why better: Examples teach AI the style you want.

Improvement 4: Change the Order or Phrasing

Sometimes the prompt is fine but the wording confuses AI.

Weaker version: "Write a report that is not too long but covers everything."

Better version: "Write a report under 500 words. Include: [three sections]. For each section, list the key points, no extra explanation."

Why better: Clearer structure, less room for confusion.

The Version Approach

When you improve a prompt, keep both versions.

Why?

V1 might work better in some cases. V2 in others. Or V2 might not actually be better.

If you delete V1 and V2 does not work, you have to rewrite from scratch.

How to Version

In your library, name them:

• "Write complaint email v1"
• "Write complaint email v2"

Add notes on what is different.

Example: "v1: Generic approach, works for most complaints v2: More empathetic tone, better for angry customers"

After a few weeks, you will know which version works best. Then you can delete the old one.

When Is a Prompt Good Enough?

You do not need perfection.

Good Enough Means

• Three runs in a row produce useful output
• The output needs only light editing (not major rewrites)
• The output matches your style and format
• It saves you time compared to writing it yourself

Not Good Enough Means

• You have to rewrite most of the output
• The format is wrong every time
• It is slower than doing it yourself
• It keeps missing key requirements

If not good enough, improve it using the methods above. Test again. Repeat until it is good enough.

Real Example: Test and Improve

Version 1

Prompt: "Write a brief for a project."

Test 1 output: 400 words, rambling, no clear recommendation.

Test 2 output: Too short, missing key info.

Test 3 output: Good but inconsistent.

Result: NOT good enough. Too vague.

Improvements Made

• Added specific sections (problem, solution, timeline, budget, risks)
• Added word limit (300 words max)
• Added example output format

Version 2

Prompt: "Write a project brief. Include these sections: Problem (50 words), Solution (100 words), Timeline (20 words), Budget (20 words), Risks (50 words), Recommendation (50 words). Make it clear and specific. No jargon."

Test 1 output: Well organized, word limit respected, clear.

Test 2 output: Good. One section was light but overall solid.

Test 3 output: Excellent. Exactly what was needed.

Result: Good enough. Save it to library as v2.

Do This Now

Take a prompt you used in the last module. Run it three times. Is it good enough? If yes, save it to your library with notes. If no, improve it and test again.