Community post
The Prompt Failed. What Should You Change First?
By Liam · Published · 2 min read
Editorial standards and correctionsA simple failure diagnosis for AI prompts: wrong task, missing context, weak format, or no test criteria.
The fastest way to improve a prompt is to name the failure. “The model was bad” does not tell me what to change. “It summarized the wrong document section” does.
Once you make one change, Compare Two Prompt Versions Without Fooling Yourself helps you test whether that change actually improved the result.
Four common failure types
Wrong job: You asked for “help” when you needed a review, comparison, or draft. Fix the task verb and define what should be included.
Missing decisive context: The model assumed a user account, a date, or a game mechanic you never supplied. Add the one fact that changes the answer or ask it to clarify.
Wrong output: The answer is a long essay when you needed a checklist or code with tests. Specify the form that makes the result usable.
No acceptance test: You cannot tell whether the answer is good. Write a criterion before revising the prompt.
Suppose the model gives you generic game ideas when you want a mechanic you can prototype tonight. The likely failure is not its writing style. The task lacks a prototype constraint. Try:
Propose three mechanics for a two-player game that can be tested with paper cards in one hour. For each, show the player action and the first 5-minute test. Reject any mechanic that requires new art, networking, or a long story.
Now an idea is useful only if it passes the buildability check.
Change one cause at a time
If you simultaneously change the task, audience, format, model, and context, you may get a better answer but learn nothing about why. Change the most likely cause first. Keep the original answer beside the new one. Google’s prompt design strategies frame prompting as experimentation and refinement rather than a fixed incantation.
Know when prompting is not the fix
If the model lacks access to a live fact, a current document, or your actual code, adding clever wording will not supply it. Bring the needed evidence, use an appropriate tool, or do the check yourself.
Try it: Save one disappointing answer. Label the failure as job, context, output, test, or missing evidence. Make one targeted edit and compare against the original criterion.
Keep learning: Make a Bad Prompt Better in Three Edits, How to Test a Prompt on More Than One Example, and Compare Two Prompt Versions Without Fooling Yourself.
About the author
Liam
Coder and gamer. I test prompts, share what works, and show how to improve AI results for code and creative projects.
View Liam's public profileComments (0)
Loading comments…
Keep exploring
Related from Prompt Engineering Lab
Prompting for a Small Feature: Requirements Before Code
Turn a vague feature idea into user actions, edge cases, and acceptance criteria before asking AI to generate code.
How to Prompt Across Models Without Pretending They Work the Same
Keep the task and success criteria stable while checking each AI provider’s current model-specific guidance.
Compare Two Prompt Versions Without Fooling Yourself
Hold the task and test set constant, change one instruction, and record tradeoffs when comparing AI prompts.