Skip to content

Structuring Requests That Actually Work

Why Vague Prompts Get Vague Answers

It's tempting to blame the AI when a response feels generic. Often, the real cause is upstream: a vague prompt structurally can't produce a specific answer, no matter how capable the model is.

The model answers the prompt you gave, not the one you meant

An AI model doesn't know your unstated intentions — it responds to the literal words and structure in front of it. "Write about productivity" has no audience, no angle, no length, no purpose — so the model has to invent all of that itself, and it will invent something generic and safe, because it has no signal pointing anywhere more specific.

This isn't a flaw unique to AI. Ask a person "tell me about productivity" and you'd get a similarly broad, unfocused answer — the vagueness of the question caps the usefulness of any answer to it.

Vague vs. specific, side by side

Vague: "Give me some marketing ideas."

Specific: "Give me 5 low-budget marketing ideas for a local bakery trying to reach people within a 5-mile radius, assuming no paid ad budget."

The second version isn't longer because it's trying harder — it's longer because it actually contains the information needed to produce a non-generic answer: budget constraint, audience, geography, channel limitation.

The "who, what, why" test

Before sending a prompt, a quick gut check: could a stranger who knows nothing about my situation answer this usefully with the information I've given them? If the honest answer is no, the AI faces the same problem a stranger would.

This compounds with follow-ups

Vague prompts also make follow-up requests harder to act on. "Make it better" after a generic first answer gives the AI almost nothing to adjust toward. "Make it more concrete — right now it doesn't mention my actual product" gives it something specific to fix.

Key takeaway: specificity isn't a nice-to-have polish step — it's usually the entire difference between a generic answer and a genuinely useful one.