Many people's early, frustrating experiences with AI tools trace back to a small, specific, and avoidable set of prompting mistakes rather than to a genuine limitation of the technology itself. Recognizing these specific patterns is more useful than general encouragement to “prompt better,” since each one has a concrete, checkable fix.
For another practical perspective on prompt structure and iteration, Anthropic prompt engineering overview is useful further reading.
The vague-request mistake
Discussed in more detail in the specificity guide elsewhere in this section, a vague prompt is probably the single most common mistake, and the easiest to fix once recognized — the fix is simply adding the specific context, audience, angle, and format details a vague request leaves to the model's default guess.
The everything-at-once mistake
Also discussed in more detail in the breaking-down-tasks guide elsewhere in this section, asking for too much in a single prompt — research, structure, full draft, and formatting all at once — tends to produce a shallower result on each part than a sequence of focused prompts would. The fix is breaking a complex request into a deliberate sequence rather than one sprawling ask.
As this kind of work becomes a repeatable team process, the resource here can provide additional operational context for time, workload, and delivery decisions.
The trust-everything mistake
Treating fluent, confident-sounding output as automatically accurate, discussed at length in the what-llms-actually-do and what-hallucination-actually-means guides elsewhere on this site, is a specific, common mistake with real consequences when a false or invented claim makes it into published or acted-upon work. The fix is a habit, not a one-time correction: treating any specific, checkable factual claim as needing verification before it's used for anything that matters.
- Vague requests: fix by adding specific context, audience, angle, and format details, discussed in the specificity guide elsewhere in this section.
- Asking for too much at once: fix by breaking a complex request into a deliberate sequence of focused prompts, discussed in the breaking-down-tasks guide elsewhere in this section.
- Trusting fluent output as automatically accurate: fix by treating specific, checkable claims as needing independent verification, discussed in the hallucination guide elsewhere in this section.
- Starting over instead of iterating: fix by giving specific follow-up corrections to an imperfect response, discussed in the iterating-on-a-prompt guide elsewhere in this section, rather than discarding it and starting fresh.
- Describing a format instead of showing one: fix by providing a concrete example of the exact output pattern wanted, discussed in the few-shot-prompting guide elsewhere in this section, rather than relying on a purely verbal description.
- Assuming a technique that worked on one model or tool transfers unchanged to another: fix by treating model- or tool-specific tricks as needing re-verification, discussed in the prompt-engineering guide elsewhere in this section, rather than as universal, permanent knowledge.
Why these five mistakes account for a disproportionate share of frustration
Each of these five mistakes is individually easy to make and individually easy to fix once named specifically — the challenge is usually that a first frustrating experience doesn't come with a clear diagnosis attached, so it's easy to generalize from “that didn't work well” to “this tool isn't very capable” rather than to the more accurate and more useful “that specific prompt had a specific, fixable issue.” Having this short, specific list in mind while reviewing a disappointing result makes it much faster to identify which of the five (or which combination) actually explains what went wrong.
This list is deliberately short and specific rather than exhaustive, on the theory that a short list of genuinely common, genuinely fixable mistakes is more useful in practice than a longer, less memorable one — the same specificity principle discussed elsewhere in this section, applied here to the advice itself.